Hub
A daemon runs agents on one machine, for you. Paseo Hub is the layer above your daemons. You register your daemons with it, and it gives them capabilities they do not have on their own.
Hub
┌─────────┼─────────┐
▼ ▼ ▼
laptop devbox build server
What that gives you today:
- Agents that start on their own, from activity in GitHub, Slack, and Discord.
- Configuration that lives in a repository and deploys when you push.
- A record of everything that arrived, what it matched, and what ran.
- One place for your team to see all of it.
Your daemons keep running agents where they always did. Hub decides when to ask them to.
How it fits together
An organization holds your connections to GitHub, Slack, and Discord, and your registered daemons. Projects sit inside it, and each project has its own configuration.
organization
├── connections
├── daemons
└── projects
A project is one set of environments and triggers. Split your work into projects the way you already split it in your head: one per product, per team, or per repository. Connections and daemons are shared across all of them, so a new project does not mean connecting GitHub again.
How Hub works covers this properly.
Reading order
Quickstart goes end to end if you would rather start by doing.
If a workflow accepts requests from GitHub, Slack, Discord, or the API, read Hub security before giving an agent access to a working directory or output capability.
Running it
Two ways: hosted or self-hosted. Everything above is the same either way.
Once Hub is running, approve durable CLI access and inspect the organization:
paseo hub login https://hub.example.com
paseo hub projects
The login is scoped to that exact Hub origin. Use it to connect a daemon or deploy configuration without copying an API key into each command.