Accounts and Auto
Register isolated agent accounts and use Auto selection, pinned profiles, live task switching, and usage-limit recovery safely.
AGI Cockpit account profiles isolate multiple sign-ins for the same agent provider and let tasks, Autoruns, and Fleet runs choose between them. Profiles are supported for Claude, Codex, Antigravity, Cursor, Qoder, and Grok Build.
Understand default and named profiles
Each provider has a default account that uses its existing environment. You can add named profiles such as work and personal. A profile name is Cockpit's local selection label, not the AI service's plan name or email address.
An agent account profile is separate from a Browser Identity. An account profile isolates execution authentication for Claude, Codex, or another task agent. A Browser Identity isolates cookies, localStorage, and other website state in the in-app browser.
Create and sign in to a profile
Open the target agent under Settings → Agents, add an account profile, and sign in to it. From the CLI, identify the provider with --agent-type.
cockpit accounts
cockpit accounts create work --agent-type codex
cockpit accounts login work --agent-type codex
cockpit accounts list --agent-type codex
The list reports the provider, profile ID, name, email when available, authState, provider-specific usage, and the time that usage was fetched. authState distinguishes usable ok, invalid expired, and credential-free signed_out accounts. The compatibility field loggedIn is true only for ok. auth_required means the profile must sign in again, while error means usage could not be fetched. Expired and signed-out accounts are unavailable to Auto and the Fleet pre-run check.
For Codex, Cockpit retrieves usage and rate limits from the Codex CLI app server in a read-only sandbox without approval prompts. This retrieval path supports Codex CLI 0.153.
Named Antigravity profiles use browser-based Google OAuth and keep conversations, logs, cache, and usage history under a profile-specific home. On macOS, Cockpit puts a profile-specific Keychain first in the search list and verifies that order before a task starts, preventing fallback to the host Antigravity login and its quota. The OS keyring is shared on Windows and Linux, so a host login stored there still takes precedence for every profile.
Use Auto
When account selection is available, new tasks, Autoruns, and Fleet nodes default to Auto. Auto is a selection method, not one named profile. At runtime it compares available usage across signed-in accounts and chooses an execution account.
Auto first requires remaining capacity in every applicable window, including shorter limits. It then compares accounts by the window with the latest reset and favors the account with the most remaining percentage per minute until that reset. This helps consume an underused weekly or other long-term quota that expires sooner. Shorter windows remain an immediate availability gate; they do not override the long-term ranking.
If an Auto task reaches a supported usage or plan limit, Cockpit selects another available account, transfers the saved session, and continues. Exhausted Claude usage credits and Codex workspace credits are included in this recovery. When no alternative is available, usage cannot be confirmed, or switching or resuming fails, the task reports the reason and waits for a person. After a recorded reset time passes, Cockpit re-evaluates that usage limit and resumes the same task when capacity has recovered. An expired credential cannot recover through a quota reset and must sign in again.
An Autorun resolves Auto again on every execution. Fleet can spread parallel nodes across available accounts instead of concentrating all work on one profile. Actual concurrency still depends on provider plans, usage limits, and machine resources.
Pin one account
Choose a named profile when audit, client, billing, or data-separation requirements must pin the execution account. Use --account from the CLI.
cockpit task create --instruction "Review this change" --directory /path/to/repo --agent-type codex --account work
cockpit autorun create --name "Daily review" --instruction "Review changes" --directory /path/to/repo --agent-type codex --account work --type cron --expression "0 9 * * *"
A pinned profile does not switch automatically after a usage limit. If a saved fixed profile becomes unavailable, Cockpit does not silently substitute another account. It disables the Autorun and marks it as needing attention.
Switch an active task
cockpit task account <task-id>
cockpit task account <task-id> work
cockpit task account <task-id> default
Claude, Codex, Grok Build, Antigravity, Cursor, and Qoder tasks can switch accounts while active. Cockpit stops the current runtime, transfers the saved conversation to the selected profile, and resumes the same task. A task may reject switching while it is generating a reply or immediately after startup, so wait until it can accept input.
After switching a task that stopped at a usage limit, send a follow-up to continue. While Auto is still switching an account, a Fleet node remains running and becomes interrupted only if recovery cannot complete. Switching does not merge provider-side billing or unrelated conversation histories.
Sign out of Antigravity
cockpit accounts logout supports Antigravity only. Without --confirm, it is a read-only preview that reports the target Keychain or keyring items and token files, shared state, and impact. Review that result before repeating the same command with --confirm.
cockpit accounts logout work --agent-type antigravity
cockpit accounts logout work --agent-type antigravity --confirm
Logging out a named profile targets only that profile's storage and does not change the host login. Logging out the default account removes the host Antigravity credential, which also signs out any other profile or ordinary terminal-launched Agy process that relied on that shared login. On Windows, Linux, or a macOS profile whose profile Keychain is unavailable, the profile preview reports the effective host item as sharedCredential and points to the default-account logout procedure. Cockpit never logs an account out automatically.
Antigravity usage reports the credential source and home, quota source, and quota scope. quotaScope: host_login means the displayed quota is not profile-specific. If an exhausted quota appears to belong to the wrong account, inspect this provenance before signing out or signing in again.
Remove a profile
cockpit accounts remove work --agent-type codex --confirm
The default account cannot be removed. Removing a named profile requires confirmation and is rejected while a task or Autorun uses it. Change those consumers to Auto, default, or another profile first. Removal makes that profile's isolated authentication and saved data unavailable, so verify both the provider and name.
See Agents and models for capability differences, Task details for stopped-task handling, the cockpit accounts reference for the exact command contract, and Security and data for credential boundaries.