Workspace Panels

The file explorer and Git panel operate on the workspace selected for the session. Open either from the workspace panels in the session UI. Paths are relative to the runner’s workspace; a browser does not read files directly from your device.

Browse and preview files

Use the file explorer to navigate directories and preview supported text files. File search and @ mentions help attach project files to a chat message. The runner enforces workspace-root boundaries; paths outside allowed workspace roots are not available through the panel. Large or unsupported files may not preview. See the file explorer implementation and file explorer UI.

Review Git changes

The Git panel shows repository status, diffs, branches, and staged changes. Use it to stage or unstage files and create commits; remote operations such as push, pull, merge, and rebase are available where configured. Review the diff before committing. The runner must have Git installed and repository credentials configured for remote operations.

The panel refreshes local repository changes automatically, including edits made by an agent or another editor. Filesystem notifications trigger updates where supported; while the browser tab is visible, a five-second status check catches missed notifications and nested-file edits. Branch and worktree metadata also refreshes periodically. Returning to the browser tab or reconnecting refreshes the snapshot. Refresh updates status, branches, and worktrees; the update timestamp shows when the last snapshot arrived. A connection or refresh failure is shown explicitly rather than presenting old data as current.

An open file diff updates as the repository changes. Files with both staged and unstaged edits have separate entries so you can review exactly what will be committed. The history explorer updates its commit list without changing an existing selection, and the Stash tab refreshes from the same repository state.

Ahead/behind counts describe locally known remote-tracking refs, not a live query of the hosting service. Automatic updates and Refresh do not fetch, pull, or push. Choose Sync options → Fetch remote updates to update remote-tracking refs without changing the working tree. Fetch, pull, and push remain explicit actions.

Git operations are carried over the runner service channel, not REST. See Protocol and the Git service source.

Web terminal

The Web Terminal opens an independent PTY on the runner (Ctrl+backtick or the panel control). It is not the agent’s shell, does not appear in the transcript, and has the same OS-user permissions as the runner—with no agent sandbox. Any authenticated user who can reach that runner can execute shell commands. Terminals require a connected runner and are lost on page reload or runner restart; use tmux for persistent processes. All terminal I/O passes through the relay, so use HTTPS when the relay is remote. See the terminal implementation.

Security and limits

Workspace visibility is not a substitute for the operating-system sandbox. The sandbox governs agent tool access; service panels have their own runner-side path checks. Do not expose a runner to untrusted users, and review sandbox behavior before using shared or remote runners.