MoonshotAI / MoonshotAI/kimi-code

Feature request: pin input line and attached UI elements to the bottom of the terminal window

Open
#875 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

Currently, as context grows and the chat scrolls, the command input line and the panels attached to it (for example, the active plan shown above the input) move up together with the rest of the content. This makes it hard to keep track of the current plan or context status without manually scrolling back down.

Request

Pin the following elements to the bottom of the terminal window:

  • The command/input line.
  • Anything directly attached above it (e.g., the active plan, current step, or context status).
  • Anything directly attached below it (e.g., hint text, keybindings, or mode indicators).

The main conversation/context area should scroll above this fixed bottom region, similar to how most modern chat clients and terminal multiplexers behave.

Example layout
┌─────────────────────────────────────┐
│ [scrollable conversation/context]   │
│                                     │
│ ...                                 │
│                                     │
├─────────────────────────────────────┤  ← fixed separator
│ context: 66.8% (175.1k/262.1k)      │
│ Plan: implement auth middleware     │
│   Step 3 of 5: write tests          │
├─────────────────────────────────────┤
│ > _                                 │  ← input line always here
├─────────────────────────────────────┤
│ Ctrl+S submit · /help · /plan       │
└─────────────────────────────────────┘
Why this helps
  • The current plan and context status remain visible at all times.
  • Users always know where to type without chasing the input line.
  • Less vertical scrolling during long agent turns.
Optional setting

A TOML option such as tui.toml:

[tui]
fixed_input_region = true

would let users keep the current behavior if they prefer it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the terminal UI entry point that renders the conversation, input line, and attached panels, then trace the current scrolling and layout behavior. Done means the input region stays at the bottom while the conversation scrolls above it, with the optional setting preserving current behavior if implemented.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.