Skip to main content

AgentsPreview

Agents

Each workspace keeps its own saved ACP sessions and has one active session at a time. Sign in with that agent's subscription, never an API key.

Desktop chrome for the live session is the Agent tab. Mobile chrome for the picker is the Agents tab. Agent-Up does not collect API keys.

  1. Pick an available agent

  2. Complete subscription sign-in if the agent asks

  3. Prompt in the live session

Chrome

Desktop Agent · Mobile Agents

Where it differs

Desktop

The Agent tab lists saved sessions and streams the selected workspace session.

Mobile

Agents lists saved sessions and Server-discovered ACP agents, then opens the selected chat as an inner page.

Desktop Agent tab showing Codex and Harbor Shop

Mobile Agents tab showing Codex

Workspace agent CLIs​

Saved sessions from every enabled ACP agent appear together within the current workspace. Each row shows the agent, the agent-generated short description, and the branch last associated with the session. Select a row to resume it; sessions from another workspace never appear in this list.

Workspace agent chat uses ACP packages enabled on the Server. The picker lists those modules by id. The Server wraps those launches in Nix. Enable the package from Desktop capability-module chrome or Mobile Settings. Clients never call the remote registry.

Sign in with the corresponding CLI's subscription login from Desktop or Mobile when the agent asks. Agent-Up runs that vendor's no-browser or device-code flow on the Server, shows the sign-in link (and Codex device code) in the client, and then starts ACP. An unavailable executable is disabled in the Desktop and Mobile agent picker.

Next in this slice

Configuration

How to declare dotnet[] and docker[] shims.