Skip to content

Host shell, git and web sessions

Run shell lines on a host from the session page, keep a session's branch in step with the default branch, and how web sessions edit and commit.

Updated 28 Oct 2026Checked against belai@35506b9, vdb-site@284f1d6, website@a31d470

Shell lines from the web

With belai rc --web-shell (on by default on a Pix Sandbox), the session page can run one shell line at a time on the host:

  • From the composer, !cmd runs the line and attaches its output to the model’s next turn, but only once the classifier has found it safe.
  • From the console drawer, the output is for you only and never goes to the model.

A line runs under the same permission rules and OS sandbox as the TUI’s !cmd, and lands in the session’s transcript. Without --web-shell, shell lines are refused.

Git sync

Sync with main on the session’s git strip rebases the session’s branch onto the default branch before the first turn, and before the first turn after a commit, when the tree is clean. It is the same as git.sync in settings, for that session. Re-check on GitHub reads the pull request and its checks live, for 1 GitHub call.

A sync before a turn ends as synced (brought up to date), current (already up to date), skipped, conflict (the rebase conflicted and was aborted, so nothing moved) or error.

Web sessions

A session started from the website runs on the host exactly as if it were typed there. You can follow it, prompt it and answer its questions from the session page. See Sessions.

API

Method Path
POST /v1/belai/sessions/{id}/shell
PUT /v1/belai/sessions/{id}/git-sync
Edit this pageSources: belai/docs/remote-control.md, vdb-site/api/internal/handler/belai_shell.go, vdb-site/api/internal/handler/belai_git.go, vdb-site/api/internal/handler/belai_web.go
esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.