Files
paseo/public-docs/hub/index.md
T
Mohamed BoudraandGitHub 05a0cabc07 Deploy multi-file Hub workflows (#3128)
* feat(hub): deploy canonical workflow bundles

Keep CLI deployment aligned with Hub's authored bundle boundary so validation and activation receive the same deterministic source files. Public documentation now teaches that boundary as the only configuration format.

* test(hub): assert validation diagnostics directly

* refactor(hub): deepen HTTP client module

* feat(hub): validate named agent configurations

* docs(hub): align Claude mode example
2026-08-10 12:32:59 +02:00

2.1 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 you write

One project resource file names environments and complete agent configurations. Each discovered workflow file keeps one trigger beside its ordered steps:

.paseo/
├── hub.yml
└── workflows/
    ├── slack-help.yml
    └── partials/
        └── answer.md

Push the bundle, mention the bot, and an agent starts on your machine. Quickstart builds the first bundle; Workflows covers routing and provider-specific replies.

Reading order

  1. How it works
  2. Daemons
  3. Triggers
  4. Workflows
  5. GitHub access
  6. Configuration
  7. Security

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.

Where it runs

Everything on this page and the pages it links to works the same way on hosted Hub and on a Hub you run yourself under self-hosting.