docs: remove references to cut VSCode extension UI

Author: nikomatsakis

md/SUMMARY.md

@@ -50,7 +50,7 @@
       - [Testing](./design/vscode-extension/testing.md)
       - [Testing Implementation](./design/vscode-extension/testing-implementation.md)
       - [Packaging](./design/vscode-extension/packaging.md)
-      - [Mod UI](./design/vscode-extension/mods.md)
+      - [Mods UI](./design/vscode-extension/mods.md)
       - [Language Model Provider](./design/vscode-extension/lm-provider.md)
       - [Language Model Tool Bridging](./design/vscode-extension/lm-tool-bridging.md)
       - [Implementation Status](./design/vscode-extension/implementation-status.md)

md/artwork/screenshots/screenshot-vscode-panel.jpg

@@ -91,17 +91,15 @@ These allow protocol extensions beyond the ACP specification. Not currently need
 - [ ] Workspace-specific state persistence
 - [ ] Tab history and conversation export
 
-## Agent Extensions
+## Agent Mods
 
-Agent extensions are proxy components that enrich the agent's capabilities. See [Agent Extensions](./extensions.md) for details.
+Agent mods are proxy components that enrich the agent's capabilities. See [Agent Mods](./mods.md) for details.
 
 - [x] CLI support (`--proxy` argument for `symposium-acp-agent`)
-- [x] VS Code setting (`symposium.extensions` array)
-- [x] Settings UI with enable/disable checkboxes
-- [x] Drag-to-reorder in Settings UI
-- [x] Delete and add extensions back
-- [ ] Registry extensions (install from agent registry with `type = 'extension'`)
-- [ ] Per-extension configuration (e.g., which Ferris tools to enable)
+- [x] Config agent with interactive `/symposium:config` command
+- [x] Per-workspace mod configuration
+- [ ] Registry mods (install from agent registry with `type = 'mod'`)
+- [ ] Per-mod configuration (e.g., which Ferris tools to enable)
 
 ## Language Model Provider (Experimental)
 

md/design/vscode-extension/implementation-status.md

@@ -1,63 +1,16 @@
-# Mod UI (VSCode)
+# Mods UI (VSCode)
 
-This chapter covers VSCode-specific UI for managing mods. For general mod concepts, see [Agent Mods](../mods.md).
+This chapter covers how mods work in the VSCode environment. For general mod concepts, see [Agent Mods](../mods.md).
 
-## Configuration Storage
+## Configuration
 
-Mods are configured via the `symposium.mods` VS Code setting:
+Mods are configured through the Symposium config agent, not through VSCode settings. The VSCode extension spawns `symposium-acp-agent run`, which handles all configuration.
 
-```json
-"symposium.mods": [
-  { "id": "sparkle", "_enabled": true, "_source": "built-in" },
-  { "id": "ferris", "_enabled": true, "_source": "built-in" },
-  { "id": "cargo", "_enabled": true, "_source": "built-in" }
-]
-```
-
-Custom mods include their distribution:
-
-```json
-{
-  "id": "my-mod",
-  "_enabled": true,
-  "_source": "custom",
-  "name": "My Mod",
-  "distribution": {
-    "npx": { "package": "@myorg/my-mod" }
-  }
-}
-```
-
-**Default behavior** - when no setting exists, all built-in mods are enabled. If the user returns to the default configuration, the key is removed from settings.json entirely.
-
-## Settings UI
-
-The Settings panel includes a Mods section where users can:
-
-- **Enable/disable** mods via checkbox
-- **Reorder** mods by dragging the handle
-- **Delete** mods from the list
-- **Add** mods via the "+ Add mod" link, which opens a QuickPick dialog
-
-### Add Mod Dialog
-
-The QuickPick dialog shows three sections:
-
-1. **Built-in** - sparkle, ferris, cargo (greyed out if already added)
-2. **From Registry** - mods from the shared registry with `type: "mod"`
-3. **Add Custom Mod**:
-   - From executable on your system (local command/path)
-   - From npx package
-   - From pipx package
-   - From cargo crate
-   - From URL to mod.json (GitHub URLs auto-converted to raw)
+See [Run Mode](../run-mode.md) for details on:
+- Configuration file format (`~/.symposium/config/`)
+- Interactive configuration via `/symposium:config` command
+- First-time setup flow
 
 ## Spawn Integration
 
-When spawning an agent, the extension builds `--proxy` arguments from enabled mods:
-
-```bash
-symposium-acp-agent run-with --proxy sparkle --proxy ferris --proxy cargo --agent '...'
-```
-
-Only enabled mods are passed, in their configured order.
+The VSCode extension spawns the agent using `symposium-acp-agent run`. The config agent loads mod configuration from disk and builds the proxy chain automatically.

md/design/vscode-extension/mods.md

@@ -11,20 +11,9 @@ Install the Symposium extension from:
 
 ## Step 2: Activate the panel and start chatting
 
-<div class="panel-guide">
-<img src="./artwork/screenshots/screenshot-vscode-panel.jpg" alt="Symposium panel in VSCode"/>
-<div class="panel-legend">
-
-1. **Activity bar icon** — Click to open the Symposium panel
-2. **New tab** — Start a new conversation with the current settings
-3. **Settings** — Expand to configure agent and extensions
-4. **Agent selector** — Choose which agent to use (Claude Code, Gemini CLI, etc.)
-5. **Extensions** — Enable MCP servers that add capabilities to your agent
-6. **Add extension** — Add custom extensions
-7. **Edit all settings** — Access full settings
-
-</div>
-</div>
+Click the Symposium icon in the activity bar to open the panel, then click **New tab** to start a conversation.
+
+On first run, Symposium will guide you through selecting an agent. After that, you can change your agent or mods at any time by typing `/symposium:config` in the chat.
 
 ## Custom Agents
 

md/install-vscode.md

@@ -1,6 +1,6 @@
 # Using Symposium
 
-Symposium focuses on creating the best environment for Rust coding through **Agent Extensions** - MCP servers that add specialized tools and context to your agent.
+Symposium focuses on creating the best environment for Rust coding through **Agent Mods** - MCP servers that add specialized tools and context to your agent.
 
 Symposium is built on the Agent Client Protocol (ACP), which means the core functionality is portable across editors and environments. VSCode is the showcase environment with experimental GUI support, but the basic functionality can be configured in any ACP-supporting editor.
 
@@ -19,26 +19,22 @@ Symposium checks for updates and installs new versions automatically as they bec
 
 For adding custom agents not in the registry, see [VSCode Installation - Custom Agents](../install-vscode.md#custom-agents).
 
-## Managing Extensions
+## Managing Mods
 
-Extensions add capabilities to your agent. Open the **Settings** panel to manage them.
+Mods add capabilities to your agent. To configure mods, type `/symposium:config` in the chat.
 
-In the Extensions section you can:
-- **Enable/disable** extensions via the checkbox
-- **Reorder** extensions by dragging the handle
-- **Add** extensions via the "+ Add extension" link
-- **Delete** extensions from the list
+The configuration menu lets you:
+- **Toggle** mods on/off by typing their number
+- **Reorder** mods with `move X to Y`
+- **Save** changes with `SAVE` or discard with `CANCEL`
 
-**Order matters** - extensions are applied in the order listed. The first extension is closest to the editor, and the last is closest to the agent.
+**Order matters** - mods are applied in the order listed. The first mod is closest to the editor, and the last is closest to the agent.
 
-When adding extensions, you can choose from:
-- **Built-in** extensions (Sparkle, Ferris, Cargo)
-- **Registry** extensions from the shared catalog
-- **Custom** extensions via executable, npx, pipx, cargo, or URL
+On first run, Symposium recommends mods based on your workspace (e.g., Cargo mod for Rust projects). You can adjust these recommendations in the config menu.
 
-## Builtin Extensions
+## Builtin Mods
 
-Symposium ships with three builtin extensions:
+Symposium ships with three builtin mods:
 
 - **[Sparkle](./sparkle.md)** - AI collaboration framework that learns your working patterns
 - **[Ferris](./ferris.md)** - Rust crate source inspection