* docs(hub): drop the manual auth secret from self-hosting setup Hub generates its authentication secret on first start and stores it in the database it is already using, so self-hosters no longer run openssl or carry PASEO_HUB_AUTH_SECRET between restarts. The variable stays as an override for deployments that must supply the secret from a platform secret store; Hub uses it without persisting it, so removing it resumes the stored value. Also corrects a claim that predates this change: rotating the secret does not invalidate execution credentials already issued. Hub verifies those against persisted hashes rather than the secret, so only browser sessions end. Documentation companion to https://github.com/getpaseo/hub/pull/50. * docs(hub): lead with the local guided setup * docs(hub): document XDG data directory * docs: make Hub self-hosting the quickstart
2.3 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Hub quickstart | Run Hub locally and answer a Slack mention with an agent on your machine. | Quickstart | 61 | Hub |
Hub quickstart
Run Hub locally, connect it to Slack without a public server, and answer a mention with an agent on your machine.
You need Paseo installed and running, Node.js, and a Slack workspace where you can create an app.
1. Start Hub
npx @getpaseo/hub
Open http://localhost:3000. Hub uses an embedded database by default, so this first run needs no database, environment variables, or Docker.
Create the operator account when Hub welcomes you.
2. Connect Slack
The next screen explains how to create the Slack app and gives you a manifest to paste into Slack. Keep Socket Mode selected. It connects out from Hub and does not need a public address or HTTPS.
Paste the App-level token and Bot token back into Hub, then choose Connect Slack. Invite the bot to the channel where you will use it:
/invite @Paseo
You can skip GitHub and Discord for now. Their setup remains available under Apps.
3. Initialize the project
From the repository where the agent should work:
paseo hub init
Choose Custom endpoint… and enter http://localhost:3000, then choose Slack. The guided setup:
- signs you in through the browser;
- connects the local Paseo daemon;
- uses the default project created during first-run setup;
- selects the connected Slack workspace and asks for your Slack username;
- writes
.paseo/hub.ymland.paseo/workflows/slack-help.yml; - validates the generated bundle and offers to deploy it.
Accept the default Deploy now? choice. The generated workflow accepts mentions only from the username you entered.
4. Mention the bot
Mention the bot in the channel:
@Paseo explain what this project does
Hub starts the agent on your daemon and posts its reply in the Slack thread. Open the project's Activity tab if nothing runs.
Hub keeps its local state in your user data directory (normally ~/.local/share/paseo-hub). Self-hosting covers PostgreSQL, public URLs, environment-managed apps, Docker, and cloud deployment. Configuration explains the generated files and manual deployment.