How to run Claude Code in the cloud

Running Claude Code in the cloud means the terminal agent executes on a remote computer instead of your laptop. On Matrix, you connect to that computer through the desktop app, browser or CLI, run Claude in its repository directory, and inspect the resulting files and tests.

This guide covers terminal-based Claude Code on a Matrix computer. Claude's own managed web tasks are a different execution path; see the official overview of Claude Code surfaces before choosing a setup.

When a cloud computer helps

A remote computer is useful when a repository needs a stable tool environment, a task should outlast a laptop connection, or several isolated agent tasks need access to the same project history. It is less useful when a short local task already works well and remote access would only add setup.

Local sleep pauses execution. A remote host can keep working while the laptop sleeps, provided the host remains running and the task is not waiting on authentication, permissions or human input. Remote compute removes one dependency; it does not guarantee completion.

Set up Claude Code on Matrix

1. Open Matrix Cloud or install the Matrix desktop app.
2. Sign in, select a computer and complete provisioning if needed.
3. Open Terminal and create a separate session for a sample task.
4. Prepare your repository using its normal setup instructions.
5. Check Claude is installed and follow its supported authentication flow.

pwd
git status --short
claude --version
claude

If the executable is missing, use Claude's official installation instructions. Matrix sign-in does not automatically authenticate Claude or grant access to a private repository. Authenticate the tools on the remote computer.

The Matrix quickstart covers provisioning and CLI access. Use the setup and reconnect tutorial for a complete first task.

Choose the computer for the workload

Use current plans and pricing to compare resources and lifecycle behavior. A short supervised task and sustained background work can require different plans. Review the terms shown at checkout, including trial eligibility and any automatic renewal.

Agent-provider access can have separate costs and limits. Check both the computer and Claude's access requirements before estimating the cost of repeated runs.

Make the first task reviewable

Start with a small repository and one acceptance test. For example:

Fix the one failing test in this sample repository.
Preserve the test's intended behavior and keep the change small.
Run the tests, summarize the diff and stop for review.
Do not commit, push or deploy.

Watch the start of the task to resolve any permissions it needs. When it finishes, inspect git diff and rerun the relevant tests. A completion message is not a substitute for checking the output.

Reconnect to the same work

Keep the session name and computer selection. Disconnect the viewing client, reopen Matrix and return to the same Terminal session. Check whether the task is running, finished or awaiting input, then inspect the files it changed.

From the CLI, list sessions before connecting:

matrix login --profile cloud
matrix shell ls
matrix shell connect -c your-session-name

Replace your-session-name with the existing session you intend to inspect. The connect command can create a session when it does not exist; that is not recovery of an old conversation.

Files can persist after a process exits, but a reboot stops processes. Provider errors and credential expiry can interrupt an agent. Inspect the last output and use the agent's supported resume path rather than assuming every reconnection restores all context.

Parallel tasks and recurring work

Give each writing agent a separate worktree, branch, terminal and any required port or test database. Sharing one checkout is not safe isolation just because the agents have different task descriptions. Follow the parallel Claude and Codex guide.

Recurring work adds a scheduler, credentials, retained state and failure handling. Confirm the actual Hermes setup or Symphony workflow available to your computer before relying on it. A terminal task does not automatically become a scheduled integration or a notification to a team channel.

Matrix, a raw VPS or a managed agent?

Choose a raw VPS if you want to operate the server, access controls and terminal tools yourself. Choose a provider-managed agent task if that provider's repository and review flow meets your needs. Choose a Matrix computer when you want direct terminal/file access and a workspace you can return to across tasks and terminal agents.

Compare the same small workload across your options: setup steps, correct output, human review effort, lifecycle behavior and current cost. Keep claims about another product tied to its current documentation rather than a general category label.

Try a first task in Matrix

Run Claude Code on one small repository issue in the cloud Terminal.

1. Follow the quickstart to sign in, choose a computer and complete any required provisioning. To use the native app, follow the desktop installation and approval steps.
2. Open a separate session with a small sample project or synthetic input. Configure the agent access needed for that task and make the expected output explicit.
3. Reconnect to the named session, inspect the diff and rerun the relevant tests.

For a worked coding example, use the setup and reconnect walkthrough. Inspect the result before expanding the scope or leaving a longer task unattended.

Open Matrix →Read the quickstart →Current plans and pricing →