Repository navigation
Conversation
ashx-j
changed the base branch from
prototype/snooze-replies-base
to
prototype/github-snooze-upstream-base
October 9, 2026 11:39
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.
snooze a thread until new feedback arrives on a linked github pr or repository discussion. the server returns the thread to the inbox as unread without starting an agent turn, so waiting work can stay out of the inbox without choosing a timer.
both ignore existing feedback and activity from the signed-in github account. choose the conversation when several are linked. checks run about every two minutes, survive server restarts and respect the shared github quota limits. there is no deadline, and manual wake is available. web, desktop, mobile and agent tools use the same server behavior.
discussion support is limited to linking, listing, unlinking and opening github. the full discussion reader and editor have been removed. no posting, reactions, voting, label editing or category editing is included.
this version integrates upstream main at
101f8b2f55. github reads use the shared http api with pinned credentials and credential-aware caching. waiting text and manual wake use upstream's thread status line. explicit usage-limit recovery clears the github snooze suppression, while stale recovery commands remain rejected.evidence
captured through t3 code's built-in browser against isolated development state. the before image uses upstream's sidebar at
101f8b2f55; the after image uses this pr. the workspace and thread are synthetic, and github responses come from a local fixture. no github comment was posted and no agent turn was started.30-second selection and wake recording. idle time is omitted and labelled. full recording retains the normal background-check timing.
verification
20 focused test files pass across the batches below. they cover feedback filtering and pagination, credentials and quota pauses, restart recovery, stale actions, explicit recovery, undo, client state, menus, mobile list logic and mcp permissions. github responses are mocked. no provider or live github mutation is needed for these tests.
the new upstream thread-management fixture and the discussion mcp tests were rerun after integration fixes. package typechecks passed with
tsc --noEmit -p apps/server/tsconfig.json,tsc --noEmit -p apps/web/tsconfig.jsonandtsc --noEmit -p apps/mobile/tsconfig.json. formatting and lint passed for files changed against upstream, with lint warnings remaining.the integrated browser pass verified reply-snooze selection, the waiting state and return to the inbox as unread after mocked feedback. persisted state confirmed the reply notice and zero runs for the test thread. native mobile device verification has not been run. ci status must be checked on this head; queued or skipped jobs do not establish a passing implementation check.
upstream scope
fork prototype for ideas discussion #16459. explicit maintainer approval of the direction and scope has not yet been received.
the remaining behavior choice is unread-only failure handling. an account change or repeated unavailable reads ends the wait and returns the thread unread without showing a failure reason in clients. a github quota pause keeps the wait active.
gpt 6 astra and gpt 6.1 sol in codex through t3 code, writing on behalf of ash.