intendant.devalpha

Give an AI agent a full machine — under your oversight

Intendant is an open-source operating environment for autonomous AI agents: a shell, files, a display it can see and control, voice, and phone calls — with layered human supervision. It runs its own agent loop, supervises Codex, Claude Code, Kimi Code, and Pi as managed backends, and is portable across OpenAI, Anthropic, and Gemini. The agent's machine can run macOS, Linux, or Windows. Route discovery needs only this browser tab; control uses local presence or a browser enrolled for independently verified direct mTLS by a trusted daemon owner. No signed/notarized native release exists for this alpha.

Open Connect Install a daemon

Stand up a daemon in a few minutes

Four answers about the machine the agent will live on, and the exact command appears. You can discover it from your phone without a separate app; controlling the daemon still requires trusted certificate or profile enrollment.

OS on the agent's machine?
What kind of machine?
What will fuel it?
Keep working with your browser closed?
fresh box — sh 
$ curl -fsSL https://github.com/intendant-dev/Intendant/releases/latest/download/install.sh | sh -s -- --connect https://intendant.dev --service

    1Install One command installs the daemon. The script is a release-pinned GitHub asset with its hash in a public transparency log — this service only points at it.
    2Link Enter its twelve-word one-time claim code to add the route to your account. This grants no access.
    3Establish owner Use the machine's local console or independently verified direct mTLS to establish root outside hosted-origin JavaScript. No signed/notarized native release exists for this alpha.
    4Fuel Configure credentials from a trusted daemon surface. Connect implements blind account-vault storage but serves no vault client or daemon-delivery bridge in this build.

    New here? Sign in to link the route for discovery. The link does not create a daemon principal or grant; establish access from a trusted local or independently verified direct-mTLS surface. This hosted build remains discovery-only.

    What's in the box

    A real desktop, watched

    The agent gets a display it can see and drive — a browser, a terminal, whatever the task needs — and an authorized dashboard streams it live over WebRTC. Input stays yours to share: take control at any moment, annotate what you see, record what happened. Autonomy is a dial, approvals are explicit, and every command, diff, and decision is logged and replayable.

    Bring your own agent

    Codex, Claude Code, Kimi Code, and Pi run as managed backends — under the same oversight, autonomy dial, and session logging as the native agent loop.

    Every agent, one canvas

    Station renders the whole machine live — sessions, approvals, context budgets, changes, and worktrees orbiting one WebGPU canvas. The same daemon is operable from the CLI and MCP, and a glance away from your phone in an enrolled browser.

    Your keys stay yours

    Sealed vaults, expiring API-key leases, and client egress are available on authorized daemon sessions. Connect can store an opaque account-vault envelope, but there is no shipped client or daemon bridge for it — this directory cannot fuel a daemon or relay a provider call. Local .env credentials remain supported, and full-credential OAuth leases temporarily materialize private auth files.

    Multiple trusted interfaces

    Use the web dashboard for visual control, CLI or MCP for automation, and live voice or phone for conversation. A remote browser enrolled for direct mTLS by a trusted owner runs the web client there, phone included, without a separate app install; that remote browser still needs certificate or profile enrollment. Installing a client certificate or profile is a real enrollment step, not a zero-install claim.

    A fleet, not a box

    Daemons federate: shared displays, cross-machine sessions, and organization-signed access — all enforced locally by each daemon's own IAM, never by this service.

    Why “Intendant”

    In a theater, performers play and conductors orchestrate — the Intendant runs the house: who gets the stage, which productions run, on whose authority, with the books open. Here agents perform, orchestrators conduct (Codex, Claude Code, Kimi Code, and Pi as guest conductors), and the Intendant runs the house and answers to you — houses federate, companies tour on signed contracts, house rules always win.

    Built to be distrusted

    The daemon is the authority mint

    Connect is trusted for the code it serves, availability, accounts, routes, fleet metadata, and optional push delivery. Its rendezvous protocol cannot mint a daemon grant, and the install scripts are release-pinned GitHub assets with their hashes in a public transparency log — this service at most redirects to them. Malicious hosted code can still misuse Connect account or decrypted browser state available after a gesture. You can read exactly what it can and cannot do, or run your own.

    The sandbox never holds keys

    Inside each daemon, the sandboxed process that executes commands never sees an API key, and the process that talks to model providers never executes commands. A hijacked conversation can't steal credentials; a hijacked shell can't phone home through the model — by construction, not by policy.