Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#554 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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
平均マージ
15時間 10分
マージ済み PR（30日）
34

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

MiniMax-AI/minimax-code のほかの issue

MiniMax-AI/minimax-code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。