#Hub quickstart

From an empty Hub to an agent that starts when someone mentions it.

#1. Sign in

Open your Hub and sign in. Your connections, daemons, and projects all live inside one organization. Hosted and self-hosting cover how you get that first account.

#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 login https://your-hub.example.com
paseo hub connect

Approve the CLI login in the browser. connect selects that active login's origin and enrolls the daemon using the stored organization credential. The CLI login and daemon relationship remain separate identities. 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:

project: your-project

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.

              Call hub.finish_execution when the step is complete.
          - text: |
              <user-prompt>
              ${{ paseo.prompt }}
              </user-prompt>

project is the project slug from step 4. The deploy CLI reads it as deployment metadata; it does not affect workflow behavior. daemon is the normalized slug from step 3. cwd is a directory on that machine.

The prompt names the Hub tool the agent should call, and keeps the triggering message in its own <user-prompt> block. This step grants no reply capability, so it only finishes. Tell the agent which tool to call covers replying to a person.

If a prompt uses an include block, store the file below .paseo/partials/. The deploy CLI bundles only the files referenced by .paseo/hub.yml; nested include-looking text inside a partial is not resolved.

#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.

To inspect the authenticated organization's projects and deploy the file directly, run:

paseo hub projects
paseo hub deploy --dry-run
paseo hub deploy

--dry-run sends the same YAML, project, and partial bundle to Hub's validator without recording or activating a revision. Deploy reads .paseo/hub.yml in the current directory; pass a path for another file, or -p, --project <slug> to override the file's project metadata. Origin and credential precedence are in Configuration.

#7. Trigger it

Comment on an issue in that repository, from the account you listed in from_users:

@paseo have a look at this

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.

If nothing happened, Activity has the checklist.

Before enabling the example for broader use, read Hub security for trigger allowlists, host boundaries, provider-native controls, and output authority.