Mohamed BoudraandGitHub
dfd18a44a7
* feat(website): nest docs pages under landable groups The docs sidebar could already render groups from subdirectories in public-docs, but nothing used it because every doc was a flat file, and two things stopped it being usable. A group had no page of its own, so its label was only a toggle and its name came from the directory name via formatLabel. A directory's index.md now supplies the group's label, order, and href, which makes the group landable and lets the label be authored rather than derived. Categories and top-level directories named the same thing, so a categorised doc at hub/index.md produced a group nested inside its own category. Only directories below the top level become groups now. Also fixes two behaviours in the sidebar: - The open/closed effect assigned containsActive on every change, so a group you expanded to browse collapsed the moment you navigated anywhere else. Navigating in now opens a group and navigating away leaves it alone. - The sidebar scrolls independently of the page and never scrolled the active entry into view, so loading or refreshing a page far down the list left the sidebar parked at the top with no visible position. The group row is a single target: it navigates and expands, and collapses when clicked again from the page it points at. A separate chevron button would put two actions a few pixels apart. * docs(hub): document Hub Adds a Hub section covering what it is, how it works, daemons, triggers, configuration, activity, and the two ways to run it. The section separates using Hub from running it. Overview, quickstart, daemons, triggers, and configuration hold regardless of who operates the deployment; the self-hosting branch owns deploying the service and creating the GitHub, Slack, and Discord apps it talks to. That split falls on a real seam, because those apps are exactly what a hosted Hub would own on your behalf. Hosted is a placeholder until it ships. Each provider gets a trigger page carrying its events, filter semantics, and the full paseo.event.* reference for the data a prompt can read. That data is the thing a config author actually needs and the thing they cannot get from anywhere else. Every YAML block was parsed against the Hub config schema rather than eyeballed, which kept several plausible-looking things out of the docs: worktree prNumber takes a literal number and not a merge variable, only daemon environments run today, and github.push has no actor so it can never satisfy the required from_users filter. Troubleshooting moves to order 90 so it stays last. * refactor(website): let the active docs entry scroll itself into view The layout queried the sidebar for the active entry after every navigation, which coupled it to when that entry mounts. A link inside a collapsed group only mounts once the group's own effect opens it, so the query could run against a DOM that does not contain it yet. Moving the scroll to the entry removes the ordering question rather than answering it, and drops the ref and the cross-component query. Reported by Greptile on #2864. The failure it described does not reproduce: navigating from a page outside a collapsed group into one of its children still scrolls correctly, verified with the group confirmed collapsed and the sidebar forced to the top. The coupling was real even though the bug was not. * docs(hub): stop listing BETTER_AUTH_URL as required It falls back to PASEO_CLOUD_PUBLIC_URL, so a deployment that sets the public origin already has a correct auth base URL. Listing it as required made the Fly recipe look incomplete when it was not. Moved to optional with its default, and recorded what actually breaks without BETTER_AUTH_SECRET: the auth routes close and nobody can sign in. Reported by Codex on #2864, which read the same inconsistency the other way round and proposed adding the variable to the Fly example. * docs(hub): attach a database in the Fly recipe The Fly section showed inline config and a secrets command, neither of which supplied DATABASE_URL. It defaults to localhost:5432, which on Fly reaches nothing, so the documented deployment could not start. fly postgres attach sets DATABASE_URL as a secret, so the step is the attach itself rather than another variable to copy. Reported by Codex on #2864. * docs: align Hub self-hosting contract
3.9 KiB
3.9 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Discord triggers | Discord mentions as Hub triggers, snowflake filters, thread context, and the full paseo.event.discord data reference. | Discord | 67 | Hub |
Discord triggers
Events
on |
Fires when |
|---|---|
discord.mention |
The bot is mentioned in a guild channel or thread |
Mentioning a role the bot holds counts as mentioning the bot.
Filters
Discord filters take snowflake IDs. Turn on Developer Mode in Discord's advanced settings, then right-click a channel or user to copy its ID.
filters:
guild: "123456789012345678"
channels: ["234567890123456789"]
from_users: ["345678901234567890"]
Quote them. Unquoted snowflakes parse as numbers and lose precision.
from_usersmatches the author's user id.guildis resolved to the connection on activation.channelsmatches the channel the message was posted in; in a thread, the thread's parent channel counts.patternmatches the start of the text after the mention.
Replying
allow_outputs:
- type: discord.reply
One plain-text reply per execution, in the triggering thread or channel.
Repository access
A Discord trigger has no implicit GitHub credential. Name the connection you want:
env:
GH_TOKEN: ${{ paseo.connections.acme-github.token }}
Hub will not guess between several GitHub installations.
Data reference
The triggering message is paseo.event.discord.trigger_message:
| Path | Value |
|---|---|
id |
Message snowflake |
content |
Raw text, including the mention |
body |
Text with the mention stripped, usually what you want |
url |
Canonical message link |
author |
Author identity, including the user id |
channel |
Channel identity |
thread |
Thread identity, or null outside a thread |
created_at |
Message creation time |
attachments |
Typed list, see below |
referenced_message |
Identity of a replied-to message, or null |
Each attachment has id, filename, url, content_type, and size. A referenced_message carries id, channel_id, and guild_id, without the message content.
Also available: paseo.event.discord.event_type and paseo.event.discord.guild.id.
Thread context
In a thread, paseo.event.discord.trigger_thread_context.messages holds the preceding messages, oldest first, never including the triggering message. Each entry exposes the same identity, content, author, channel, creation time, attachment, and reference fields as trigger_message.
This is how you give an agent the conversation rather than one line:
prompt: |
Thread so far:
${{ paseo.event.discord.trigger_thread_context.messages }}
Latest request:
${{ paseo.event.discord.trigger_message.body }}
Outside a thread the list is empty.
Example
triggers:
- name: discord-fix
on: discord.mention
environment: dev
filters:
guild: "123456789012345678"
channels: ["234567890123456789"]
from_users: ["345678901234567890"]
agent:
provider: codex
mode: full-access
env:
GH_TOKEN: ${{ paseo.connections.acme-github.token }}
allow_outputs:
- type: discord.reply
prompt: |
${{ paseo.event.discord.trigger_message.body }}
Context: ${{ paseo.event.discord.trigger_message.url }}
Reply in the thread when you're done.