MoonshotAI / MoonshotAI/kimi-code

功能建议:Kimi Code Web 支持无工作区启动选项,便于处理与工作区无关的小任务

Open
#1,717 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

建议

在新建对话时选择工作区(或添加工作区)的下拉选择中,增加一个 "无工作区启动" 的选项。

动机

目前 Kimi Code 必须在某个文件/目录下才能启动。但有时候我只想用来快速处理一件小任务,这个任务可能与当前目录下的任何项目都无关。

由于当前必须在某个目录下启动,Kimi Code 会首先读取当前目录,这严重干扰了它执行这种"小任务"的场景。为了避免这种干扰,我现在每次都要先说明"请帮我做一个小任务,跟当前项目毫不相关",它才会比较优雅高效地执行。

如果支持"无工作区启动",就可以让 Kimi Code 直接进入一个干净的、不绑定任何工作区的对话上下文,更专注于当前的小任务。

参考

可以借鉴 Codex(现称 ChatGPT)的做法:

  • 新建对话时,可以选择一个工作区,对话会自动归档到对应的工作区,并在该工作区中干活。
  • 如果不选择工作区,则将当前对话视为一个独立的任务,并归类到任务列表中。

这种设计区分了"与项目相关的工作"和"快速的小任务",体验上更加清晰。

环境信息

  • Kimi Code CLI 版本:0.23.6
  • 操作系统:macOS 26.5.2

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 by tracing the CLI flow for creating a conversation and selecting or adding a workspace. Check how the current workspace is read and how conversations are categorized. Done means a new conversation can explicitly start without a workspace and does not read or bind to the current directory, while workspace-based conversations continue to work.

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.