Mohamed BoudraandGitHub
b1455fb4b3
Lead with the browser-to-CLI onboarding journey, document the generated starter bundle, and align guided setup with available Hub connections and daemon-reported runtime defaults.
2.3 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Hub | The layer above your daemons. Register them, give them capabilities, and share them with your team. | Overview | 60 | Hub |
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.
What lives in your repository
Guided setup creates a project resource file for environments and agents, plus one safe starter workflow:
.paseo/
├── hub.yml
└── workflows/
└── slack-help.yml
Guided setup deploys the bundle, and mentioning the bot starts an agent on your machine. Quickstart runs it end to end; the generated starter bundle shows what it wrote, and Workflows covers routing, prompt partials, and provider-specific replies.
Reading order
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.
Run Hub yourself
Start on your machine with the embedded database, then add PostgreSQL or a public deployment only when you need them. Self-hosting covers each step.
Hosted Hub uses the same projects, workflows, daemons, and activity model. New account registration is currently closed.