Skip to content

feat(tui): say what to type when a permission or an input rule stops a run - #2

Merged
Yigtwxx merged 1 commit into
mainfrom
allow-hints
Sep 17, 2026
Merged

Yigtwxx merged 1 commit into
mainfrom
allow-hints

Conversation

@Yigtwxx

@Yigtwxx Yigtwxx commented Sep 17, 2026

Copy link
Copy Markdown
Owner

What this changes

The TUI's consent question names the four /allow answers instead of the terminal's [y] [a] [n] [never] keys; every "not permitted" line (TUI footer, /fetch block, CLI gate line and footer, the report) says which setting turns it on (/config set … in the TUI, proofpath config set … elsewhere); a page given where a post was expected says to paste the claim as text; /allow with nothing waiting says where the question appears. loading models … is a transient note in the TUI, taken back when the Verifying stage ends. The release workflow creates the GitHub Release for each tag from its CHANGELOG section (scripts/release_notes.py, gated before PyPI, idempotent); the README's screenshots are real runs with the raven.

Why

A user pasted a page URL, got a hint naming a command-line form inside the TUI, typed /allow, and got nothing to allow; a finished run still read "loading models …"; the repo had eight tags and no Releases. Design and decisions: docs/superpowers/specs/2026-09-17-permission-hints-design.md.

Checklist

  • ruff check and ruff format --check are clean
  • pytest passes (2080 passed, 1 skipped on macOS; mypy --strict clean)
  • Type annotations on every new function signature
  • No network access in unit tests
  • If a new reported state was added, spec section 15 is updated too (none added; state words unchanged, hints appended)
  • This change does not make the tool sound more confident than its evidence (every fact sentence stays first; the hint follows —)

🤖 Generated with Claude Code

https://claude.ai/code/session_017G4e6oqMrpALsNEQpHoopg

…a run

The consent question in the TUI names the four /allow answers instead of the
terminal's keys; every "not permitted" line says which setting turns it on
(/config set … in the TUI, proofpath config set … elsewhere); a page given
where a post was expected says to paste the claim as text; /allow with nothing
waiting says where the question appears. The "loading models …" note is
transient in the TUI and is taken back when the stage ends. The release
workflow now creates the GitHub Release for each tag from its CHANGELOG
section, gated before PyPI; the README's screenshots are real runs with the
raven.

Design: docs/superpowers/specs/2026-09-17-permission-hints-design.md

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017G4e6oqMrpALsNEQpHoopg
@Yigtwxx
Yigtwxx merged commit c5e8964 into main Sep 17, 2026
7 checks passed
@Yigtwxx
Yigtwxx deleted the allow-hints branch September 17, 2026 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant