Skip to main content
Start the workspace from the project directory you want the agent to work in:
Open the printed URL (default http://127.0.0.1:3000).

Projects and sessions

The workspace organizes sessions into projects bound to directories on disk. Create a project, browse to its directory, and every session you start in it runs with that working directory. Sessions persist after you close the tab; resume, rename, fork, or delete them from the session list. See Sessions and projects.

The composer

The composer is where you type requests and control the run:
  • Model picker — choose the provider and model per session.
  • Thinking leveloff, minimal, low, medium, high, xhigh, or max.
  • Modeagent (default), plan, or harness. Plan mode tracks a plan with progress; you can execute or refine it.
  • Attachments — attach files to the session for the agent to use.

Tool cards

Every tool call renders as a dedicated card in the transcript:
  • IPython — code cells with their output, backed by the session’s persistent kernel.
  • Bash and Edit — shell commands and file edits with diffs.
  • Plans and todos — plan progress and task lists.
  • Subagents — child agents spawned by the engine’s recursive rlm workflow.
  • Questions — interactive prompts you answer inline. Unanswered dialogs time out after 60 seconds.
Anything without a dedicated card falls back to a generic tool renderer.

Slash commands

Type / in the composer for autocomplete over the engine’s slash commands. Common ones:
  • /login — add provider credentials.
  • /refine — run the engine’s self-improvement workflow over the session trajectory.
Autocomplete comes from GET /api/chat/commands; execution goes through POST /api/chat/command.

Skills, prompts, and extensions

The engine’s executable skills, prompt templates, and extensions are surfaced in the workspace through GET /api/chat/resources. They are engine features: install and author them the same way you would for a plain prime-agent install, and Fleet lists them per session.

Workspace navigation

The workspace panel shows the file tree of the bound directory (GET /api/workspace/tree) with file previews (GET /api/workspace/file). Rebind the root directory from the UI (POST /api/workspace/root) or pick a directory with the built-in browser.

Settings

Settings exposes the resolved engine settings and persists changes through the engine’s settings manager (GET/PATCH /api/chat/settings). Provider management lives in Settings → Providers; see Providers and models.
Last modified on August 30, 2026