feat(discord): Discord bot#80
Draft
patroza wants to merge 4 commits into
Draft
Conversation
patroza
added
the
OVERLAY
patroza
changed the title
This was referenced Jul 26, 2026
patroza
force-pushed
the
fork/changes
branch
2 times, most recently
from
July 26, 2026 08:56
79176b5 to
d526bc4
Compare
This was referenced Jul 26, 2026
patroza
force-pushed
the
fork/discord
branch
3 times, most recently
from
July 26, 2026 10:37
70cf79c to
e817ff5
Compare
patroza
force-pushed
the
fork/discord
branch
9 times, most recently
from
July 26, 2026 17:45
acf4763 to
b578fce
Compare
patroza
force-pushed
the
fork/discord
branch
2 times, most recently
from
July 26, 2026 19:19
452dcd5 to
7fc61e2
Compare
patroza
force-pushed
the
fork/discord
branch
2 times, most recently
from
July 26, 2026 19:29
0c3be12 to
3387d32
Compare
patroza
force-pushed
the
fork/discord
branch
3 times, most recently
from
July 27, 2026 05:55
a416a75 to
6ae78bd
Compare
2 tasks
patroza
force-pushed
the
fork/discord
branch
2 times, most recently
from
July 27, 2026 07:10
b4fc1d3 to
c07b309
Compare
patroza
force-pushed
the
fork/discord
branch
2 times, most recently
from
July 27, 2026 13:13
c31525c to
9ba3353
Compare
…och (#100) When a queued follow-up starts, Discord clears the live tip for a new Working ack. If the prior turn's real answer only lived in that tip, it vanished. Promote substantial tip body to a durable final first. Pairs with server turnId rebind fix for the same race.
…ue (#112) steernow was reporting "Nothing is queued" whenever the HTTP thread snapshot was missing or lagging, even when Discord still had parked follow-ups in the in-memory registry. Prefer the server queue, fall back to the local registry, register failed mid-turn steers for later flush, and clarify the empty-queue reply so users know to use /agent steer. Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
… queue (#114) connectPrepared's parameter was named httpBaseUrl, so the assignment that should record the connected base URL only mutated the parameter. Outer connection state stayed null, fetchThreadDetail always short-circuited, and /agent steernow reported "thread snapshot unavailable" while WS steering from desktop still worked. Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Managed integration overlay
fork/changesfork/discordThis one-commit overlay owns the complete end-to-end Discord integration:
This PR intentionally remains open and draft. Do not merge it. Update
fork/discorddirectly,or start a reviewable child PR with:
The stack workflow rebases this branch and composes it into
fork/integration.