View as markdown

Hub quickstart

Run Hub on your machine, connect Slack over Socket Mode without a public server, and answer a mention with an agent in your repository.

You need Paseo installed and running, Node.js, and a Slack workspace where you can create an app.

1. Start Hub

Run Hub locally:

npx @getpaseo/hub

Open the printed address, normally http://localhost:3000, and create the operator account. The first run needs no external database, Docker, or environment variables. Hub creates an embedded database and your organization automatically.

Hub opens Home with a guided four-step setup: connect an integration, connect a daemon, create a trigger, and run it.

2. Connect Slack

Open Apps → Slack and keep Socket Mode selected. Socket Mode connects out from Hub and needs no public HTTPS address.

Follow the steps in Hub to create the Slack app from the generated manifest, create an App-level token with connections:write, and install the app. Paste the App-level token and Bot token into Hub, then choose Connect Slack.

Invite the bot to the Slack channel where you will mention it:

/invite @Paseo

You can set up GitHub, Linear, and Discord later under Apps.

3. Connect your machine

Open the repository where the agent will work, then log in to your local Hub:

paseo hub login http://localhost:3000

Approve the login in your browser. In the terminal, answer Yes to connect this daemon to Paseo Hub and Yes to allow Hub automations to run agents on it.

Execution permission defaults to no. If you answered no, grant it from the machine later:

paseo hub permissions grant hub.execute

4. Create the starter trigger

Use a repository directory whose absolute path starts with /. Hub rejects Windows drive paths such as C:\work\project when paseo hub init validates the trigger. See target and worktree.

From that repository directory, generate and deploy a starter trigger.

paseo hub init

Choose your local Hub endpoint (http://localhost:3000) and select your Slack connection if prompted. Setup asks three questions:

PromptValue to provide
Starter agent provider, model, and modeAn enabled provider on your daemon with a selectable model and at least one execution mode (such as Claude, Codex, or OpenCode).
Your Slack member IDYour Slack ID, such as U01234567. Only listed users can trigger the bot.
Deploy now?Yes, to validate and install the trigger in Hub.

Providers that advertise zero execution modes (such as Pi) are skipped by paseo hub init, but you can configure them in the Hub dashboard or in .paseo/triggers/*.yml and deploy with paseo hub deploy.

See Find your Slack IDs to copy your member ID.

Setup validates the agent configuration against your connected daemon, writes .paseo/triggers/slack-help.yml, and deploys it. If you skip deployment during setup, run paseo hub deploy from the repository root when ready.

You can also create and edit triggers directly in the Hub dashboard under Triggers.

5. Mention the bot

In the Slack channel you invited the bot to, send a mention:

@Paseo summarize this repository

Hub starts the agent on your daemon and posts the reply in the Slack thread. In Hub, open Activity to see the run status. When Hub runs behind HTTPS, replies also include an Open in Paseo link so organization members can jump straight to the live session.

If nothing runs, check Activity to tell a filtered mention from an unrouted event.

Next

  • How Hub works explains integrations, daemons, triggers, and continuation.
  • Triggers lists all event sources, including GitHub, Linear, schedules, and webhooks.
  • Generated starter trigger walks through .paseo/triggers/slack-help.yml.
  • Hub security explains host boundaries and safe allowlists before you add more users or permissions.

Hub stores local data under ~/.local/share/paseo-hub by default. See Self-hosting when you are ready for PostgreSQL or a public HTTPS deployment.

Sponsors

⌂ 换网址