Continue a session with another subscription
Antigravity CLI uses the same managed history/resume and structured-handoff
launch paths. Its adapter identifies conversations from native hooks and resumes
the exact saved UUID with agy --conversation <id> in the same isolated account.
Antigravity's workspace cache
contains only the most recent UUID per absolute workspace path, not complete
history. devctl does not use that shared cache to guess a live pane's identity.
The native /resume picker remains available for other account history and
Antigravity App imports.
When native /resume or /fork changes that UUID inside a running process,
devctl accepts the hook identity only for the same runtime account and process
generation, with a matching previous UUID and a fresh observation. It retains
the previous UUID in bounded native history and clears model, goal and context
telemetry from the previous conversation.
For Claude/Codex → Antigravity, save an ordinary structured handoff, then select
it in new-session launch or choose Antigravity in the continuation account
picker. The installed adapter declares contextHandoff and the verified
--prompt-interactive launch flag; devctl supplies only the managed handoff path
as the initial prompt. The source conversation is retained. Antigravity →
Claude/Codex also uses an existing structured handoff. Antigravity receives the
managed devctl MCP through its native per-session configuration; ask the source
agent to publish its current checkpoint with report_session_handoff. The same
approved Project/session bindings and MCP tool allowlists apply as for other
managed clients. A Project that disables devctl MCP keeps it disabled. Operators
can also publish an agent-written checkpoint using the existing CLI, then launch
its destination:
./devctl session handoff workspace-id:antigravity < checkpoint.json
./devctl session new project-id claude continued claude-account --handoff handoff-id
checkpoint.json contains the existing handoff fields goal, completed,
changedFiles, testResults, knownIssues and nextStep; it must contain task
context and evidence, never credentials or a raw transcript. Handoffs remain
scoped to their repository and container. External destinations require a host
advertising agent-context-handoff-v1; managed Documents, portable Skills and MCP
require agent-managed-configuration-v1. Older hosts reject the launch before
starting a client. Authentication and quota for Antigravity remain native and
are not inferred from an unverified account status.
Antigravity 1.4.0 has no verified Claude/Codex raw conversation import/export
command or documented transcript-record schema. Its hooks
expose a local transcriptPath, but that path alone does not establish a safe
history converter. devctl therefore rejects --import-session across this
boundary and labels it unavailable instead of treating an opaque file as full
history. Automatic Write an additional handoff requests use the verified
Claude/Codex composer/receipt protocol and are not offered for Antigravity.
To export context from it, first publish a structured checkpoint as above.
This is context handoff, not native conversation migration or cross-account
Antigravity resume. Native authenticated history and hook delivery have not been
verified against a signed-in account; installer/version/help, argument handling,
capability gates and handoff provenance are tested without model calls.
Administrator-shared subscriptions appear as separate user-owned profiles, but their quota observations refer to the same source subscription pool. Selecting another recipient of that same source is not new paid capacity. Revoked/disabled grants prevent new starts, while existing processes are left running until an explicit continuation. Source authorization is renewed by its administrator. Shared subscriptions (source access required).
In Projects, select a Claude or Codex session and press b. In the web console, click Continue with another account beside the session. Select an account and press Enter (or click Continue). Claude-to-Codex transfers a copy through Codex's native import. Codex-to-Claude converts bounded saved Codex history locally, without prompting the source agent or consuming its quota. The picker labels this convert saved Codex context → Claude · no source tokens. Provider changes create a new session in the same workspace and keep the original session. Project grants remain available; permissions scoped only to the original session are not copied automatically.
The continuation dialog shows animated progress, total elapsed time and time on the current step while checking the account, transferring authorization, waiting for the execution host, importing context and opening the terminal. Host-stop failures appear immediately from the durable command result. Inventory reads have deadlines, so an unavailable host cannot leave an endless waiting screen.
Same-provider account changes on an enforced container are a durable controller operation: stop the exact source process, wait for its successful host command receipt, change the account and enqueue native resume atomically. A native exit hook or temporarily empty inventory is not a stop receipt. Closing the dialog, disconnecting or restarting the controller does not abandon an accepted transfer. The original conversation stays visible in Projects while the transfer is pending or failed. b / Continue remains available in a native mosaic header and in the web actions, including before quota exhaustion. Reopening Continue follows the current transfer rather than queuing another stop. Failed resume retains the conversation identity and permits retry with the selected account.
Operator MCP discovers POST /v1/sessions/:id/account-transfer with
requestId (UUID), accountId and expectedAccountId, and the bounded
GET /v1/sessions/:id/account-transfer status. Reuse the request UUID after a
transport timeout. States distinguish stopping, starting, completed and failed;
success requires the durable native launch result. These routes use the existing
controller session ownership and account authorization boundaries. They do not
authorize another user's credentials or copy session-only grants. Legacy
switch-account remains an explicit stopped-process metadata operation.
The h / Migration action follows the same preference: native Claude-to-Codex import, local Codex-to-Claude conversion, then an already saved handoff. It shows Choose account / agent immediately when saved context exists, without sending a source-agent prompt. w / Write an additional handoff explicitly asks the source agent to save a separate Markdown checkpoint when its quota permits. When neither persisted native identity nor an existing handoff is available, the existing agent-written handoff preparation remains the fallback.
CLI operators can use the same controller/host process:
./devctl session new project-id claude continued target-claude-account --import-session workspace-id:codex
The command selects the source's original container and repository, even when a
different container is preferred or several repositories share a container.
It submits the existing POST /v1/sessions with importSessionId; it does not
export transcript text to the client. --resume, --import-session and
--handoff are mutually exclusive. Existing MCP report_session_handoff is a
checkpoint-reporting tool, not a cross-account migration command, and retains
its existing scope. Controller quota and owner checks remain authoritative.
Codex-to-Claude conversion reads only the selected account-owned rollout inside the original Project container. It keeps the last committed compaction's readable replacement messages/summary, the current branch's first and latest user tasks, recent user/assistant text and bounded saved tool-result excerpts. Tool arguments are not replayed, and pending calls are identified as unconfirmed. A compaction replaces the old branch even when its content is encrypted: earlier conversations are not brought back to replace missing encrypted context.
The resulting text is capped at 24 KiB, with per-message limits and an explicit
omission notice. UTF-8 excerpts retain the start and end of long messages.
The stored tokenUpperBound uses one token per UTF-8 byte plus a per-message
reserve; it is a conservative context allowance, not measured usage or billing.
This leaves room for Claude's own instructions, tools and later prompts. The cap
does not constrain arbitrary extra context supplied by the user's plugins,
configuration or next prompt. There is no model-based summarization and no
requirement for a source subscription with remaining quota.
devctrl publishes a new private Claude JSONL conversation and resumes it through
the existing managed Claude CLI. This is devctrl history conversion, not an
upstream Claude migration API or a native Codex resume. The target UUID differs
from the source. Parent provenance and importedFrom.method=converted-history
remain in controller state; transcript text, tool excerpts and credentials do not.
A private receipt holds identity, source digest, byte counts and omission counts.
Reconnects reuse the published transcript and never overwrite later Claude work.
No source process is stopped and no text is typed into its terminal.
System/developer instructions, hidden reasoning, credentials/configuration trees,
images, encrypted compaction content and subagent conversations are excluded.
Recognized credential formats in visible text are redacted; this is not a
guarantee that every arbitrary secret inside an old user message is identifiable.
An empty or entirely unreadable current branch fails instead of launching a
context-free substitute. Rollouts requiring a separate inherited history_base
or a rollback after the last compaction are rejected explicitly rather than
importing an unavailable or superseded branch.
Use a previously saved handoff when no readable rollout/native identity exists.
The host must advertise codex-claude-import-v1; updating devctl management
components is sufficient, without restarting Project containers.
Source formats were checked against Codex's persisted rollout representation and real Claude JSONL records. Claude's session documentation describes local transcript storage and resume; its CLI reference documents the managed resume command.
Claude-to-Codex import stages Claude's latest complete, main-session compaction summary, messages explicitly preserved by that compaction, and subsequent history. Older messages already covered by the summary stay in the unchanged Claude transcript. Native Codex performs the conversion; devctrl does not rewrite its resulting rollout or invent a summary. Conversations without a verified compaction remain byte-for-byte snapshots. Missing preserved messages fail rather than silently losing context. Private staging metadata records only source/staged byte counts, a digest and whether a compaction was applied.
This compensates for Codex 0.162.1's native importer, which reads chronological
user/assistant messages without applying Claude compaction boundaries. A long
import can otherwise succeed and then fail on every prompt with
context_length_exceeded during remote compaction. Compaction requests themselves
must fit the target model's context window. Already imported conversations are
not overwritten automatically; their import receipts protect subsequent work.
Sources: native Claude reader,
OpenAI compaction guidance.
Format check, 2026-10-17: Claude's native saved conversations are still plaintext
JSONL; the HTTP gzip request-body change in Claude 2.1.300 does not change that
on-disk format. The ZIP saved by /feedback is a diagnostic export, not a native
conversation import. devctrl does not treat arbitrary ZIP/gzip files as saved
Claude sessions or unpack them while discovering history.
Sources: Claude session storage,
official release notes.
To prepare a fresh handoff, select the running source session and press h,
or click Migration in its web card, then choose w / Write an additional
handoff when saved-history migration is available. The source agent authors the context from
its current task; the user is not asked for a goal or next step. The console shows
progress until the host confirms the bounded Markdown file's completion marker,
then b / Choose account / agent opens continuation. The source conversation
and Project remain in place. Esc returns to Projects while preparation continues
on the host. A duplicate pending request reuses the same command; failures do not
silently start an empty target conversation. This requires source authorization,
remaining source quota, and a host advertising session-handoff-purpose-v1.
The host pastes the request, waits for the CLI's composer to settle, then sends
Enter separately. Its native UserPromptSubmit hook confirms receipt before the
file wait starts. A successful terminal write alone is not confirmation. Missing
acknowledgement fails within seconds instead of waiting the full three-minute
checkpoint timeout. Existing or edited user drafts are preserved and never
submitted automatically. Delivery checks the exact container, runtime account,
process start time, execution scope and generation; retries never replay an
ambiguous prompt or interrupt another session.
If the source cannot respond, use stored-history import or its latest previously
saved handoff; the console cannot obtain a fresh agent-written summary from an
exhausted or stopped agent.
The picker shows accounts of both providers, including the available native-import or handoff continuation method, its subscription and remaining weekly/session quota. Current accounts, exhausted accounts and accounts requiring login remain visible but cannot be selected for continuation. If another online host has the selected login, devctrl can transfer its credential using the existing account-transfer workflow. An unknown quota is labeled unknown; it is never presented as 100% remaining. Quota checks use recent official provider samples, ignore reset windows, and are checked again by the controller.
When switching accounts within the same provider, only the selected provider process stops. devctrl waits for host inventory to confirm shutdown, switches the session account and copies exactly that conversation's opaque transcript into the selected account's isolated storage. It keeps the managed session ID, official conversation ID, workspace, settings, handoffs and session access grants. Other sessions and the Project container stay running. Credentials, settings, SQLite databases and other conversations are not copied. A per-switch receipt prevents reconnects from overwriting newly written history.
New-session history has a separate QUOTA EXHAUSTED group, including conversations whose provider process is still alive. Selecting one under the same provider opens the same account picker. Switching providers uses Claude-to-Codex native import, bounded Codex-to-Claude saved-history conversion or an existing handoff; changing subscriptions within one provider preserves the full conversation.
No alternative signed-in account means the picker explains the limitation. Add or renew an account in Accounts. Continuation requires a known official conversation UUID and a host-agent advertising account-continuation-v1; update the control plane/host-agent, without rebuilding Project containers. An autonomous Agent Run must finish or be cancelled before changing its session account. API clients must stop the session, wait for authoritative inventory, then POST /v1/sessions/:id/switch-account with accountId and expectedAccountId, and attach normally.
The source transcript is retained. A missing or unsafe transcript fails closed and does not start an empty conversation. If terminal connection fails, retry the selected account/attach; no duplicate session is created. Codex uses its supported filesystem lookup for the selected rollout rather than copying the source account's global SQLite index (official implementation).
Exhausted mosaic tiles use one red outer border when unselected. Selecting one adds a white outer frame around a red inner frame, so selection remains visible alongside the quota warning. The red ! LIMIT header and leading QUOTA EXHAUSTED label remain visible.
The native TUI executes inside the controller container. On console startup, devctl compares the local compiled UI with the cached console image. A changed build is verified and copied into a derived image without reinstalling dependencies, then only the controller is activated when its image differs. The same UI survives console-container recreation; copying a bundle into a running container alone is not an update. Project containers and host-agents remain in place, including when the local controller is an SSH proxy. Existing TUI processes need reopening to load the new code. Installations without a local build use their installed image. The web launcher also rebuilds its local browser bundle before starting.
Inherited conversations show Parent: Project / provider session beneath the child. Press p or click that line to focus the parent. Hidden live parents open in the hidden mosaic; stopped parents open in Sessions. A removed parent remains identified but cannot be focused. New import/handoff/fork records persist parent provenance, while older imports and handoffs are resolved from their existing metadata.
Native Claude-to-Codex import returns an official conversation ID. The host sends that ID to the controller before reporting the terminal ready, so it survives detach and process exit and remains available in continuation history. Older imports can recover their ID from the private conversion receipt bound to the same account, session HOME, repository, process generation, and explicit Codex resume command. An imported conversation is never replaced by another account's newest transcript.
Accounts places each five-hour and weekly quota row beside a separate time remaining label. Token rows are named tokens 5h and tokens weekly. Both bars fill forward: tokens show consumed quota, time shows the elapsed portion of the window. Percentages beside the bars describe what remains. Claude, Codex and Antigravity use this same convention. Remaining duration and the exact weekly reset timestamp stay visible as text. Exhausted quota rows and their account headers are red. Both the terminal and browser use the same component in detailed and compact views. Its local clock updates each minute and at the reset boundary without polling the controller. The time bar follows the official subscription cycle rather than a calendar Monday. Missing, expired or inconsistent reset timestamps produce an unavailable/reset-due label instead of an invented new week; last-known quota samples retain their stale label.
Press v in Accounts to switch views, including while the sidebar has focus.
Compact view keeps the account identity, authentication warnings, five-hour and
weekly quota bars, and both remaining-time bars. It hides sample timestamps, host
presences, session rows and route metadata. Press v again for those details;
selection stays on the same account.
The host also reads Claude's account-wide five-hour and seven-day quotas every
five minutes without a connected TUI or browser. This supplements status-line
reports, where either window can be absent, including an exhausted Team window.
The probe runs as the account UID inside an existing owned Project container,
uses the account's configured proxy/VPN route, and makes only a read-only request
to the same OAuth usage endpoint used by Claude. It never starts another Claude
process, submits a model prompt, refreshes tokens, or modifies credentials.
API samples are labeled official-api; native status-line samples remain
official-cli. Failed or unsupported responses preserve the last known sample
with its original timestamp. This upstream CLI endpoint is version dependent;
missing values are not inferred as unused allowance. Manual refresh of an active
Claude account requires a host advertising claude-oauth-usage-v1, so older hosts
cannot run their legacy concurrent CLI probe beside a live session.
Claude's official five_hour and seven_day fields define their durations, including older
saved samples. Codex samples retain the app server's windowDurationMins as
durationSeconds; time bars require a verified five-hour or seven-day duration
for the corresponding window. Older Codex samples with no duration keep their quota/reset information but
do not pretend their window length is known. Refresh usage to obtain the duration.
Official window duration is preserved when an older host report omits it for the same account/provider and exact reset instant. An explicitly reported duration replaces it; a different reset or account never inherits that metadata. Hosts running an older collector still need a control-plane update to report durations for newly observed Codex windows. Missing duration is shown as unavailable rather than assuming every secondary quota window lasts a week.
Launch progress and failures
Accepted launches use immediate host WebSocket dispatch, reconnect replay and an independent two-second persisted-queue poll. They do not wait for full Docker storage accounting. The observer shows queue waiting, container lookup, retained storage, folder/mount checks, existing terminal, permission checks, CLI updates and conversation import as separate timed steps. Closing the observer does not cancel the accepted server operation.
A launch failure is sent in a full terminal error frame rather than a truncated WebSocket close reason. It remains visible in Projects and Mosaic with its error; it is not silently hidden as old conversation history. The account-continuation picker displays this actual error instead of a generic terminal-unavailable hint.
Continuing an agent does not bypass the Project's enforced Internet policy. A legacy container without the required isolation cannot start another process until its boundary is explicitly updated or a compatible container is selected. Existing provider processes and conversations are preserved. Native imports in this version remain scoped to the same Project container.
Frozen sessions
Projects supports Freeze / Thaw (Shift+F), independently of Hide and Detach. The server saves the last terminal screen, stops the exact agent process, retains native history and the original account/profile, and resumes through the existing durable launch path. Frozen has its own tab; empty Frozen, Hidden and Quota tabs are omitted. Temporary compute requires a verified encrypted S3 archive and recovery index. See Freeze and thaw for recovery and storage boundaries.