Source Control and web terminal

Open the Workspace tab in the dashboard. Choose a project, then a workspace, from the dropdowns at the top of that page. Source Control and the terminal are available only to the signed-in owner of that project, while its Exeora CLI is connected. Theproject root is the directory you registered; it may be on any branch, not necessarily main. Any other option is a Git workspace connected through exeora workspace or created from Source Control. Project pages still offer Open workspace, which lands on the same tab.

Source Control

The dashboard reads Git's porcelain status from the selected workspace and presents it as a git client: the current branch in the toolbar, a commit composer above staged and unstaged files, and the selected diff beside them. You can stage, unstage, commit staged changes, discard tracked changes, delete individual untracked files, fetch, pull, and push. The branch control lists the current branch, other local branches, and remotes you can check out. Choosing a branch that is already checked out in another connected workspace switches the view to that workspace rather than running git switch in place. Type a name there to create a branch from HEAD, delete a merged local branch, or create a new Git workspace from Source Control.

Exeora invokes the installed git executable directly, without passing these actions through a shell. Credentials stay on the connected machine, and interactive credential prompts are disabled so an unattended operation fails instead of hanging.

For projects registered from a repository subdirectory, status, diffs, staging and destructive actions stay inside that subdirectory. A commit is refused while the Git index contains staged files outside the selected project root.

Force push, hard reset, remote branch deletion, forced local branch deletion, and exposed rebase controls are intentionally absent. Pull uses that repository's own Git configuration.

Web terminal

Opening a terminal requires an explicit confirmation. It starts the machine's default shell in a real pseudo-terminal at the selected workspace's local path. Open terminals belong to the dashboard as a whole: the list stays in the chrome when you leave Workspace, switch project, or reload the tab. Closing the browser detaches the dashboard; the local process keeps running until you close that terminal, the CLI disconnects, the machine is revoked, or the session reaches its idle or maximum lifetime. Reopening the dashboard reconnects to the same shell.

A terminal connection uses a one-time ticket that expires after 30 seconds and is bound to this site's origin and selected workspace. One web terminal may be open per workspace, so the project root and multiple connected workspaces can each have one. Idle sessions end after 30 minutes and every session ends after eight hours.

What is recorded

Source Control mutations and terminal session openings appear in the audit stream. Exeora doesnot record command text, keystrokes, terminal output, file diffs, or commit messages.

Project policy

Source Control and the web terminal are owner-operated workspace features. They do not travel through an MCP client and are therefore separate from the project's MCP command policy. Opening the terminal grants the same authority as opening a local shell as the user running the CLI; review the confirmation accordingly.