Into its environments
Every machine a run works on, open beside it: its files, a shell, and what changed.
- Every environment of the run. Each role's environment, every worktree, scratch directory or copy a flow made of one, and a chat's own workspace, local or on another machine.
- What it can do, not what the flow asked for. Files are always there; a shell wherever the machine has one; changes wherever git is. What the flow declared only picks the panel you land on.
- Written down. Every file you write, every commit and every shell you open goes into the run's history under your name. What you type into a shell does not.
- Gone when it goes. An environment that closes stays on screen, read-only, saying so.
In a browser
On a running epic, every environment in the Epic panel links to it; in a chat, open the Environment panel beside the conversation. The Environments view lists every environment of the run, grouped by role, with the ones a flow made nested under the one they came from.
- Files. A tree of the workdir, tabs, syntax highlighting, find and replace. You never save: a file is written 0.8 seconds after you stop typing, and when you leave it. If an agent changed it meanwhile, a banner offers Compare, Keep mine or Reload; a file you have not touched just follows what the agent writes.
Ctrl+Popens any file by name,Ctrl+Shift+Fsearches them all. - Terminal. A login shell in the workdir, as many as you like. Close the page and they keep running; open it again, or from another browser, and you see what they printed while you were away. A shell nobody has looked at for 10 minutes is closed, and every shell goes when its environment does.
- Changes. Like an editor's source control: merge conflicts, staged, changed and untracked files, a diff of each, stage, unstage, discard, commit, the last commits, and, where the run keeps them, the snapshots to rewind to. Rewinding waits until no agent is mid-turn there.
In the terminal
/env lists the same environments; /env coder opens the first of the role coder. Files browses and edits with highlighting, or hands the file to $VISUAL/$EDITOR with e. Changes stages, unstages, discards and commits. Shell gives the whole terminal to a shell in the environment; type ~. at the start of a line to come back, leaving it running.
From another device
A device you paired, or one reaching this machine over EasyTier, reads and writes files and works git like any other frontend, but cannot open a shell: a shell is the machine itself. To let it, set this in the settings file:
envs:
paired_terminals: trueYour user, on every machine the run reaches
Whatever you do in an environment you do as the user the daemon runs as, on the machine the environment is on. Read Security.