You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ship v0.8.59 as a stabilization + maintainer-queue release after v0.8.58. The release must include the TUI mouse-report input leak fix observed on macOS, then triage the newly tagged maintainer-request PRs and issue mentions before cutting the release.
Release-blocking fix: raw SGR mouse reports leak into composer
Observed failure: the composer fills with raw mouse-coordinate tails such as:
;76;20M35;74;22M35;73;23M...
Likely root cause: the terminal/crossterm parser can consume the ESC[< prefix from SGR mouse reports and deliver only the coordinate tail as ordinary Char key events. The existing composer sanitizer stripped these sequences only when app.use_mouse_capture was true. That is not sufficient because a killed/crashed/orphaned TUI, focus recovery race, or host terminal bug can leave mouse-reporting mode active even when the next App instance did not request mouse capture.
Local patch exists on branch fix/tui-mouse-report-leak:
crates/tui/src/tui/app.rs
make strip_raw_mouse_reports_from_input() run defensively regardless of use_mouse_capture
add regression tests for full SGR reports and tail-only bursts when mouse capture is disabled
preserve normal coordinate-like text such as Size 12;34M
Acceptance:
Land the fix/tui-mouse-report-leak patch or equivalent.
Composer strips full SGR mouse fragments like [<35;44;18M even when use_mouse_capture = false.
Composer strips tail-only leaked bursts like ;76;20M35;74;22M35;73;23M... even when use_mouse_capture = false.
Composer keeps legitimate text like Size 12;34M.
Add/keep tests covering composer_strips_* and composer_keeps_* cases.
Verify cargo test -p codewhale-tui composer_strips.
Verify cargo test -p codewhale-tui composer_keeps.
Mentioned issues and unread maintainer-attention threads tagged for v0.8.59
Already captured in the earlier mention sweep:
Add to acp-registry #1447Add to acp-registry — new concrete blocker: ACP registry requires authMethods with at least one agent or terminal; CodeWhale currently returns empty authMethods from crates/tui/src/acp_server.rs.
SSE多智能体并行在windows11下依旧45s超时,并且还出现了UI错乱的问题 #1679SSE多智能体并行在windows11下依旧45s超时,并且还出现了UI错乱的问题 — Windows sub-agent timeout/UI corruption; latest mention asks for compatibility around failed sub-agent handoff and /compact failing while a sub-agent is present.
Added from unread GitHub mention notifications on 2026-06-11:
During local diagnosis, an orphaned /Users/hunter/.local/bin/codewhale-tui process was found under PID 5157 with revoked stdio and 100% CPU. That supports the defensive sanitizer change: terminal/reporting state can outlive the App state that originally enabled it.
Goal
Ship v0.8.59 as a stabilization + maintainer-queue release after v0.8.58. The release must include the TUI mouse-report input leak fix observed on macOS, then triage the newly tagged maintainer-request PRs and issue mentions before cutting the release.
v0.8.58 release commit timestamp checked locally: 2026-06-10 23:06:44 -0700.
Release-blocking fix: raw SGR mouse reports leak into composer
Observed failure: the composer fills with raw mouse-coordinate tails such as:
Likely root cause: the terminal/crossterm parser can consume the
ESC[<prefix from SGR mouse reports and deliver only the coordinate tail as ordinaryCharkey events. The existing composer sanitizer stripped these sequences only whenapp.use_mouse_capturewas true. That is not sufficient because a killed/crashed/orphaned TUI, focus recovery race, or host terminal bug can leave mouse-reporting mode active even when the next App instance did not request mouse capture.Local patch exists on branch
fix/tui-mouse-report-leak:crates/tui/src/tui/app.rsstrip_raw_mouse_reports_from_input()run defensively regardless ofuse_mouse_captureSize 12;34MAcceptance:
fix/tui-mouse-report-leakpatch or equivalent.[<35;44;18Meven whenuse_mouse_capture = false.;76;20M35;74;22M35;73;23M...even whenuse_mouse_capture = false.Size 12;34M.composer_strips_*andcomposer_keeps_*cases.cargo test -p codewhale-tui composer_strips.cargo test -p codewhale-tui composer_keeps.cargo build -p codewhale-tuiandcargo fmt -p codewhale-tui --check.New open issues since v0.8.58
v0.8.57 fatal_bug_report_runtime_prompt_autonomous_loop— safety/runtime bug; treat as release-blocking until explicitly fixed or deferred with rationale.land— bug issue currently has template body only; needs title/body cleanup or closure as insufficient repro.Is it necessary to generate a .codewhale in every folder?— workspace hygiene enhancement; decide whether v0.8.59 should stop eager.codewhalecreation or defer.Maintainer review requests tagged for v0.8.59
Clean / likely mergeable after review:
feat(i18n): localize ToolFamily labels (10 MessageIds)— CLEAN; contributor rebased and explicitly asked for merge.fix(tools): apply strict mode per schema— CLEAN; likely related to v0.8.58: Tool-schema sanitization hardening — land sanitize_for_responses, per-tool strict mode, preserve dropped constraints #3017; review test caveats and merge if acceptable.feat(cli): track provider source and customize unsupported TUI errors— CLEAN.feat(config): implement verbosity settings with normal and concise modes— CLEAN.docs(prompt): clarify Constitution trust framing— CLEAN.refactor(config): extract provider metadata into data-driven registry— CLEAN.feat(voice): add /voice slash command for speech-to-text input— CLEAN; decide whether this belongs in a stabilization release or should wait.feat(tui): dispatch hotbar slots from number keys— CLEAN; decide whether this belongs in a stabilization release or should wait.Blocked / needs owner action before merge:
fix(update): detect legacy deepseek/deepseek-tui binary and print migration instructions— BLOCKED.docs: add Upgrading from deepseek-tui section to README— BLOCKED.Dependabot review requests tagged for v0.8.59:
chore(deps): bump reqwest from 0.13.1 to 0.13.4— CLEAN.chore(deps): bump rustls from 0.23.36 to 0.23.40— CLEAN.chore/deps): bump clap_complete from 4.5.65 to 4.6.5— CLEAN.Mentioned issues and unread maintainer-attention threads tagged for v0.8.59
Already captured in the earlier mention sweep:
Add to acp-registry— new concrete blocker: ACP registry requiresauthMethodswith at least oneagentorterminal; CodeWhale currently returns emptyauthMethodsfromcrates/tui/src/acp_server.rs.SSE多智能体并行在windows11下依旧45s超时,并且还出现了UI错乱的问题— Windows sub-agent timeout/UI corruption; latest mention asks for compatibility around failed sub-agent handoff and/compactfailing while a sub-agent is present.Added from unread GitHub mention notifications on 2026-06-11:
如何强制让模型推理的时候是特定语言的思考链路,而不是默认英文。Two issues occur during first-time initialization and configurationbug: thinking collapse - multiple root causes causing thinking blocks to freeze, truncate silently, or drop reasoning_contentAdd vision_model registration & vision tools for image input supportword wrap报错:Stream stalled: no data received for 90s, closing stream。Language has been configured to Chinese, but "thinking" outputs are still in EnglishThere still seems to be some problems with cache hits缓存命中方面似乎还是有些问题feat(execpolicy): add typed persistent permission rulesAlways stuck, I don't know the status of task!deepseek-linux-x64 0.8.28 火绒报告病毒:Trojan/Linux.Agent.bpProposal: universal PreToolUse/PostToolUse hook layer for Cancel/Pause/Resume across all action typesClipboard copy silently fails on non-wlroots Wayland compositors (e.g. niri)Feature Request: Provider fallback chain — auto-switch on API failureUI refactor neededRefactor command dispatch from monolithic match to modular strategy patternLeft out of the v0.8.59 sweep because they are explicitly future-release or roadmap items already tied to v0.9.0: #471, #472, #473, #474, #475, #476, #477, #478, #479, #481, #534, and #582.
Older open PRs with recent activity to decide before release
feat(prompt): exclude Calm personality overlay from default prompt path (#2953)— DIRTY.feat(bench): improve cli-compare harness with real Harbor integration— CLEAN, but not part of the maintainer-request sweep.Suggested release policy
Notes
During local diagnosis, an orphaned
/Users/hunter/.local/bin/codewhale-tuiprocess was found under PID 5157 with revoked stdio and 100% CPU. That supports the defensive sanitizer change: terminal/reporting state can outlive the App state that originally enabled it.