Skip to main content

AgentsPreview

Agents

Each workspace has one ACP agent session. 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 streams the live workspace session.

Mobile

Agents lists Server-discovered ACP agents and opens chat as an inner page.

Workspace agent CLIs​

Workspace agent chat uses first-party Codex, Cursor, and Claude capability adapters on the Server. Those adapters launch only the ACP command declared in Agent-Up capability inventory, not a hardcoded executable name.

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 inventory declares ACP commands.