Claude
aa45bf84ef
`dispatch --prepare-model --thread` (and a send that uses the local model) only connected the lead's provider. A group member on another provider then failed at spawn on the guest. After the lead's `key` operation, the CLI now reads the conversation's `group` (GET /v1/threads/:id), resolves each active non-lead member's saved route from /api/agents/:id, and sends one more `key` operation per distinct provider from the local configuration for it, under the same portability checks as the lead (HTTPS endpoint, API-key auth, no device-bound sign-in). Keys stay memory-only on the guest through the existing session `key` operation. Removed members are ignored; a member whose provider is the lead's is not sent twice. A member with no saved model, or whose provider is not configured locally, stops the handoff with that member's name rather than being skipped. The prepare receipt gains `members` (agentId, provider) for the connections it added; the desktop already prepares before every cloud send, so it picks this up with no app change. Verification: a throwaway test (not committed) drove computer::run with the existing FakeTransport for a group (lead deepseek; Ana anthropic; Dee deepseek; Old removed): key operations went to deepseek then anthropic only, receipt listed Ana/anthropic; 1 passed, 0 failed. cargo test -p codewhale-cli --lib cloud: 122 passed, 1 failed — the failure, login_selects_managed_route_when_provider_is_default, fails identically without this change in this container (pre-existing, environment-dependent). cargo fmt clean. No live account, Boat computer or provider call. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01PsruMwr3b8fWh1sfKL7JTQ
5.3 KiB
Cloud computer dispatch (preview)
Cloud conversations run on a computer in your Codewhale account. The terminal and desktop open the same conversation ID; closing either view leaves the task running. Availability depends on your account and the deployed service.
Sign in, configure your model in Codewhale, and dispatch:
codewhale login
codewhale dispatch "your task"
printf 'Review the failing checks' | codewhale dispatch
Dispatch selects your only running account computer and the configured model.
When several computers are running, use --computer COMPUTER_ID. List them with
codewhale account computers list. Start and create operations use the account's existing
compute allowance, consent and admission checks. To create a computer, use
codewhale account computers create --help or Manage cloud computers in desktop.
Dispatch does not allocate or start a computer implicitly.
The returned conversation appears in desktop history for the same account. Desktop's Continue in terminal control shows the matching command:
codewhale dispatch --thread CONVERSATION_ID
codewhale dispatch --thread CONVERSATION_ID "continue the task"
codewhale dispatch --thread CONVERSATION_ID --stop
codewhale dispatch --thread CONVERSATION_ID --json
Inspecting prints messages and pending approvals. Use --approve APPROVAL_ID
or --deny APPROVAL_ID after reviewing the request; approvals apply once.
Answer pending questions in desktop. --stop interrupts the turn and leaves
the computer running. Use account computers pause COMPUTER_ID to stop compute.
Dispatch resolves your configured model through Codewhale's shared config and credential resolver. A portable API key is supplied to the selected Engine in memory, bound to the same provider endpoint. Restarting the Engine clears it. The receiving Engine must support endpoint-bound session credentials; an older Engine refuses this handoff. The desktop uses the same CLI resolver through its native bridge, so credentials never pass through the webview.
Device-bound sign-ins, custom header authentication and local-only inference
cannot currently be transferred this way. Select a portable HTTPS API-key
connection, or configure the computer's existing connection explicitly.
--key-stdin remains available for explicit memory-only credential entry.
Do not put keys in command arguments. This does not enable the account key vault.
--cloud-provider PROVIDER --cloud-model MODEL explicitly selects the computer's
existing connection. Without those overrides, a follow-up checks that your
configured model still matches the conversation before transferring a key.
--configured-model reports the selected model and whether it is portable,
without returning a credential. --prepare-model --thread ID reconnects that
model without starting a turn.
A whale is a named account collaborator with a saved provider and model.
codewhale account agents create NAME --provider PROVIDER --model MODEL --operation-key KEY saves one without starting work or a computer, and
codewhale account agents list shows each whale's saved model.
codewhale dispatch --whale AGENT_ID "your task" starts a cloud conversation
with that whale: the service takes the route from the whale's saved
configuration, and your local configuration for that provider supplies the
memory-only key. Later --thread follow-ups keep using the whale's current
saved model; a changed whale applies to the next turn, not to a running one.
In a group conversation, a send or --prepare-model also connects the provider
of each active member whose saved provider differs from the lead's, from your
local configuration for that provider, memory-only like the lead's key. A
member whose provider is not configured locally stops the send with that
member's name; it is never skipped.
Every send prints a replay key before submission. After an uncertain response,
repeat the original command and prompt with --operation-key KEY. Keep the
original --computer target when retrying creation, or the original --thread
when retrying continuation. Reusing the key with changed content is refused.
Do not start another conversation to recover an uncertain send.
codewhale account session exposes the same computer conversation commands.
The earlier dispatch Agent Work flow, including its repository and file
context options, remains available when an Agent Work option such as --agent
or --context-file is supplied.
Work-only flags cannot be mixed with computer conversations. This preview does
not move local folders or repository checkouts into a VM.
The command pattern follows Claude's cloud CLI: submit a task, retain the returned session ID, and send follow-ups from another surface. Codewhale retains its own model and computer account controls.
Codex cloud environments
also separate reusable environment setup from ongoing tasks. The installed Codex CLI
exposes cloud exec --env, cloud status, cloud list, cloud diff and
cloud apply; these are reference commands, not Codewhale dependencies.
Codewhale uses its existing Boat computer and workspace rather than provisioning
another execution service. Sessions on one computer share that computer's files;
select a separate computer when filesystem isolation is required.