Read this guide as markdown

Settings and Agent Access

Account

"Account" holds your sign-in and profile.

App

"App" sets personal appearance and behavior.

Agent hosts

"Agent hosts" lists the machines that run agents for your account.

General

"General" holds the name, pauses and settings. After a lost response, inspect current settings and saved requests before changing them.

Assistant

"Assistant" sets the Assistant’s permissions by tool.

Autopilot

"Autopilot" sets which approvals Autopilot may answer, its schedule and its guidance.

Repositories

"Repositories" lists the repositories agents work on.

Agent host

"Agent host" picks the agent host. Pause and drain runs before replacing or detaching it. Lost assignment, checkpoint, transfer or cleanup replies retain one request; retry inspects it without repeating work or restoring an old host.

Agent subscriptions

"Agent subscriptions" lists agent accounts and fallbacks.

Agent personas

"Agent personas" sets how each agent seat is briefed.

Agent MCP grants

"Agent MCP grants" sets outside agents’ access (also called Agent Access).

Check an account request

  1. Open /requests for account requests, including workspace creation and factory limits. Checking never repeats an action.
  2. No receipt means unknown. Keep the request and check again before replacing it.

Recover a settings save

  1. Settings saves, including factory limits, retry a lost reply once and reload current values. Keep the page open until confirmed.
  2. Request IDs and secret digests stay out of browser storage. Reload sends nothing and loses retry identity; inspect settings before retrying.
  3. Handoffs, host credentials and enrollment codes appear once. After a lost reply, inspect recovery and revoke obsolete access before replacing it.
  4. Repository access and author/signing retries inspect the original operation without repeating provider checks or restoring removed repositories.

Grant an outside agent access

  1. Open /<workspace>/settings/agent-mcp-grants.
  2. Click "Grant external agent access".
  3. Name the agent. Leave "Executable actions" and "Approval response categories" unticked for read-only access.
  4. To let the agent act, tick tools such as "Create ideas" or "Set priorities", and approval categories such as "Intake and questions". Choose how long the session lasts.
  5. Click "Create handoff", then copy the handoff prompt and paste it to the agent. The handoff expires 10 minutes after creation.

Reduce or revoke an outside agent's access

  1. Open /<workspace>/settings/agent-mcp-grants and find the agent under "Access grants".
  2. Untick the tools or approval categories to remove, then click "Reduce access". The agent keeps what stays ticked.
  3. To end the session entirely, click "Revoke now" on the same row. A revoked or expired grant shows its end time.

Change what the Assistant may do

  1. Open /<workspace>/settings/assistant. The Assistant starts with no permission to change anything.
  2. Under "Workspace actions", tick the tools it may use, such as "Set task priority". Under "Approval decisions", tick the approval categories it may answer, such as "Intake and questions".
  3. Click "Save Assistant permissions". Untick a row and save again to take a permission away. Removing code-experiment permission cancels the Assistant’s active experiments and keeps their scratch files until expiry. Outside agents keep their own permissions.

Configure Autopilot

  1. Open /<workspace>/settings/autonomy.
  2. Under "Mode", choose whether Autopilot observes, acts or stays out of the way. Under "Risk ceiling", choose the highest risk tier it may act on. Everything above stays yours.
  3. Use "Schedule" to give different hours their own policy, and "Standing guidance" to tell Autopilot how you want cards handled.
  4. Click "Save" to apply. Your own answers always win over Autopilot's.

Archive an agent subscription

  1. Open /<workspace>/settings/agent-subscriptions and find the subscription in the account list.
  2. Click "Archive account". Archiving also removes the fallback policy the subscription owns and its current fallback state. Past fallback transitions stay as history.
  3. If the archive is refused, the message names what still uses the subscription: a seat, a provider default, another subscription's fallback list, or a failover in progress. Clear each, then archive again.

Pause, change and resume the workspace

  1. Open the workspace pause controls and choose "Pause indefinitely" or "Pause until", then confirm. To change a manual pause's end time, click "Change end time" and pick again.
  2. While paused, a banner shows at the top. Click "Resume" to start work again. A pause caused by a provider limit reads "Resume anyway".

Understand a run's sandbox memory

  1. Open /<workspace>/settings/workspace. Its Memory card shows each live sandbox's starting cap, admission reservation, source, and current cap.
  2. Open /<workspace>/timeline?view=everything to see the same evidence beside a queued or live run. A profile's declared minimum is named when it raised either value.