See the work
Follow agent output, inspect Git changes, and switch between projects without returning to your terminal.
Claude Code + Codex · Browser + phone
AgentD
Your coding agents keep working.
Stay in control from anywhere.
How it fits together
Your agents. Your machine.
The daemon runs beside your projects. Your browser is the control surface. Add a relay when you leave the local machine.
- 01 · Developer machine
AgentD daemon
Runs Claude Code and Codex. Owns local session history and routes approval requests.
- 02 · Optional transport
Your relay
Routes encrypted payloads over TLS. Sees routing metadata, not decrypted session content.
- 03 · Wherever you are
Browser or phone
Decrypts the session, displays output, and sends your prompts and decisions back.
On the same machine, the browser can connect directly. Direct WebSocket access is trusted local access and is not E2E encrypted.
The working session
Read. Respond. Keep moving.
Make the decision
Respond to approval requests and questions. Permission modes and policies determine when the agent needs you.
Pick up the thread
Reconnect to the daemon's session state and history. A closed browser does not mean a stopped agent.
Get started
Start with one session
For the source build: Linux or macOS, Git, Make, the daemon's declared Go toolchain, Node.js 22.12+, and an authenticated Claude Code or Codex CLI.
For a phone or another network, host the PWA over HTTPS and configure a TLS relay. Keep pairing codes private.
Release preparation: installation instructions and repository links will be available after publication.
Trust boundaries
Know what you are granting access to.
Encrypted relay payloads
AES-256-GCM protects content between daemon and browser. The relay still sees connection and routing metadata.
Permissions are explicit
Claude SDK permission callbacks and Codex app-server approvals have different controls. Bypass modes and automatic policy decisions are not manual approval.
Endpoints matter
Protect your machine, browser profile, and PWA host. Transport encryption does not protect a compromised endpoint or every local file.
Source and ownership
Choose the pieces you need.
Five MIT components. One optional source-available relay. Self-hosting does not require the private hosted account service.
agentd
Session daemon and Claude hook
MITagentd-web
Browser and mobile PWA
MITagentd-protocol
Shared wire contracts
MITclaude-agent-sdk-go
Claude Code SDK for Go
MITcodex-agent-sdk-go
Codex SDK for Go
MITagentd-relay
Optional self-hosted relay
BSL 1.1 · source-availableThe relay's BSL 1.1 additional use grant excludes competitive hosted or embedded offerings. Its license specifies an Apache-2.0 change date of March 15, 2030.
Questions
Before you connect
Does AgentD run the models?
No. Claude Code and Codex run on your machine and use their own authentication and model access. AgentD manages their sessions and connects them to your browser.
Do I need a hosted account?
No. Run the daemon and browser client yourself. Add a self-hosted relay when you need remote access. Hosted service interest is separate.
Does every action ask for approval?
No. The agent, permission mode, sandbox, and policies determine which actions need a decision. Broad permissions can allow tools automatically. Review those settings before starting work.
Which parts are open source?
The daemon, PWA, protocol, and both Go SDKs use MIT. The optional relay uses Business Source License 1.1 with a competitive-hosting restriction. Read the component license before offering a service.
What happens when I disconnect?
The agent can keep running. Reconnect to restore session state and request history from the daemon. Pending approvals still need a decision; losing a pairing credential can require pairing again.
Can I use it from a phone?
Yes. Serve the PWA over HTTPS and pair with your relay-connected daemon. HTTPS is needed for browser cryptography, camera scanning, and installation. Plain LAN HTTP is not equivalent to localhost.
Hosted service
Interested in hosted AgentD?
Self-hosting works without an account. Join the hosted-service waitlist if you prefer a managed option.