Sessions & headless runs

Interactive sessions

Open Run → Sessions when agent sessions are enabled (typically requires Kubernetes).

Sessions provision a persistent workspace pod:

1. Create with a project (required). Optionally attach a GitHub repo (both full name and URL) or leave repository fields empty for a blank workspace.
2. Choose environment profile, provider/model, and optional first message.
3. Chat in the session; upload files; use Plan / Ask / Agent modes as offered.
4. Watch the live event stream; cancel an in-flight turn or stop the session when done.
5. Export a ZIP before deleting if you need the files — delete tears down the pod, PVC, and history.

Adjust settings (provider, model, mode, token/cost budgets) from the session settings panel. MCP tools assigned to the project (with your credentials) are resolved automatically.

Headless agent runs

Admin-oriented runs queue Jobs against a development-style agent (repository work, PR delivery, and so on). Open the run detail to:

• Follow resumable SSE events (after= after reconnect)
• Send input when status is waiting
• Cancel, retry, inspect artifacts, or review memory proposals

Runs require Agents + Kubernetes. If the feature is off, create/run actions fail with service unavailable — check GET /api/features.

Tips

• Use Ask or Plan before enabling write tools in Agent mode.
• Set cost and token budgets on long sessions.
• Prefer GitHub App–linked repos so clone/auth works without personal PATs in the UI.