Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[Feature]: Allow creating a project without a local directory, and attach multiple directories to one project

未關閉
  • 哪裡不對？
#554 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript
領域
backend, cli, desktop

研究方向

Start by tracing project creation and session project resolution in the desktop and CLI/TUI paths, then inspect the database schema for the workspace project kind and its workspace_dir constraint. The issue identifies these as single-directory assumptions but names no files or tests. Done means projects can have zero or multiple roots, directory changes preserve session associations, and the UI and agent handle every attached root.

由索引模型根據 Issue 內容生成。

描述

desktop
Product or interface

Desktop app

Use case and problem

Creating a project in the MiniMax Code desktop app currently requires selecting a local directory. The "Create project" flow opens a directory picker, and there is no way to complete it without choosing a folder.

That makes two everyday workflows awkward:

1. A project that is not tied to a folder.
Sometimes I want a project that groups conversations, notes, or research before any code exists — for example "OceanBase proposal", "onboarding notes", or "side project ideas". The only workaround today is to create an empty throwaway folder just to satisfy the directory picker. That folder then appears in the project list with a meaningless name, an empty workspace, and an extra directory on disk that has to be cleaned up later.

2. A project that spans several directories.
Real work is often split across multiple checkouts — a frontend repo plus a backend repo plus a shared library, or a monorepo plus an adjacent tooling repo. The Codex app handles this by letting one project hold multiple local directories. In MiniMax Code I have to create one project per directory and mentally track which one a session belongs to. There is no grouping and no multi-root workspace, so the agent only ever sees a single root and cannot read or write across the directories that make up the task.

Desired behavior

1. Create a project without a local directory.
Allow the project creation flow to be completed with no directory selected. The agent would then start in a neutral location, and the user could attach a folder later or work purely on chat/scratch content.

2. Attach multiple local directories to a single project.
A project should hold a list of workspace roots rather than exactly one:

  • "Add folder" and "Remove folder" actions on an existing project.
  • When the agent runs in such a project, every attached directory is exposed to it as a workspace root, so it can read and write across them.
  • The project file tree shows each attached root separately.
  • Sessions started in the project resolve paths against the union of those roots.

Acceptance criteria

  • The "New project" flow can be completed without selecting a directory.
  • A second, third, … directory can be added to and removed from an existing project.
  • A multi-root project exposes every attached directory to the agent, and tool calls resolve paths inside each of them.
  • The UI distinguishes clearly between a project with 0 roots, 1 root, and N roots.
Platform

macOS (the request is cross-platform; the same limitation applies on Windows and Linux)

Alternatives and additional context
  • Today I work around this by creating one project per directory. I am not aware of an existing "group projects" or "multi-root workspace" feature in the desktop app.
  • The same single-directory assumption appears in the CLI/TUI path as well: session project resolution is based on one workspace directory.
  • Note for the implementation, in case it helps: in the current runtime model a workspace Project is keyed by its directory (workspace:<dir>), and the database schema constrains a workspace project to exactly one non-empty workspace_dir (a separate default project kind holds no directory at all). Supporting several directories per project therefore most likely needs a new project↔directory relation rather than a UI-only change — it would also need a way to keep sessions associated with a project when the directory that created them is removed.
主要語言
TypeScript
星號
2.1k
分支
271
平均合併
12 小時 15 分鐘
30 天內合併 PR
41

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

MiniMax-AI/minimax-code 的其他 Issue

查看 MiniMax-AI/minimax-code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。