IseeIsee
View as markdown

Hub

A daemon runs agents on one machine, for you. Isee 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

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

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. Sign in to start a free trial.