MoonshotAI / MoonshotAI/kimi-code
[Feature request]: add a “Delete session” option to the session menu (web app)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What feature would you like to see?
Description:
In the Kimi Code web app, a session’s context menu (the “…” button next to a session in the sidebar) currently offers: Copy session ID, Rename, Fork session, Export session, and Archive.
Proposal:
Add a “Delete session” option to this menu, allowing users to permanently delete a session.
Why it’s useful:
- Archive only hides a session — it doesn’t remove it. Users who want to completely get rid of old or irrelevant sessions have no way to do so.
- Helps keep the session list clean and gives users control over their data (e.g., deleting sessions containing sensitive information).
Suggested behavior:
- Place the “Delete session” button at the bottom of the menu, styled in red to signal a destructive action.
- Show a confirmation dialog before deleting (e.g., “Are you sure you want to delete this session? This action cannot be undone.”).
Visual reference:
See the attached screenshot — the current session menu with Archive highlighted; the new Delete button could be added right below it.
Additional information
No response
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 locating the session sidebar’s context menu and tracing how the existing Archive action is implemented. Add the requested Delete session entry with destructive styling and confirmation; done means users can permanently remove a session and the menu reflects the new option.
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
- 62/100