jb/paseo

Files

T

Mohamed BoudraandGitHub 1e03e2d120 docs(hub): clarify daemon slug references (#2952 )

Hub configuration resolves a normalized friendly slug to an immutable daemon ID. Document that model consistently so enrollment terminology matches hub.yml.

2026-08-06 22:00:06 +02:00

2.6 KiB

Raw Blame History

title, description, nav, order, category

title	description	nav	order	category
Hub quickstart	Sign in, connect GitHub, register a daemon, and get an agent starting from a mention.	Quickstart	61	Hub

Hub quickstart

From an empty Hub to an agent that starts when someone mentions it. Each step links to the page that covers it properly.

Open your Hub and sign in with the owner account created during deployment. Replace its temporary password when prompted. Your connections, daemons, and projects all live inside its organization.

2. Connect GitHub

Open Connections and connect GitHub. Choose the account or organization whose repositories you want to use.

The connection appears with a generated slug like yourname-github.

3. Register a daemon

On the machine that will run agents:

paseo hub connect https://your-hub.example.com

The CLI prints a verification code. In Hub, open Daemons → Register a daemon, enter the code, and choose a friendly slug. Hub normalizes Build Studio to build-studio. See Daemons.

4. Create a project

Open Projects → New project. On its Configuration tab, pick a repository and choose Use for configuration. Hub now reads .paseo/hub.yml from that repository's default branch.

5. Commit the configuration

Add .paseo/hub.yml to that repository:

environments:
  - name: dev
    kind: daemon
    daemon: my-daemon
    cwd: /Users/you/code/your-repo

triggers:
  - name: mention
    on: github.issue_comment
    max_runtime: 2h
    filters:
      repo: yourname/your-repo
      contains: "@paseo"
      from_users: [your-github-login]
    steps:
      - id: work
        environment: dev
        max_runtime: 90m
        idle_timeout: 10m
        agent:
          provider: codex
          mode: full-access
        prompt:
          - text: |
              Someone asked for help.
              ${{ paseo.prompt }}

daemon is the normalized slug from step 3. cwd is a directory on that machine.

6. Push

Push to the default branch. Hub fetches the file at that commit, validates it, and activates it. The Configuration tab shows the active revision and the last sync.

If the file is invalid, Hub records the failure and keeps the previous revision active.

7. Trigger it

Comment @paseo have a look at this on an issue in that repository, from the account you listed in from_users.

Open the project's Activity tab. You should see the event received and routed, and an execution in Executions. The agent itself appears in the Paseo app on that machine.

Nothing happened? Activity has the checklist.

2.6 KiB Raw Blame History