Repository navigation
fix(discord-bot): stop echoing Grok runtime_info dumps - #481
Merged
Merged
Conversation
Grok extra ACP prompt parts persist as user-role text. The Discord bridge treated them as t3-client input and posted `<runtime_info>` / `<pull_request_linking>` as from unknown@unknown. Classify those harness envelopes as internal scaffolding and strip them from echoed text. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
Ship-gate vpr typecheck on fork/dev fails on a yield* union in ChromiumCookies and on electron-updater feed types leaking from updatesTestHarness. Annotate the key-resolution paths and keep feedUrls as unknown[]. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza
marked this pull request as ready for review
September 23, 2026 08:00
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.
Grok extra ACP prompt parts (
<runtime_info>,<pull_request_linking>) were persisted as user-role text. The Discord bridge treated that as t3-client input and posted the raw harness instructions as💭 from **unknown@unknown**.Classify those envelopes as internal scaffolding so they are not mirrored, and strip them from echoed text as a fallback.
Pushing this branch required the current
fork/devtypecheck unblocks: ChromiumCookies yield* union, updates harness feed types, HostPowerMonitor / NativeTelemetryClient Option.match.grok-4.6 / Grok harness
opened by Patrick Roza in chat thread Discord · Discord · T3 (.)