Mohamed BoudraandGitHub
9163aed3f1
* docs(hub): drop the manual auth secret from self-hosting setup Hub generates its authentication secret on first start and stores it in the database it is already using, so self-hosters no longer run openssl or carry PASEO_HUB_AUTH_SECRET between restarts. The variable stays as an override for deployments that must supply the secret from a platform secret store; Hub uses it without persisting it, so removing it resumes the stored value. Also corrects a claim that predates this change: rotating the secret does not invalidate execution credentials already issued. Hub verifies those against persisted hashes rather than the secret, so only browser sessions end. Documentation companion to https://github.com/getpaseo/hub/pull/50. * docs(hub): lead with the local guided setup * docs(hub): document XDG data directory * docs: make Hub self-hosting the quickstart
2.2 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
paseo hub init creates a project resource file for environments and agents, plus a safe starter workflow:
.paseo/
├── hub.yml
└── workflows/
├── slack-help.yml
└── partials/
└── answer.md
Deploy the bundle, mention the bot, and an agent starts on your machine. Quickstart runs the guided setup; Workflows covers routing 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.