MoonshotAI / MoonshotAI/kimi-code

feat(kimi-web): add a collapse button at the bottom (or floating) of long expanded blocks

Open
#3,147 0 comments 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

Problem

In the kimi web session view, several blocks are collapsible (thinking, work-in-progress groups, tool call details, etc.). When such a block is expanded and its content is very long (long thinking, large tool output), the collapse control only exists at the top of the block. To collapse it again, the user has to scroll all the way back up, which is tedious.

Expected behavior

Either of the following would work:

  1. Render an additional "collapse" button at the bottom of an expanded block; or
  2. When the block header scrolls out of the viewport, show a floating "collapse" button (sticky/floating) that collapses the block and scrolls the view back to the block header.

Environment

  • kimi web 0.37.2
  • macOS, Chrome

Additional context

It would be even better if the long-content collapse interaction were considered consistently across TUI and web. Thanks!

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

Start in the Kimi web session view by locating the existing collapsible block headers for thinking, work-in-progress groups, and tool call details. Inspect how expanded long content is rendered, then add a bottom or floating collapse control and verify that long thinking and tool output can be collapsed without scrolling back to the header.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.