MoonshotAI / MoonshotAI/kimi-code
Input box should stay pinned to the bottom while scrolling (currently scrolls away)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Problem
In the interactive TUI, the input box does not stay docked at the bottom of the terminal. When a conversation produces long output and I scroll up to review earlier messages, the input box scrolls out of view along with the content. I then have to scroll all the way back to the bottom before I can continue typing.
This makes reviewing context and entering follow-up messages very painful.
Environment
- OS: macOS
- Terminal: Ghostty
- Kimi Code version: 0.26.0
- Model: deepseek-v4-pro (via OpenAI-compatible provider)
Expected behavior
The input box (and ideally the status line / context info above it) should be pinned to the bottom of the window, with only the conversation area scrolling above it — like Claude Code and most chat UIs.
Steps to reproduce
- Launch
kimi. - Run a task that produces long output (e.g. read multiple files / run tests).
- Scroll up to review earlier content.
- The input box is no longer visible and cannot be typed into until you scroll back down.
Related
- #875 — same request; proposes a
tui.tomloption likefixed_input_region = true - #891 — same symptom report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by launching kimi and reproducing the behavior with a task that produces long output, then inspect the interactive TUI layout and scrolling behavior. Keep the conversation area scrollable while the input box and, if supported by the layout, the status/context line remain visible at the bottom during upward scrolling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100