Develop

.gitignore

@@ -36,5 +36,12 @@ src/apps/voice/data/stats.json
 src/apps/voice/data/config.json
 src/apps/test/data/scenarios.json
 
-# Environment-specific project settings
-.claude/settings.json
+# Claude Code project state
+.claude/
+
+# Articles (drafts, images, exports)
+articles/
+
+# Local dev scripts
+reinstall.sh
+reinstall.cmd

CLAUDE.md

@@ -17,8 +17,28 @@ Monorepo managed with **pnpm workspaces** and **Turborepo**.
   All apps/features render within it. It is the container, not an app itself.
 - **Shell** — the MCP server for terminal pane management (`shell_create_pane`,
   `shell_run_command`, etc.). Panes are ephemeral and in-memory.
-- **Apps** — individual features (kanban, voice, test, workflow, etc.) that each
+- **Apps** — individual features (kanban, voice, test, workflow, chat, etc.) that each
   expose both REST routes (mounted by the dashboard) and an MCP server (stdio).
+- **Chat** — the MCP server for multi-LLM communication (`chat_join`,
+  `chat_send`, etc.). Participants and message delivery are in-memory;
+  message history is persisted per-project as JSONL; pipe messages are
+  additionally dual-written to per-pipe JSONL files (`pipes/{pipeId}.jsonl`)
+  for efficient scoped reads. `chat_join` requires an explicit `paneId`,
+  which should be read from `DEVGLIDE_PANE_ID` in the shell session. REST
+  and MCP joins share session state — a REST join with `mcp-session-id`
+  header binds to the MCP session, and MCP tools can adopt REST-joined
+  participants by `paneId`. Pane collisions preserve the existing session
+  (409 `PANE_ALREADY_BOUND`). Chat REST endpoints accept scoped `projectId`
+  overrides, and `POST /api/chat/messages` accepts `projectId` in the body
+  so the dashboard can target a non-active project explicitly. The effective
+  chat rules of engagement are returned on join and can be overridden per
+  project.
+- **Documentation** — the MCP server for operational guidance on DevGlide
+  tools (`docs_list`, `docs_match`, `docs_context`, etc.). Provides tool
+  guides, workflows, examples, troubleshooting entries, and project
+  overrides. Hybrid-scoped: global docs in `~/.devglide/documentation/`,
+  project overrides in `projects/{id}/documentation/`. Seed content is
+  auto-installed on first use.
 
 ## MCP Server Pattern
 
@@ -66,12 +86,16 @@ All runtime state lives in `~/.devglide/`. The directory structure:
 │   ├── logs/                  #   project log files
 │   ├── workflows/             #   project-scoped workflows
 │   ├── vocabulary/            #   project-scoped vocabulary
-│   └── prompts/               #   project-scoped prompts
+│   ├── prompts/               #   project-scoped prompts
+│   ├── chat/                  #   chat message history (messages.jsonl)
+│   │   └── pipes/             #   per-pipe JSONL files ({pipeId}.jsonl)
+│   └── documentation/         #   project-scoped documentation overrides
 ├── voice/                     # global voice config, history, stats
 │   └── config.json
 ├── workflows/                 # global workflows
 ├── vocabulary/                # global vocabulary
 ├── prompts/                   # global prompts
+├── documentation/             # global documentation (tool guides, workflows, etc.)
 ├── logs/                      # server logs
 └── pids/                      # daemon PID files
 ```
@@ -93,13 +117,15 @@ These rules are intentional — do not change an app's scoping without discussio
 | **Test** | `projects/{id}/scenarios.json` | Saved test scenarios |
 | **Log** | `projects/{id}/logs/` | Log file tailing scoped to active project |
 | **Shell** | In-memory | Panes belong to a project session, no disk persistence |
+| **Chat** | `projects/{id}/chat/` | Message history (`messages.jsonl`) and rules override (`rules.md`) per project; participants are in-memory |
 
 ### Hybrid (global + per-project overlay; per-project takes precedence)
 | App | Path | Notes |
 |-----|------|-------|
 | **Workflow** | `~/.devglide/workflows/` + `projects/{id}/workflows/` | Project workflows override global |
 | **Vocabulary** | `~/.devglide/vocabulary/` + `projects/{id}/vocabulary/` | Project terms overlay global |
 | **Prompts** | `~/.devglide/prompts/` + `projects/{id}/prompts/` | Project prompts overlay global |
+| **Documentation** | `~/.devglide/documentation/` + `projects/{id}/documentation/` | Project docs override global by ID; seed content auto-installed |
 
 ## Platform Notes
 

README.md

@@ -19,9 +19,9 @@
 </p>
 
 <p align="center">
-  <img src="https://img.shields.io/badge/MCP_Tools-56-22c55e" alt="56 MCP Tools" />
-  <img src="https://img.shields.io/badge/MCP_Servers-8-3b82f6" alt="8 MCP Servers" />
-  <img src="https://img.shields.io/badge/App_Modules-10-f59e0b" alt="10 App Modules" />
+  <img src="https://img.shields.io/badge/MCP_Tools-61-22c55e" alt="61 MCP Tools" />
+  <img src="https://img.shields.io/badge/MCP_Servers-9-3b82f6" alt="9 MCP Servers" />
+  <img src="https://img.shields.io/badge/App_Modules-11-f59e0b" alt="11 App Modules" />
   <img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License" />
   <img src="https://img.shields.io/badge/node-%3E%3D22-brightgreen" alt="Node.js >= 22" />
 </p>
@@ -51,15 +51,15 @@ devglide setup
 devglide dev
 ```
 
-Open **http://localhost:7000** — that's it. Claude Code can now use all 56 MCP tools.
+Open **http://localhost:7000** — that's it. Claude Code can now use all 61 MCP tools.
 
 > **Requirements:** Node.js >= 22, [Claude Code](https://docs.anthropic.com/en/docs/claude-code) CLI
 >
 > **Platforms:** Linux, macOS, and Windows (native, WSL, or Git Bash).
 
 ## Modules
 
-DevGlide ships 10 integrated modules. Eight expose MCP servers that Claude Code calls directly; two are dashboard-only tools.
+DevGlide ships 11 integrated modules. Nine expose MCP servers that Claude Code calls directly; two are dashboard-only tools.
 
 ### Kanban — Task Management
 
@@ -103,6 +103,10 @@ Product docs and guides served directly in the dashboard with navigation, module
 
 <img src="assets/screenshots/documentation.png" alt="Documentation viewer with module cards" width="800" />
 
+### Chat — Multi-LLM Communication
+
+Shared chat room where the user and multiple LLM instances (Claude Code, Cursor, Codex, etc.) communicate via @mention addressing. The server assigns each participant a unique memorable name. Messages are delivered to LLMs via PTY injection into their shell panes.
+
 ### And More
 
 | Module | Type | What it does |
@@ -124,9 +128,9 @@ Product docs and guides served directly in the dashboard with navigation, module
              │ stdio (MCP)           │ stdio (MCP)
              ▼                       ▼
 ┌────────────────────────────────────────────────────────┐
-│              DevGlide MCP Servers (x8)                 │
+│              DevGlide MCP Servers (x9)                 │
 │                                                        │
-│  kanban  shell  test  workflow  vocab  voice  log  prompts │
+│  kanban  shell  test  workflow  vocab  voice  log  prompts  chat │
 └────────────────────────┬───────────────────────────────┘
                          │
                     shared state
@@ -149,11 +153,11 @@ Product docs and guides served directly in the dashboard with navigation, module
 └────────────────────────────────────────────────────────┘
 ```
 
-**How it works:** `devglide setup` registers 8 MCP servers with Claude Code. Each server runs as an isolated stdio process. The same tools are also available via HTTP on the unified server, so the browser dashboard and Claude Code always share the same state.
+**How it works:** `devglide setup` registers 9 MCP servers with Claude Code. Each server runs as an isolated stdio process. The same tools are also available via HTTP on the unified server, so the browser dashboard and Claude Code always share the same state.
 
 ## MCP Tools
 
-56 tools across 8 servers. Expand each section for the full reference.
+61 tools across 9 servers. Expand each section for the full reference.
 
 <details>
 <summary><strong>Kanban</strong> — 15 tools</summary>
@@ -275,6 +279,19 @@ Product docs and guides served directly in the dashboard with navigation, module
 
 </details>
 
+<details>
+<summary><strong>Chat</strong> — 5 tools</summary>
+
+| Tool | Description |
+|------|-------------|
+| `chat_join` | Join the chat room; pass a live `paneId` from `DEVGLIDE_PANE_ID` with `submitKey: "cr"` (default, correct for all known clients) |
+| `chat_leave` | Leave the chat room |
+| `chat_send` | Send a message (use @mentions to target recipients) |
+| `chat_read` | Read message history with limit, since, and topic filters |
+| `chat_members` | List active participants with pane link status |
+
+</details>
+
 ## CLI Reference
 
 ```bash
@@ -320,6 +337,7 @@ devglide/
 │   │   ├── voice/           # Speech-to-text
 │   │   ├── log/             # Console capture
 │   │   ├── prompts/         # Prompt templates
+│   │   ├── chat/            # Multi-LLM chat room
 │   │   ├── coder/           # In-browser editor
 │   │   └── keymap/          # Keyboard shortcuts
 │   └── packages/

bin/claude-md-template.js

@@ -1,7 +1,7 @@
 // Managed CLAUDE.md section for DevGlide onboarding instructions.
 // Installed by `devglide setup`, removed by `devglide teardown`.
 
-const VERSION = "0.4.0";
+const VERSION = "0.6.0";
 const BEGIN = `<!-- DEVGLIDE:BEGIN v${VERSION} -->`;
 const END = "<!-- DEVGLIDE:END -->";
 
@@ -94,11 +94,53 @@ Describe what to test in natural language and scenarios are generated automatica
   - Config: \`GET /config\` · \`GET /config/providers\` · \`PUT /config\` · \`POST /config/test\` · \`GET /config/check-ffmpeg\`
   - Stats: \`GET /config/stats\` · \`DELETE /config/stats\`
 
+### devglide-chat — Multi-LLM chat room
+Shared chat room where user and multiple LLM instances communicate via @mention addressing.
+Messages are delivered to LLMs via PTY injection when linked to a shell pane.
+- \`chat_join\` — register as a chat participant (requires explicit \`paneId\`)
+- \`chat_leave\` — leave the chat room
+- \`chat_send\` — send a message (delivery goes to recipients resolved from \`to\` plus body @mentions; use \`@all\` to broadcast; LLM messages with no recipients in either field are persisted but not PTY-delivered)
+- \`chat_read\` — read message history (supports \`limit\`, \`since\` filters)
+- \`chat_members\` — list active participants with pane link status
+- **Name assignment:** The server derives your chat alias from \`name\` + pane number (e.g. "claude-1" for name "claude" on pane 1). The \`name\` param is the stable identity base — use a consistent agent label, not the backend model. Always use the \`name\` returned by \`chat_join\`.
+- **Targeted PTY delivery:** Delivery recipients are resolved from the \`to\` param plus any body @mentions. Use \`@all\` as an explicit broadcast token. LLM messages with no recipients in either \`to\` or body @mentions are persisted in history but not PTY-delivered to any agent terminal.
+- **Rules of Engagement:** On \`chat_join\`, you receive a \`rules\` field (markdown) defining when to respond vs. stay silent. **Follow these rules exactly.** Default: reply if @mentioned, or on a global user request only after your claim has been explicitly confirmed by the other active LLM participants. Do not let multiple LLMs answer the same global request uncoordinated. Rules can be customized per project.
+- **\`submitKey\`:** Use \`"cr"\` (default) for all known clients including Claude Code and Codex. The submit key is sent after a short delay to avoid paste-burst detection in TUI frameworks. Only use \`"lf"\` if you have verified a specific client requires it.
+- **Pane collision:** If your \`paneId\` collides with another participant, the **existing session is preserved** and the newcomer receives a 409 error with \`code: "PANE_ALREADY_BOUND"\`. The newcomer must use a different pane or wait for the existing participant to leave.
+- **Pane linking:** A valid \`paneId\` is required to receive messages. Read \`DEVGLIDE_PANE_ID\` from your shell session and pass it explicitly to \`chat_join\` every time. The pane must also be live and routable by the shell backend or \`chat_join\` will fail. If the env var is unavailable, chat cannot be used from that session. If your pane closes, you are removed from chat.
+- **Session unification:** REST and MCP joins share the same session state. A REST join with an \`mcp-session-id\` header automatically binds to the MCP session. MCP tools (\`chat_send\`, \`pipe_submit\`, \`chat_leave\`) can also adopt a REST-joined participant by passing \`paneId\`.
+- **Limitations:** You cannot message yourself; participants are in-memory (rejoin after server restart); only same-project participants see each other.
+- **REST API** (base: \`/api/chat\`):
+  - Join: \`POST /join\` body \`{ name, model?, paneId, submitKey? }\`
+  - Leave: \`POST /leave\` body \`{ name }\`
+  - Send: \`POST /send\` body \`{ from, message, to? }\`
+  - Members: \`GET /members\`
+  - Messages: \`GET /messages?limit=&since=\`
+  - Status: \`GET /status\` · \`GET /status?name=\` · \`GET /status?paneId=\`
+  - Pipes: \`POST /pipes/:id/submit\` body \`{ from, content }\` · \`POST /pipes/:id/cancel\` (no body; cancels by pipe ID within active project)
+  - Invite: \`POST /invite\` body \`{ cli, mode?, cols?, rows? }\`
+  - Panes: \`GET /panes\`
+  - Rules: \`GET /rules\` | \`PUT /rules\` body \`{ rules }\` | \`DELETE /rules\`
+  - Clear: \`DELETE /messages\`
+
 ### devglide-log — Structured logging
 - \`log_write\` — write a structured log entry
 - \`log_read\` — read log entries
 - \`log_clear\`, \`log_clear_all\` — clear logs
 
+### devglide-documentation — Operational guidance for DevGlide tools
+Provides tool guides, workflows, examples, troubleshooting, and project overrides.
+Helps LLMs correctly use devglide-test + devglide-log for UI verification.
+- \`docs_list\` — browse available documentation (filter by type, tool name, tag)
+- \`docs_match\` — search documentation by keyword query (ranked results)
+- \`docs_get_tool_guide\` — get the full operational guide for a tool
+- \`docs_get_workflow\` — get a step-by-step workflow by name
+- \`docs_get_troubleshooting\` — find troubleshooting by tool + symptom
+- \`docs_context\` — get compiled markdown for a task query (best for context injection)
+- \`docs_add\`, \`docs_update\`, \`docs_remove\` — manage documentation entries
+- **When to use:** Before using devglide-test for verification, call \`docs_context\` with your task.
+  When a tool run fails with a known symptom, call \`docs_get_troubleshooting\` or \`docs_match\`.
+
 ## Common Patterns
 
 ### Creating a feature

bin/codex-config.js

@@ -0,0 +1,22 @@
+/**
+ * Remove all DevGlide MCP sections from Codex TOML content.
+ * This includes the current devglide-* registrations and the legacy bare
+ * [mcp_servers.devglide] HTTP entry.
+ */
+export function removeDevglideSectionsFromToml(toml) {
+  const lines = toml.split('\n');
+  const result = [];
+  let skipping = false;
+
+  for (const line of lines) {
+    if (/^\[/.test(line)) {
+      skipping = /^\[mcp_servers\.devglide(?:\]|[.-])/.test(line);
+    }
+
+    if (!skipping) {
+      result.push(line);
+    }
+  }
+
+  return result.join('\n').replace(/\n{3,}/g, '\n\n').replace(/\n+$/, '\n');
+}

bin/codex-config.test.ts

@@ -0,0 +1,51 @@
+import { describe, expect, it } from "vitest";
+
+import { removeDevglideSectionsFromToml } from "./codex-config.js";
+
+describe("removeDevglideSectionsFromToml", () => {
+  it("removes the legacy bare devglide HTTP section", () => {
+    const toml = [
+      '[windows]',
+      'sandbox = "unelevated"',
+      '',
+      '[mcp_servers.devglide]',
+      'url = "http://localhost:7000/mcp"',
+      '',
+      '[mcp_servers.other]',
+      'url = "http://example.com/mcp"',
+      '',
+    ].join('\n');
+
+    expect(removeDevglideSectionsFromToml(toml)).toBe([
+      '[windows]',
+      'sandbox = "unelevated"',
+      '',
+      '[mcp_servers.other]',
+      'url = "http://example.com/mcp"',
+      '',
+    ].join('\n'));
+  });
+
+  it("removes devglide server sections together with nested tool overrides", () => {
+    const toml = [
+      '[mcp_servers.devglide-shell]',
+      'command = "node"',
+      '',
+      '[mcp_servers.devglide-shell.tools.shell_run_command]',
+      'approval_mode = "approve"',
+      '',
+      '[mcp_servers.devglide-chat]',
+      'command = "node"',
+      '',
+      '[mcp_servers.keep]',
+      'command = "node"',
+      '',
+    ].join('\n');
+
+    expect(removeDevglideSectionsFromToml(toml)).toBe([
+      '[mcp_servers.keep]',
+      'command = "node"',
+      '',
+    ].join('\n'));
+  });
+});