Run Claude Code on your own machine, and drive it from anywhere

Updated 2026-10-23

Claude Code can run on your machine and be accessed remotely through its native Remote Control feature. Denly is another option when you want task queues, runtime choices and recorded plan and review steps across projects.

Denly is a control plane for coding agents (Claude Code, Codex, Cursor, Grok Build, Antigravity) that run on your own machines using your vendor subscription or API key. It manages tasks, plans and reviews across projects; Git-backed tasks can open pull requests, while no-Git projects end with a review of local changes. Your laptop or workstation does the work; a browser gives the instructions.

When native Remote Control is enough

If you want to continue a local Claude Code session from a phone or browser, start with Claude Code Remote Control. It provides that access directly; Denly is not required. Your machine and the Claude process must remain available. Check Anthropic's current plan eligibility and organization settings.

Consider Denly when you need a shared task queue across projects, runtime selection beyond Claude Code, recurring tasks, and a recorded plan-approval and review workflow. It adds a runner to install, a coordination service and its own plan limits and pricing. If native session access covers your needs, you can avoid that additional setup.

Remote Control descriptions were read from the official documentation linked above on 23 October 2026.

What runs where

On your machine	On Denly's servers	Outside both
The runtime CLI and its login	The task list, stages and timing	Your Git host receives pushed code
The repository checkout	Runner liveness and build version	Your AI provider receives the context its CLI sends
File operations, builds and tests	Selected uploads, including READMEs, plans, transcripts and no-Git review diffs, can contain source. Optional workspace E2E covers supported fields; see the data boundary	Local execution does not mean the model runs locally

The connection only goes one way

The runner is outbound-only. It polls Denly for work and pushes status back; nothing connects to your machine. There is no inbound port to open, no tunnel to keep alive and no remote exec path, so this works behind a home router or a corporate VPN without a network change.

The cost of that shape: work runs only while your machine is awake and online. You can queue tasks with the lid down, and they start when the runner wakes.

Set it up

Install Claude Code on the machine that will do the work and sign in to it there.
Install the Denly CLI: curl -fsSL https://denly.dev/install.sh | sh on macOS or Linux, irm https://denly.dev/install.ps1 | iex on Windows. Both install for your user only and need no admin rights.
Run denly login. It shows a code, opens your browser, and you confirm the machine once.
Add the project in the dashboard, then run the denly install <project-id> command it gives you. That clones the repository and starts the runner.
Run denly doctor to check the platform, the service, the credentials, the runtimes it found and the connectivity.

The whole setup

curl -fsSL https://denly.dev/install.sh | sh
denly login
denly install my-project
denly doctor

What you can do from a phone

Every decision the agent hands back to you:

Describe a task and queue it, with an assignee, a runtime and model, attachments, and a task it should wait for.
Approve the plan, or send it back with notes so the agent plans again.
Answer the questions the agent asks mid-run.
Review the pull request and merge it through the recorded gate.
Open a Live Chat session against the project and watch each tool the agent runs, message by message.
Read runner health, and restart a runner that has stopped claiming work.

Which runtime CLIs this works for

The same arrangement covers Claude Code, OpenAI Codex, Cursor, Grok Build and Antigravity. Availability is per machine: each CLI has to be installed and authenticated where the runner executes, and Denly stores the selection policy rather than your vendor subscription.