Carlos Remote

Connect this computer to Carlos Remote MCP with one command:

npx carlos-remote

The command opens Carlos in your browser for account verification, pairs the local machine, then keeps the Carlos agent connected.

Options

npx carlos-remote --relink
npx carlos-remote --name "My Mac"
npx carlos-remote --allow "~/Projects"
npx carlos-remote --server https://carlos-v2-pi.vercel.app

Without --allow, Carlos authorizes the current directory plus Desktop, Documents and Downloads when those folders exist. Sensitive paths and secret files remain blocked by the local agent.

Parallel terminal sessions

Carlos Remote 0.13.0 adds a persistent execution runtime on top of the existing multi-session terminal/process layer. Persistent commands such as development servers and watchers can be moved automatically to an independent process session instead of blocking later work.

The default limits are 4 commands being handled concurrently by the HTTPS worker and 32 tracked persistent process sessions. They can be tuned with CARLOS_MAX_PARALLEL_COMMANDS and CARLOS_MAX_PROCESS_SESSIONS.

Useful MCP tools:

• terminal_exec — short command, or automatic backgrounding for persistent commands.
• process_start / process_read / process_write / process_kill — explicit persistent sessions.
• process_sessions — inspect tracked sessions.
• terminal_pool_status — inspect current capacity.

Security approvals remain enforced for actions classified by the Carlos policy as requiring explicit approval. The runtime additionally persists execution sessions, jobs, process metadata, workspaces, checkpoints, artifacts, events, hooks, schedules and deterministic skills under the local Carlos state directory.

Important architecture rule: the calling AI remains the brain. Carlos is the execution runtime/connector: it makes machine actions persistent, observable, recoverable and verifiable without introducing a separate general-purpose chatbot.

Key runtime MCP groups include execution_session_*, terminal_session_*, job_*, workspace_*, checkpoint_*, artifact_*, event_*, skill_*, project_*, website_*, repo_*, agent_process_*, Git, SSH, machine health and port inspection.

End-to-end cancellation

Carlos Remote 0.9.4 propagates MCP cancellation to the local machine. When a compatible MCP client stops a running tool request, Carlos marks the remote command for cancellation and the agent aborts the active execution instead of continuing in the background.

For terminal commands, Carlos sends SIGTERM to the process group and follows with SIGKILL if it does not stop during the grace period. For browser and desktop operations, actions already performed cannot be undone, but the current mission is marked cancelled and subsequent steps are not executed.

Cancellation is supported across both Carlos transports:

• HTTPS/Supabase: MCP request -> cancel_requested -> Desktop cancel poll -> local AbortController -> cancelled.
• Custom Relay: MCP request -> /admin/cancel -> WebSocket cancel -> local AbortController.
• Local stdio MCP: notifications/cancelled directly aborts the matching local request.

MCP and Relay timeouts also propagate a cancellation rather than only dropping the waiting request. The Supabase transport also uses a transactional race guard: cancel and enqueue are serialized for the same user/request, and the original request start timestamp prevents a stale cancellation from affecting a later JSON-RPC call that reuses the same request id.

Multiple Chrome profiles

Carlos Remote 0.9.3 supports several Chrome profiles connected at the same time through extension 0.7.0. It also detects locally known Chrome profiles from Chrome's own profile metadata and marks profiles without the Carlos extension as non-controllable. Each connected profile has a stable local profileId, can expose its Chrome account email when available, and can have a friendly Carlos-only label.

Useful MCP tools:

• browser_profiles — discover connected Chrome profiles.
• browser_profile_select — persist the profile Carlos should control.
• browser_profile_rename — set a friendly local label.
• browser_windows — list windows and tabs for the selected profile.
• browser_window_select — focus an existing authenticated window/tab.

The extension must be enabled in each Chrome profile Carlos should control. Authentication remains inside that Chrome profile; Carlos does not copy cookies or credentials between profiles.