Repository navigation
/bug: a prefilled GitHub issue link, scrubbed; sends nothing (#26 item 6) - #30
Merged
Merged
Conversation
#26 item 6. `/bug [what happened]` (also `/feedback`) prints a report: incode's version, OS and architecture, the model and permission mode in force, and what was typed, then a link to a new issue on the bug form (.github/ISSUE_TEMPLATE/bug.yml) with those fields filled in. It sends nothing and opens nothing. The link is printed for the person to check and open: mcp_oauth::open_browser is for login addresses only. What was typed is redacted with the same patterns as stored agent errors (bearer tokens, key=value secrets, sk-, GitHub and Slack tokens, AWS keys, JWTs), and the home folder in a path becomes ~. No settings file, transcript or trace is read: none of them is redacted, and an issue is public. stderr_tail::redact is split out of clean: clean also cut each line to 512 bytes, for stored error output, which would have cut a description silently. clean is redact, then the cut, as before. The link is bounded by its ENCODED size (7000 bytes; GitHub refuses about 8 KB): a character count does not bound it, since `é` is six bytes percent-encoded. The description is cut to fit and says so; the terminal shows it whole. Tests: the fields land in the link; tokens and the home folder never reach the link or the text; long ASCII, accented, emoji and %&-heavy descriptions all fit; every field id sent is one the form has. Controls: with redaction off the bearer token leaks; with the bound off the link is not cut.
This was referenced Oct 22, 2026
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.
#26 item 6.
/bug [what happened](also/feedback) prints a report (version, OS/arch, model, permission mode, your words) and a link to a prefilled issue on the new bug form (.github/ISSUE_TEMPLATE/bug.yml).open_browserstays for login addresses only).stderr_tail::redact, split fromcleanso a long line is not silently cut), and the home folder becomes~. No settings, transcript or trace is read: none is redacted.éis 6 bytes percent-encoded; the terminal shows the description whole.Local (Windows): fmt clean; clippy only the existing
with_tool_serverwarning; bin tests 52 passed; lib 2175 passed, 1 failed:desktop::uia::tests::live::the_focused_window_can_be_walked. It walks whatever window has focus on the real desktop (its doc expects a terminal); here that was a browser page with an element scrolled to y=-9528, outside the bounds it allows. It is unrelated to this change; CI's Windows runner, with a terminal focused, runs it too and is its check.