fix(discord-bot): make steernow resilient to empty/lagging server queue - #112
Merged
Merged
Conversation
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.
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
patroza
pushed a commit
that referenced
this pull request
Jul 27, 2026
…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>
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
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.
Summary
/agent steernowno longer treats a missing/lagging HTTP thread snapshot as an empty queue; it falls back to the in-memory Discord queued-prompt registry so just-parked 📥 follow-ups still flush./agent steerfor immediate mid-turn injection.Context
steernowwas only readingfetchThreadDetail().queuedMessages. That path soft-fails to empty when the snapshot is unavailable, which surfaced as "Nothing is queued on this thread" even when follow-ups were parked (or after a steer race left work on the server queue).Test plan
vp test run src/features/DiscordQueuedPromptRegistry.test.ts(8 tests)@Omegentparks with 📥, then/agent steernowinjects/agent steernowwith nothing parked shows clearer guidance including/agent steer