Option to render the plan box title at the bottom
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start in apps/kimi-code/src/tui/components/messages/plan-box.ts at PlanBoxComponent.render() and inspect how configuration or theme options are defined elsewhere in the TUI. Confirm the intended title-position behavior with the maintainer, then verify that the plan box renders the title correctly in each supported position without changing other TUI boxes.
Written by the indexing model from the issue text.
Description
Feature request: option to render the plan box title at the bottom
What I'd like: a way to display the plan box title (plan: <file>.md) at the bottom of the box instead of the top.
Currently, when a plan is approved, the box renders like this — title at the top:
Current plan · Approved
┌ plan: catwoman-patriot-forge.md ──────
│ ...plan content...
└───────────────────────────────────────
I'd prefer the filename title on the bottom border:
Current plan · Approved
┌───────────────────────────────────────
│ ...plan content...
└── plan: catwoman-patriot-forge.md ────
Where this is implemented: the plan box has a dedicated renderer in
apps/kimi-code/src/tui/components/messages/plan-box.ts
(PlanBoxComponent.render()). The title is drawn on the top border only:
const title = this.buildTitle(horzLen);
const trailingDashLen = Math.max(0, horzLen - visibleWidth(title));
const top = indent + paint('┌') + paint(title) + paint('─'.repeat(trailingDashLen)) + paint('┐');
const bottom = indent + paint('└' + '─'.repeat(horzLen) + '┘');
The bottom line is currently plain dashes, so moving the title there is a small, localized change affecting only the plan box (not other TUI boxes).
Suggestion: expose a config/theme option (e.g. title_position = "top" | "bottom"), or simply default the plan box title to the bottom. Happy to open a PR if a maintainer indicates a preferred approach.
Environment: kimi-code v0.38.0 (single-binary install), Linux.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 41m
- Merged PRs (30d)
- 345
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.
More from MoonshotAI/kimi-code
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
MoonshotAI/kimi-code#3947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-code#3836 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MoonshotAI/kimi-code#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-code#3755 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-code#3627 ·
All issues in MoonshotAI/kimi-code
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100