Skip to content

Bring back the Discord assistant on Houston, confirmed by mention - #57

Open
matthewp wants to merge 1 commit into
mainfrom
discord-assistant-houston
Open

matthewp wants to merge 1 commit into
mainfrom
discord-assistant-houston

Conversation

@matthewp

@matthewp matthewp commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Brings back the Discord assistant from Discord assistant: ask Factory about the codebase, then file issues or open PRs from a thread #54 (reverted in Revert the Discord assistant until Message Content is approved #56) and runs it on Houston's bot, which already has the Message Content intent, so the assistant reads the whole thread. Factory's existing advisory triage also moves to Houston once its token is swapped in, keeping everything on one bot.
  • Houston's interactions endpoint already serves its own slash commands and buttons, so the assistant uses no buttons and no interactions endpoint. A maintainer confirms a draft issue or PR plan by mentioning the bot ("@houston file it", "@houston open the PR"). The agent calls a new confirm_proposal tool. Trusted workflow code then checks the proposal belongs to the thread and is still pending, and claims it once in the thread coordinator. Only after that does it file the issue or queue the PR job.
  • Only Core and Maintainer can trigger it (role check on every mention), and only the mention itself can confirm, never other text in the thread.
  • Houston has no persistent Gateway connection, and its weekly stats job only connects briefly, so Factory's Gateway connection doesn't conflict with it. Factory never handles Houston's interactions.
  • Sets the server and role ids in wrangler.jsonc, and adds a v9 migration recreating the Durable Object classes that v8 deleted.

Testing

Docs

  • README documents confirmation by mention and the bot requirements (Message Content, permissions); the interactions endpoint setup is gone.

… by mention

Restores the assistant reverted in #56 and runs it on Houston's bot, which
has the Message Content intent. Houston's interactions endpoint serves its
own commands, so proposals have no buttons: a maintainer confirms one by
mentioning the bot, the agent calls confirm_proposal, and trusted code
claims the proposal once before filing the issue or queuing the PR.

Adds a v9 migration recreating the Durable Object classes v8 deleted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant