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
Fix TUI prompt corruption by using Log instead of UI.println (#180)
* fix: replace UI.println with Log in engine bootstrap to prevent TUI prompt corruption
Engine bootstrap messages (downloading uv, engine ready, etc.) were written via
UI.println() which writes to stderr. In TUI mode the framework captures stderr,
causing garbled text like "readyltimate-engine 0.4.0..." in the prompt input area.
Switched all status messages in engine.ts to use Log.Default.info() which routes
to the log file instead of stderr, keeping the TUI display clean.
https://claude.ai/code/session_01MBVNhRX6XKTHqtZ6zS1i6w
* chore: update bun.lock after dependency install
https://claude.ai/code/session_01MBVNhRX6XKTHqtZ6zS1i6w
* fix: replace console.log/error with Log.Default in TUI code to prevent prompt corruption
All console.log and console.error calls in TUI components and bridge
client wrote to stdout/stderr, which the TUI framework captures and
renders as garbled text in the prompt input area. Replace with
Log.Default.info/error which writes to the log file instead.
Affected: route navigation, bootstrap, theme resolution, route changes,
clipboard detection, session creation, auto-enhance, MCP toggle,
workspace creation, and altimate-engine stderr.
https://claude.ai/code/session_01MBVNhRX6XKTHqtZ6zS1i6w
* fix: resolve code review findings for TUI prompt corruption PR
- Move "workspace created" log inside success branch (was logging on failure)
- Use structured metadata in `client.ts` stderr handler instead of template string
- Downgrade noisy diagnostic logs to `debug` level (clipboard, theme, route, sync)
- Replace platform-dependent binaries (`echo`, `python3`, `tar`) with `process.execPath`
in tests for CI portability
- Replace hollow Log test with real `Log.init({ print: false })` integration test
- Use regex matching instead of brittle exact-string matching in log assertion tests
- Add source-scanning regression tests for TUI files and `client.ts` to prevent
future `console.log/error` regressions
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments