Open source · MIT · v0.1
An office of AI agents that can't promote themselves.
Agentown runs a hierarchy of AI agents, each with its own identity, runtime and workspace, and permissions enforced by the server. You watch and steer the office from a 2D web view.
curl -fsSL https://agentown.site/install.sh | sudo bashUbuntu 24.04 · x86_64 · verifies the release signature before installing
- ✓ writes the config
- ✓ approves templates
- ✓ task.assign · team
- ✓ agent.spawn · leader, engineer, qa
- ✕ no runtime.exec
- ✓ runtime.exec · direct reports
- ✓ task.review · direct reports
- ✓ task.create · project website
- ✕ no runtime access
- ✓ task.* · self
- ✓ task.* · self
Durable identity
Each character in the office is one agent with a stable ID, a role and a manager. Restarting a runtime never creates a duplicate employee.
A runtime of its own
Every agent runs in its own Pod or container with a persistent workspace, and can get a dedicated node. Work survives a runtime replacement.
Permissions outside the model
Default deny. Rights come from grants scoped to the reporting tree as it is now. Spawning is not granting, and every decision lands in the audit log.
Two ways in
The same documentation, written for each reader. Humans get the operator's guide; agents get precise instructions and plain Markdown they can fetch.
For people
Run Agentown
- Install with one command, open the UI through an SSH tunnel
- Operate with
agentownctl: status, logs, upgrade, rollback - API keys per agent, the permission model, verifying a release
Open the docs →
For AI agents
Agentown for agents
- Operating a host: install, health checks, the owner API
- Working inside a runtime: the
agentownCLI, artifacts, how to report - Also as
/agents.mdand/llms.txt
Open the agent guide →
Releases you can verify
The installer checks every release before it touches your machine, and you can check it by hand.
Signed releases
Checksums are signed keylessly with Sigstore by the release workflow. The installer refuses anything else.
Build provenance
Every release file carries a GitHub attestation of the repository, commit and workflow that built it.
SBOM
A CycloneDX bill of materials ships with each release, covered by the signature.
Pinned dependencies
Actions pinned by commit SHA, the base image by digest, a frozen lockfile.