MoonshotAI / MoonshotAI/kimi-code

Tower 模式在多仓库环境下不可用

Open
#3,895 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

你运行的 Kimi Code 版本是?

Desktop 1.0.1

你使用的是哪个开放平台/订阅?

第三方供应商

你使用的是哪个模型?

kimi-k3

你的电脑平台是?

Darwin 25.6.0 arm64 arm

你遇到了什么问题?

Key findings: the session directory is not a git repo and no .tower workspace exists anywhere — so TowerInit here would bootstrap a fresh git history over this multi-repo directory (the exact case the tower docs flag as requiring a safe default; under auto mode I won't create that mess, and tower missions can't span the 3 repos this objective needs anyway).

OK here's my final approach, balancing everything:

  1. Do NOT call TowerInit (would git-init the multi-repo parent dir and snapshot it — the exact dangerous case the docs flag; under auto mode I take the safe default: don't).
复现步骤?

项目目录:folder/
内有多个 Git 仓库:

  • folder/repo1
  • folder/repo2
  • ...

folder/ 中开启 agent session,启动 Tower 模式,模型拒绝执行。

期望的行为是什么?

目前想到两种方案:

  1. session 原生支持指定多个 Git 目录;
  2. 支持在上级文件夹开启 Tower 模式。
补充信息

No response

Contribution
  • 我愿意自己提交修复此 bug 的 PR(请先等待维护者在本 issue 中批准)

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 at the session initialization and Tower mode entry points responsible for discovering Git repositories. Reproduce the issue from a parent folder containing repo1 and repo2, then trace how the session directory and Tower workspace are detected. Done means Tower mode can safely handle the multi-repository layout without creating a new Git history or refusing the session.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.