EFEnvForgeJoin waitlist

Docs / Branch workspaces

Branch workspaces are the shared handoff point.

A workspace gives one branch a durable shell, repo checkout, readiness state, signed dev link, and awake-only runtime. Developers, agents, reviewers, and operators can move through that same workspace without trading raw VM names or rebuilding local setup.

Start with setupReview resourcesReview workspace policies
workspacebranch lifecycle

$envforge up signed-links

Shell ready: signed-links

Runtime awake for web, API, workers, and tests

Dev URL: web--signed-links--acme.dev.envforge.ai

Idle sleep keeps shell and metadata ready

Lifecycle

One branch workspace moves through five visible states.

The lifecycle should be readable from the CLI and product UI: workspace identity, shell attach, runtime wake, signed review, and idle sleep are separate states with different access and billing implications.

  1. Branch selectedworkspace identity

    EnvForge opens or reuses the workspace for the selected project and branch, so developers and agents meet in the same repo checkout instead of recreating local state.

  2. Shell readyincluded baseline

    envforge up attaches to the always-ready shell first. Git, tmux, editors, Claude, Codex, logs, and workspace metadata are available before service processes finish waking.

  3. Runtime awakemetered services

    Dev URL traffic, tests, workers, or service commands wake the runtime VM for web, API, database, cache, mail, storage, and queue work.

  4. Dev link sharedsigned browser session

    A service--workspace--org.dev.envforge.ai link gives reviewers the app surface for that workspace without exposing SSH, secrets, logs, or runtime admin.

  5. Idle sleepruntime stopped

    When service work goes quiet, EnvForge sleeps the runtime meter while preserving the shell, branch checkout, workspace metadata, and signed-link state.

Collaboration handoff

Each surface has a clear owner.

A handoff should name the workspace and the surface someone needs, not the host running it. That keeps reviewer access narrow, developer access authenticated, and operator checks visible.

SurfaceOwnerHandoff
Developer shell

Developer or agent

Attach to the existing branch workspace with envforge up, then continue from the same Git checkout and terminal context.

Service runtime

Workspace services

Wake services only when tests, dev URL traffic, workers, or explicit commands need web, API, resources, or background jobs.

Signed dev link

Reviewer

Share the dev.envforge.ai link for app review while private operational surfaces stay behind authenticated workspace access.

Usage and readiness

Operator

Check runtime state, caps, readiness, and smoke results before leaving an unattended agent or reviewer session running.

Continuity rules

Keep workspace state durable, but cleanup explicit.

EnvForge should make branch work easy to resume without turning dev links into permanent environments. These rules keep collaboration notes product-facing and cleanup intentional.

  • Branch workspace names are the handoff handle; raw VM hostnames, IP addresses, and cloud resource IDs should not be part of public review notes.
  • Sleep is not deletion: idle sleep stops the runtime meter but keeps shell access, repo storage, metadata, and dev link state available.
  • A fresh envforge up should reattach to the workspace and report dev URL, runtime, and resource readiness instead of asking users to rebuild local setup.
  • Cleanup should be an explicit workspace action after branch work is merged, abandoned, or no longer needs signed dev links.