feat: polish rolling TUI and release 0.18.0 - #21
Merged
Merged
Conversation
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.
Prepare chivgent 0.18.0 with a usable rolling TUI and the streaming performance improvements already merged in #20.
The TUI now shows a welcome panel, completes slash commands, ignores ordinary typing during runs while retaining Ctrl+C, handles Unicode display widths, redraws resized regions, and reports run outcomes. Prompts and status stay on stderr while final answers remain redirectable on stdout. An offline demo and bilingual usage documentation are included.
Validation: all 455 tests in 29 files pass, TypeScript check and build pass, npm package dry run succeeds, and the built CLI reports 0.18.0. Previous real-PTY verification covered resize, interruption, continued prompts, exit and redirected answers. No real DeepSeek API calls were made; this limitation is recorded in the release notes.
After CI passes, merge to main and dispatch the existing Publish npm package workflow, then verify the published artifact.