Mohamed Boudra
c54f20e53e
Hosted Hub replaces its automatic trial with a real Free plan, so the pricing section becomes three columns: Self-hosted, Free, and Pro. Both hosted columns render entirely from `GET /api/billing/plans` — name, price, the `included` figures, and the catalog's feature prose — because those figures are derived from the entitlement template the instance enforces, so nothing on this page can drift from the limit a customer actually gets. The parser requires both slugs and the new `included` object and throws on anything else. The page already degrades to "temporarily unavailable" when the loader throws, so a strict boundary costs a fallback we have rather than a wrong number we would ship. This is also why the change must not merge before the Hub side deploys: against today's API the section renders that fallback. Public docs follow the two Hub changes: Free replaces the trial and points at /hub for the figures Stripe metadata now owns; sign-in lands on Home with its four-step checklist; `hub.execute` gets the grant command it needs; and trigger authoring documents that the agent is validated against the target daemon at save, which needs that daemon connected and accepts Claude, Codex, and OpenCode only.
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.
- Triggers you can keep in a repository and deploy from the CLI.
- 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 one self-contained starter trigger:
.paseo/
└── triggers/
└── slack-help.yml
The file names the app connection, allowed user, daemon, working directory, agent runtime, prompt, and outputs. Setup validates it and asks whether to deploy. Mentioning the bot then starts an agent on your machine. Quickstart runs it end to end; the generated starter trigger shows what setup wrote.
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 triggers, daemons, and activity model. Create a free account; it needs no card and does not expire.