mantisai-cli 2.0.1 → 3.0.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "mantisai-cli",
-  "version": "2.0.1",
-  "description": "Mantis developer CLI — create maps, manage spaces and threads, configure Claude Code, and connect agents to Mantis MCP.",
+  "version": "3.0.0",
+  "description": "Mantis CLI — spaces, maps, and MCP tools for AI coding agents",
   "type": "module",
   "license": "MIT",
   "author": "AnasMaar",
@@ -18,6 +18,7 @@
   },
   "dependencies": {
     "@inquirer/prompts": "^7.5.1",
+    "@modelcontextprotocol/sdk": "^1.29.0",
     "commander": "^13.1.0",
     "csv-parse": "^6.2.1",
     "csv-stringify": "^6.7.0",
@@ -27,9 +28,6 @@
     "mantis": "bin/mantis.js"
   },
   "files": [
-    ".claude-plugin",
-    ".claude-plugin/marketplace.json",
-    ".mcp.json",
     "skills",
     "bin",
     "lib",
@@ -43,7 +41,6 @@
     "mantis",
     "cli",
     "mcp",
-    "claude-code",
-    "plugin"
+    "ai-agents"
   ]
 }

package/skills/codebase/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Index a local codebase into a CSV for Mantis, optionally creating and activating a Mantis codebase map. Use when the user wants Claude Code to map a repository or create a codebase CSV.
+description: Index a local codebase into a CSV for Mantis. Run `mantis use get_space_context` first when Mantis is mentioned.
 argument-hint: [repo-path]
 allowed-tools: Bash, AskUserQuestion
 disable-model-invocation: true
@@ -7,6 +7,8 @@ disable-model-invocation: true
 
 # Create Codebase CSV
 
+First: `mantis use get_space_context` (unless you just ran it this turn).
+
 Use `mantis create codebase`. This command is local-first: it scans files on the user's machine and writes a CSV. It can optionally continue into `mantis create map`.
 
 ## CSV-only Flow
@@ -52,15 +54,15 @@ The command uses good defaults for codebase maps:
 - `categoric`: `language,kind,extension`
 - `numeric`: `loc,bytes`
 
-## After Activation
+## After activation
 
-If `--activate` was used, tell the user to run:
+If `--activate` was used, the new thread is active immediately. Explore with:
 
-```text
-/reload-plugins
+```bash
+mantis use get_space_context
 ```
 
-Then suggest prompts like:
+Example follow-up questions:
 
 ```text
 What are the main architectural zones in this codebase?

package/skills/connect/SKILL.md

@@ -1,42 +1,26 @@
 ---
-description: Run the Mantis MCP setup wizard (API key, space, thread). Use when the user wants to connect Claude Code to Mantis or fix MCP connection issues.
-disable-model-invocation: true
+description: Run mantis setup to connect API key, space, and thread. Use when the user wants to connect to Mantis or fix auth issues. After setup, run `mantis use get_space_context`.
 ---
 
-# Connect Mantis MCP
+# Connect to Mantis
 
-Run the interactive setup in the user's terminal:
+If already configured, run `mantis use get_space_context` first. Otherwise:
 
 ```bash
 mantis setup
 ```
 
-If the plugin is not on PATH, use:
+Setup only prompts for space/thread if they are not already configured.
 
-```bash
-node "${CLAUDE_PLUGIN_ROOT}/bin/mantis.js" setup
-```
-
-The wizard will:
-
-1. Ask for Mantis API URL and Developer API key (`live_…` from the Mantis Developer portal).
-2. List accessible spaces — owned, shared, and public (most recent first).
-3. Pick or create a **space state** (thread).
-4. Save config for MCP headers (`X-Space-State-ID`).
-
-After setup, switch context with **`/mantis:space`** and **`/mantis:thread`** (Claude Code **AskUserQuestion** menu with arrow keys). Terminal: `mantis select space` / `mantis select thread`.
-
-If they have not run **`mantis setup`** yet, tell them:
+Then verify:
 
 ```bash
-npm install -g mantisai-cli
-mantis setup
+mantis status
+mantis use get_space_context
 ```
 
-That installs the **mantis@mantis-plugins** Claude Code plugin and saves API/space/thread config.
-
-Then: **`/reload-plugins`** in Claude Code (if already open). Confirm **API URL** when prompted (default `https://kellis-h200-1.csail.mit.edu`; use `http://localhost:8000` for local Docker). API keys: https://mantis.csail.mit.edu/developer/#keys
+First-time Claude Code users: `mantis setup claude` installs skills to `~/.claude/skills/`.
 
-If `/plugin` shows **Disabled** or *not installed*: run `claude plugin install mantis@mantis-plugins`, enable it, then `/reload-plugins`. If update fails, uninstall and reinstall the plugin (stale `installed_plugins.json` / orphaned cache).
+API keys: https://mantis.csail.mit.edu/developer/#keys
 
-For connection errors: URL must end with `/mcp_integrated/`; avoid `/mcp/mcp` unless their deployment uses it.
+If `mantis use` fails with "No thread configured", run `mantis select thread`.

package/skills/createmap/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Create a Mantis map from a local CSV or XLSX file using the mantis CLI. Use when the user wants to upload a dataset, configure field types, or turn a CSV into a Mantis map.
+description: Create a Mantis map from a local CSV or XLSX file using the mantis CLI. Run `mantis use get_space_context` first when Mantis is mentioned.
 argument-hint: [csv-or-xlsx-path]
 allowed-tools: Bash, AskUserQuestion
 disable-model-invocation: true
@@ -7,6 +7,8 @@ disable-model-invocation: true
 
 # Create Mantis Map
 
+First: `mantis use get_space_context` (unless you just ran it this turn).
+
 Use the local `mantis create map` CLI. Prefer passing arguments explicitly so this works for agents and humans.
 
 ## Steps
@@ -53,10 +55,10 @@ mantis create map "./dataset.csv" \
   --semantic-column "summary,content"
 ```
 
-5. Report the created space link and map id from the JSON output. If `--activate` was used, tell the user to run `/reload-plugins`.
+5. Report the created space link and map id from the JSON output.
 
 ## Notes
 
 - If the user wants a fully interactive human flow, run only `mantis create map "./dataset.csv"`.
-- If Claude Code is driving the flow, avoid interactive prompts by passing flags.
+- If an agent is driving the flow, avoid interactive prompts by passing flags.
 - Use `mantis setup` first if the CLI says API key or URL is missing.

package/skills/mantis/SKILL.md

@@ -1,52 +1,68 @@
 ---
+name: mantis
+description: Work with MIT Mantis spaces, maps, clusters, and notebooks via the mantis CLI. Use whenever the user mentions Mantis. Always run `mantis use get_space_context` first before any other Mantis action.
+---
 
-## name: mantis
-description: Work with MIT Mantis spaces, maps, clusters, and notebooks via MCP. Use when the user mentions Mantis, spaces, maps, embeddings, clusters, bags, or wants to explore/visualize data in their workspace.
+# Mantis
 
-# Mantis (Claude Code)
+Mantis is a spatial data workspace: **spaces** contain **maps**, **clusters**, **bags**, and **notebooks**.
 
-Mantis is a spatial data workspace: **spaces** contain **maps** (embeddings of datasets), **clusters**, **bags**, and **notebooks**.
+## First step
 
-## Connection
+Run this **before any other Mantis command or tool** (skip only if you already ran it this turn):
 
-1. User runs `mantis setup` (or `/mantis:connect`) with a Developer API key from the Mantis portal.
-2. MCP endpoint: `{api_base_url}/mcp_integrated/` (trailing slash required).
-3. Required header on every MCP request: `**X-Space-State-ID`** = thread UUID from setup (setup writes this into the plugin MCP config).
-4. After changing space/thread: `mantis select` then ask the user to run `**/reload-plugins**`.
+```bash
+mantis use get_space_context
+```
 
-## REST (setup only)
+If it fails with no thread configured, run `mantis setup` or `mantis select thread`, then retry.
 
+## Setup
 
-| Endpoint                                      | Purpose                             |
-| --------------------------------------------- | ----------------------------------- |
-| `GET /api/v1/me/spaces/?scope=accessible&limit=100` | List owned, shared, and public spaces |
-| `GET /api/v1/me/space-states/?space_id=`      | List threads                        |
-| `POST /api/v1/me/space-states/`               | Create thread `{ space_id, name? }` |
+```bash
+mantis setup          # API key + space + thread (only prompts what's missing)
+mantis status
+mantis select space
+mantis select thread
+```
 
+Config lives at `~/.mantis/config.json`.
 
-Auth: `Authorization: Bearer live_…` — key must be linked to a Mantis user.
+Install editor skills (CLI-only workflow, no MCP plugin):
 
-## MCP tools (read-focused)
+```bash
+mantis setup claude     # ~/.claude/skills/
+mantis setup opencode   # ~/.config/opencode/skills/ + .opencode/skills/
+```
 
-Call `**get_space_context**` first when you need map IDs, field types, cluster names, or point counts.
+## MCP tools via CLI
 
-Other useful tools: `get_tree_status`, `get_cluster_children`, `get_bags_from_map`, `get_bag_contents`, `get_point_details`, `get_selected_points`, `get_available_dimensions`.
+Every Mantis MCP tool is available through the CLI — no editor MCP plugin required:
 
-Space management tools (`create_space`, `create_map_from_url`, etc.) need session or space-state context.
+```bash
+mantis tools
+mantis use get_space_context
+mantis use get_cluster_children --map-id <uuid> --cluster-id <id>
+mantis use general_search --query "your search"
+```
 
-## Conventions
+Use `--args '{"key":"value"}'` for complex arguments. Kebab flags map to snake_case (`--map-id` → `map_id`).
+
+Use map IDs, field types, and cluster names from the `get_space_context` output — do not guess them.
 
-- Refer to spaces and maps by **name** in user-facing text; use UUIDs only in tool arguments.
-- Maps belong to a space; pick `primary_map_id` from space list API or `get_space_context`.
-- Notebooks can bootstrap from `X-Space-State-ID` alone; file uploads still need a chat session when applicable.
-- Default API URL: `https://kellis-h200-1.csail.mit.edu` (local: `http://localhost:8000`). API keys: https://mantis.csail.mit.edu/developer/#keys
+## REST via CLI (setup & resources)
 
-## Slash commands in this plugin
+| Task | Command |
+|------|---------|
+| Setup | `mantis setup` |
+| Status | `mantis status` |
+| List spaces | `mantis spaces list --filter "query"` |
+| Create map from CSV | `mantis create map file.csv` |
+| Index codebase | `mantis create codebase . --create-map` |
 
-- `/mantis:connect` — first-time setup (API key)
-- `/mantis:space` — pick space via **AskUserQuestion** (↑↓ in Claude UI; optional filter: `/mantis:space atlas`)
-- `/mantis:thread` — pick thread the same way
-- Terminal pickers: `mantis select space` / `mantis select thread` if the in-chat menu fails
-- `/mantis:status` — show current space/thread
+API keys: https://mantis.csail.mit.edu/developer/#keys
+
+## Conventions
 
-After **`/mantis:thread`** only, run `/reload-plugins` once (MCP headers are fixed at connect time). Space-only changes do not need a reload until a thread is set.
+- Refer to spaces and maps by **name** in user-facing text; use UUIDs in tool arguments.
+- After `mantis select space` or `mantis select thread`, the next `mantis use` picks up the new context automatically — no reload step.

package/skills/select/SKILL.md

@@ -1,17 +1,20 @@
 ---
-description: Change the active Mantis space or thread (space state) for MCP. Use when the user wants to switch workspace or conversation context.
-disable-model-invocation: true
+description: Switch active Mantis space and thread via the CLI. Run `mantis use get_space_context` first when Mantis is mentioned.
 ---
 
-# Select Mantis space / thread
+# Select space and thread
 
-Prefer the interactive slash commands (arrow keys + filter as you type):
+First: `mantis use get_space_context` (unless you just ran it this turn).
 
-- **`/mantis:space`** — pick a space
-- **`/mantis:thread`** — pick a thread (after space)
+```bash
+mantis select space
+mantis select thread
+```
 
-CLI fallback: `mantis select` or `node "${CLAUDE_PLUGIN_ROOT}/bin/mantis.js" select`.
+Or both:
 
-After a change, run **`/reload-plugins`**.
+```bash
+mantis select
+```
 
-Optional argument from user (not passed to CLI automatically): if they give a **thread UUID**, they can paste it during setup or edit `~/.mantis/claude-code/config.json` (or `${CLAUDE_PLUGIN_DATA}/config.json`) and set `spaceStateId`.
+After selection, run `mantis use get_space_context` again.

package/skills/space/SKILL.md

@@ -1,62 +1,25 @@
 ---
-description: Select your Mantis space (arrow-key menu in Claude Code). Use when switching workspace for MCP.
+description: Select the active Mantis space using the CLI or list/search helpers. Run `mantis use get_space_context` first when Mantis is mentioned.
 argument-hint: [filter]
-allowed-tools: AskUserQuestion, Bash
-disable-model-invocation: true
+allowed-tools: Bash, AskUserQuestion
 ---
 
 # Select Mantis space
 
-Slash-command `!` blocks cannot use an interactive terminal (no arrow keys). Use **AskUserQuestion** — that is the native Claude Code picker UI.
+First: `mantis use get_space_context` (unless you just ran it this turn).
 
-## Steps
-
-1. If `$ARGUMENTS` looks like a Mantis space URL (`/space/{uuid}`) or a UUID, resolve it first:
-
-```bash
-node "${CLAUDE_PLUGIN_ROOT}/bin/mantis-resolve-space.js" $ARGUMENTS
-```
-
-If JSON has `space`, run `mantis-set-space.js` with that id and name, then stop (skip browse). On `error`, explain and offer browse.
-
-2. Otherwise run (search text or empty for recent page):
-
-```bash
-node "${CLAUDE_PLUGIN_ROOT}/bin/mantis-list-spaces.js" --filter "$ARGUMENTS"
-```
-
-Parse the JSON. On `error`, tell the user to run `mantis setup` in a terminal.
-
-3. **AskUserQuestion** (max 4 options per call):
-   - If the user pasted a link in chat, pass it as `$ARGUMENTS` or run step 1 with that URL.
-   - `header`: `Space`
-   - `question`: `Which Mantis space should Claude use?`
-   - For each item in `spaces`, one option:
-     - `label`: space `name` (short)
-     - `description`: full `id` + map count if present
-   - If `hasMore` is true, use the 3rd slot for the best match and the 4th option:
-     - `label`: `More spaces…`
-     - `description`: `Show next page (${total} total)`
-   - On "More spaces…", re-run with `--offset` increased by `limit` (same filter), then AskUserQuestion again.
-
-4. After the user picks a space (not "More"), run:
+Interactive:
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/bin/mantis-set-space.js" <uuid-from-description> "<name>"
+mantis select space
 ```
 
-Use the UUID from the selected option's **description**, not the label.
-
-5. If `needThread` or `threadCleared`, run **`/mantis:thread`** next in this session (user must pick a thread for the new space).
-
-6. After space or thread changes, tell the user to run **`/reload-plugins`** so MCP reconnects with the updated `X-Space-State-ID` header. Do not try to invoke `/reload-plugins` as a Skill tool.
-
-## Terminal fallback
-
-If AskUserQuestion does not appear (known CC bug in some versions), tell the user to run in a separate terminal:
+Scriptable (for agent menus):
 
 ```bash
-mantis select space
+mantis spaces list --filter "$ARGUMENTS"
+mantis spaces resolve "$ARGUMENTS"
+mantis spaces set <uuid> "<name>"
 ```
 
-Then `/reload-plugins`.
+If space changed and thread was cleared, run `mantis select thread` next, then `mantis use get_space_context`.

package/skills/status/SKILL.md

@@ -1,20 +1,15 @@
 ---
-description: Show the current Mantis space, thread, and MCP URL from plugin config. Use when checking whether Claude Code is connected to Mantis.
-disable-model-invocation: true
+description: Show current Mantis space, thread, and MCP URL from CLI config. Run `mantis use get_space_context` first when Mantis is mentioned.
 ---
 
 # Mantis status
 
-Run in the terminal:
+First: `mantis use get_space_context` (unless you just ran it this turn).
 
 ```bash
 mantis status
 ```
 
-Or:
+Or JSON-friendly check via config path printed by status.
 
-```bash
-node "${CLAUDE_PLUGIN_ROOT}/bin/mantis.js" status
-```
-
-Report the output to the user. If no thread is set, tell them to run `/mantis:connect` or `mantis setup`, then `/reload-plugins`.
+If no thread is set: `mantis setup` or `mantis select thread`.

package/skills/thread/SKILL.md

@@ -1,43 +1,31 @@
 ---
-description: Select your Mantis thread / space state (arrow-key menu in Claude Code). Use after /mantis:space.
+description: Select the active Mantis thread (space state) using the CLI. Run `mantis use get_space_context` first when Mantis is mentioned.
 argument-hint: [filter]
-allowed-tools: AskUserQuestion, Bash
-disable-model-invocation: true
+allowed-tools: Bash, AskUserQuestion
 ---
 
 # Select Mantis thread
 
-Use **AskUserQuestion** for the arrow-key menu inside Claude Code (shell pickers have no TTY in slash commands).
+First: `mantis use get_space_context` (unless you just ran it this turn).
 
-## Steps
-
-1. Run:
+Interactive:
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/bin/mantis-list-threads.js" $ARGUMENTS
+mantis select thread
 ```
 
-If error mentions space, tell user to run **`/mantis:space`** first.
-
-2. **AskUserQuestion**:
-   - `header`: `Thread`
-   - `question`: `Which thread in this space?`
-   - One option per thread (`label`: name, `description`: full `id`)
-   - Always include (if room under 4 options):
-     - `label`: `New thread`
-     - `description`: `Create a new space state for Claude Code`
-   - If `hasMore`, add `More threads…` like `/mantis:space` (paginate with `--offset`)
-
-3. On selection:
-   - **New thread** → `node "${CLAUDE_PLUGIN_ROOT}/bin/mantis-set-thread.js" --new "Claude Code"`
-   - Otherwise → `node "${CLAUDE_PLUGIN_ROOT}/bin/mantis-set-thread.js" <uuid> "<name>"`
-
-4. After a successful `mantis-set-thread.js`, tell the user to run **`/reload-plugins`**. Claude Code exposes `/reload-plugins` as a user command, not a Skill tool, so do not try to invoke it yourself.
+Scriptable:
 
-5. Confirm with one line: space name, thread name, and that MCP is ready after `/reload-plugins`.
+```bash
+mantis threads list --filter "$ARGUMENTS"
+mantis threads new "Thread name"
+mantis threads set <uuid> "<name>"
+```
 
-## Terminal fallback
+Then refresh context:
 
 ```bash
-mantis select thread
+mantis use get_space_context
 ```
+
+Context is read from `~/.mantis/config.json` on each invocation — no reload step.

package/.claude-plugin/marketplace.json

@@ -1,14 +0,0 @@
-{
-  "name": "mantis-plugins",
-  "owner": {
-    "name": "Kellis Lab"
-  },
-  "plugins": [
-    {
-      "name": "mantis",
-      "description": "Mantis MCP: spaces, threads, and map context for Claude Code",
-      "version": "1.0.15",
-      "source": "./"
-    }
-  ]
-}

package/.claude-plugin/plugin.json

@@ -1,18 +0,0 @@
-{
-  "name": "mantis",
-  "description": "Connect Claude Code to Mantis MCP — explore maps, clusters, and notebooks in your spaces",
-  "version": "1.0.15",
-  "author": {
-    "name": "MIT Mantis"
-  },
-  "homepage": "https://mantis.csail.mit.edu",
-  "userConfig": {
-    "api_base_url": {
-      "type": "string",
-      "title": "Mantis API URL",
-      "description": "Base URL only (no path). Default is the CSAIL H200 API; use http://localhost:8000 for local Docker.",
-      "default": "https://kellis-h200-1.csail.mit.edu",
-      "required": true
-    }
-  }
-}

package/.mcp.json

@@ -1,11 +0,0 @@
-{
-  "mcpServers": {
-    "mantis": {
-      "type": "http",
-      "url": "http://localhost:8000/mcp_integrated/",
-      "headers": {
-        "X-Space-State-ID": "51e4a4c2-1510-4456-afe9-ccbd422c7646"
-      }
-    }
-  }
-}

package/bin/mantis-list-spaces.js

@@ -1,32 +0,0 @@
-#!/usr/bin/env node
-import { spacesForPrompt } from '../lib/list-cli.js';
-
-const args = process.argv.slice(2);
-let filter = '';
-let offset = 0;
-let limit = 4;
-for (let i = 0; i < args.length; i++) {
-  const a = args[i];
-  if (a === '--offset') {
-    offset = parseInt(args[++i], 10) || 0;
-    continue;
-  }
-  if (a === '--limit') {
-    limit = parseInt(args[++i], 10) || 4;
-    continue;
-  }
-  if (a === '--filter') {
-    filter = args[++i] ?? '';
-    continue;
-  }
-  filter = args.slice(i).join(' ').trim();
-  break;
-}
-
-try {
-  const data = await spacesForPrompt(filter, { limit, offset });
-  process.stdout.write(JSON.stringify(data));
-} catch (e) {
-  console.error(JSON.stringify({ error: e.message }));
-  process.exit(1);
-}

package/bin/mantis-list-threads.js

@@ -1,32 +0,0 @@
-#!/usr/bin/env node
-import { threadsForPrompt } from '../lib/list-cli.js';
-
-const args = process.argv.slice(2);
-let filter = '';
-let offset = 0;
-let limit = 4;
-for (let i = 0; i < args.length; i++) {
-  const a = args[i];
-  if (a === '--offset') {
-    offset = parseInt(args[++i], 10) || 0;
-    continue;
-  }
-  if (a === '--limit') {
-    limit = parseInt(args[++i], 10) || 4;
-    continue;
-  }
-  if (a === '--filter') {
-    filter = args[++i] ?? '';
-    continue;
-  }
-  filter = args.slice(i).join(' ').trim();
-  break;
-}
-
-try {
-  const data = await threadsForPrompt(filter, { limit, offset });
-  process.stdout.write(JSON.stringify(data));
-} catch (e) {
-  console.error(JSON.stringify({ error: e.message }));
-  process.exit(1);
-}

package/bin/mantis-mcp-headers.js

@@ -1,9 +0,0 @@
-#!/usr/bin/env node
-import { loadConfig } from '../lib/config.js';
-
-const cfg = loadConfig();
-const headers = {};
-if (cfg.spaceStateId) {
-  headers['X-Space-State-ID'] = String(cfg.spaceStateId);
-}
-process.stdout.write(JSON.stringify(headers));

package/bin/mantis-pick-space.js

@@ -1,5 +0,0 @@
-#!/usr/bin/env node
-import { pickSpace } from '../lib/picker.js';
-
-const filter = process.argv.slice(2).join(' ').trim();
-await pickSpace(filter);

package/bin/mantis-pick-thread.js

@@ -1,5 +0,0 @@
-#!/usr/bin/env node
-import { pickThread } from '../lib/picker.js';
-
-const filter = process.argv.slice(2).join(' ').trim();
-await pickThread(filter);

package/bin/mantis-resolve-space.js

@@ -1,25 +0,0 @@
-#!/usr/bin/env node
-import { loadConfig } from '../lib/config.js';
-import { resolveSpaceFromInput } from '../lib/spaces.js';
-
-const input = process.argv.slice(2).join(' ').trim();
-if (!input) {
-  console.error(JSON.stringify({ error: 'Provide a space link or UUID' }));
-  process.exit(1);
-}
-
-try {
-  const cfg = loadConfig();
-  if (!cfg.apiKey || !cfg.apiBaseUrl) {
-    throw new Error('Run mantis setup first (API key + URL).');
-  }
-  const space = await resolveSpaceFromInput(cfg.apiBaseUrl, cfg.apiKey, input);
-  if (!space) {
-    console.error(JSON.stringify({ error: 'Space not found or no access' }));
-    process.exit(1);
-  }
-  process.stdout.write(JSON.stringify({ space, threadCleared: true }));
-} catch (e) {
-  console.error(JSON.stringify({ error: e.message }));
-  process.exit(1);
-}

package/bin/mantis-select.js

@@ -1,7 +0,0 @@
-#!/usr/bin/env node
-import { pickSpace, pickThread } from '../lib/picker.js';
-import { banner } from '../lib/ui.js';
-
-banner('Mantis — switch space / thread');
-await pickSpace();
-await pickThread();

package/bin/mantis-set-space.js

@@ -1,31 +0,0 @@
-#!/usr/bin/env node
-import { loadConfig, saveConfig } from '../lib/config.js';
-import { syncMcpConfigs } from '../lib/mcp-config.js';
-
-const id = process.argv[2];
-const name = process.argv[3] || '';
-if (!id) {
-  console.error('Usage: mantis-set-space <space-uuid> [name]');
-  process.exit(1);
-}
-
-const cfg = loadConfig();
-const changed = cfg.spaceId !== id;
-const next = {
-  ...cfg,
-  spaceId: id,
-  spaceName: name || cfg.spaceName,
-  ...(changed ? { spaceStateId: undefined, spaceStateName: undefined } : {}),
-};
-saveConfig(next);
-syncMcpConfigs(next);
-console.log(
-  JSON.stringify({
-    ok: true,
-    spaceId: id,
-    spaceName: name,
-    threadCleared: changed,
-    needThread: changed,
-    needReloadPlugins: true,
-  }),
-);