stable · Go + TypeScript
Pan
Self-hosted AI workspace — desktop agent with full PC control, web UI, native shell, and 3D engine.
Pan is the open-source umbrella for the Hermes Agent ecosystem — a self-hosted AI workspace that runs entirely on the operator's own machines. There is no Pan cloud.
Pan is composed of four sibling repositories, each shipped on its own cadence:
- pan-agent — Go binary that gives an LLM full PC control behind an explicit approval system. Every action that touches the filesystem, the network, or the keyboard is mediated. Single static binary, no daemon, no auto-update.
- pan-ui — TypeScript web UI for chat, skills, extensions, memory, profiles, and runtime controls. Currently the most-starred repo in the Pan family.
- pan-desktop — native Windows desktop wrapper for the Hermes Agent. A hard fork of
fathah/hermes-desktop(MIT), kept in sync with upstream where the changes are compatible. - pan-office — open 3D engine for Pan's spatial layer; experimental. Where the agent gets a body.
The agent itself — the long-running entity behind the conversation — lives separately as hermes-agent. Pan is the workspace; hermes-agent is the worker.
Design choices that probably won't change
- Approval-first. The agent never takes a destructive or external-network action without an explicit approval, even when the operator has granted "automatic" mode. Automatic mode lowers the friction; it does not eliminate the prompt.
- Single-operator. Pan does not multi-tenant. One Pan deployment serves one human. This is intentional: the security model and the audit trail collapse meaningfully when you try to share an agentic workspace across people.
- No telemetry. The binary does not phone home. There is no opt-in either — there is nothing to opt into.
Where it's headed
The roadmap, in priority order: stable v1 of the approval ledger; first-class scheduling (so the agent can do things while the operator is asleep); and the Linux desktop wrapper to follow pan-desktop.