Jeremy Huang
Jeremy Huang
## Summary The TUI app layer is still carrying too much responsibility across `src/tui/app.rs` and related `src/tui/app/*` modules. State shape, turn execution, orchestration, remote/session flows, and UI coordination are still...
## Summary The server/runtime side still carries too much shared mutable state and too many wide function interfaces. There is also a lot of stringly typed protocol/state plumbing where typed...
## Summary `src/provider/mod.rs` has become a large mixed-responsibility abstraction. It currently combines provider trait definitions, routing/config logic, auth handling, failover behavior, pricing/model concerns, and shared HTTP helpers in one place....
## Summary Several rendering-heavy TUI files remain far above the intended size budget, especially `src/tui/ui.rs`, with additional large files like `src/tui/info_widget.rs`, `src/tui/markdown.rs`, and `src/tui/mermaid.rs` still carrying broad responsibilities. ## Why...
## Summary This issue tracks the most promising next steps for reducing jcode's private dirty memory footprint without changing provider-visible transcript semantics. I did a code and runtime audit focused...
## Summary Heavy active local client sessions still retain significantly more memory than expected because the same conversation can remain resident in multiple full in-memory representations at once: - `Session.messages`...
Follow-up extracted from closed-out review of PR #31. ## Goal Allow maintainers to run release build validation manually from a branch without publishing an actual tagged release. ## Scope -...
Split from #32.\n\nUse persisted customization records during update/reload flows and report the outcome clearly.\n\n## Scope\n- load active customization records during update/install flows\n- surface record metadata to the agent/update logic\n- report...
Split from #32.\n\nAdd the rich metadata needed so future agents can preserve user intent across updates.\n\n## Scope\n- capture original request / clarified goal summary\n- capture touched files/modules/symbols and patch/diff provenance\n-...
Split from #32.\n\nCreate the first implementation slice for durable self-dev customization records.\n\n## Scope\n- define a stored customization record schema\n- persist records to disk in a stable location\n- support identity, status,...