@sudosandwich/limps 3.1.0 → 3.2.0

package/README.md

@@ -23,9 +23,11 @@
 - [Project Setup](#project-setup)
 - [Client Setup](#client-setup)
 - [Transport](#transport)
+- [Daemon Management](#daemon-management)
 - [CLI Commands](#cli-commands)
 - [Configuration](#configuration)
 - [Environment Variables](#environment-variables)
+- [Troubleshooting](#troubleshooting)
 - [MCP Tools](#mcp-tools)
 - [Skills & Commands](#skills--commands)
 - [Extensions](#extensions)
@@ -49,6 +51,9 @@ limps init
 
 # Start the HTTP daemon
 limps start
+# → Daemon starts on http://127.0.0.1:4269/mcp
+# → PID file written to OS-standard location
+# → Ready for MCP client connections
 
 # Generate MCP client config
 limps config print --client claude-code
@@ -57,6 +62,8 @@ limps config print --client claude-code
 
 That's it. Your AI assistant now has access to your documents via HTTP transport. The folder can be anywhere—local, synced, or in a repo; limps does not require a git repository or a `plans/` directory.
 
+**Tip:** `limps status-server` shows the status of the current project if a config is found in the working directory (or passed via `--config`). Run it from a directory where no limps config can be resolved to list all running limps daemons on your system.
+
 ## Features
 
 - **Document CRUD + full-text search** across any folder of Markdown files
@@ -74,6 +81,7 @@ That's it. Your AI assistant now has access to your documents via HTTP transport
 
 - **Local only** — Your data stays on disk (SQLite index + your files). No cloud, no subscription.
 - **Restart after changes** — If you change the indexed folder or config, restart the MCP server (or rely on the file watcher) so the index and tools reflect the current state.
+- **Daemon management** — The HTTP server runs as a background process. Use `limps start`, `limps stop`, and `limps status-server` to manage the daemon lifecycle. PID files are stored in OS-standard directories for system-wide awareness.
 - **Sandboxed user code** — `process_doc` and `process_docs` run your JavaScript in a QuickJS sandbox with time and memory limits; no network or Node APIs.
 - **One optional network call** — `limps version --check` fetches from the npm registry to compare versions. All other commands (serve, init, list, search, create/update/delete docs, process_doc, etc.) do **not** contact the internet. Omit `version --check` if you want zero external calls.
 
@@ -309,21 +317,23 @@ limps v3 uses **HTTP transport exclusively** via a persistent daemon. This allow
 
 ```bash
 # Start the daemon
-limps start --config /path/to/config.json
+limps start
 
 # Check status (shows uptime, sessions, PID)
-limps status-server --config /path/to/config.json
+limps status-server
 
 # Stop the daemon
-limps stop --config /path/to/config.json
+limps stop
 ```
 
 The daemon runs at `http://127.0.0.1:4269/mcp` by default. Use `limps config print` to generate the correct MCP client configuration:
 
 ```bash
-limps config print --client claude-code --config /path/to/config.json
+limps config print --client claude-code
 ```
 
+See [Daemon Management](#daemon-management) for detailed lifecycle documentation.
+
 ### MCP Client Configuration
 
 All clients use HTTP transport. Example config:
@@ -345,15 +355,15 @@ All clients use HTTP transport. Example config:
 
 Customize the HTTP server by adding a `"server"` section to your `config.json`:
 
-| Option             | Default        | Description                              |
-| ------------------ | -------------- | ---------------------------------------- |
-| `port`             | `4269`         | HTTP listen port                         |
-| `host`             | `127.0.0.1`   | Bind address                             |
-| `maxSessions`      | `100`          | Maximum concurrent MCP sessions          |
-| `sessionTimeoutMs` | `1800000`      | Session idle timeout in ms (30 min)      |
-| `corsOrigin`       | `""` (none)    | CORS origin (`""`, `"*"`, or a URL)      |
-| `maxBodySize`      | `10485760`     | Max request body in bytes (10 MB)        |
-| `rateLimit`        | `100 req/min`  | Rate limit per client IP                 |
+| Option             | Default                | Description                              |
+| ------------------ | ---------------------- | ---------------------------------------- |
+| `port`             | `4269`                 | HTTP listen port                         |
+| `host`             | `127.0.0.1`            | Bind address                             |
+| `maxSessions`      | `100`                  | Maximum concurrent MCP sessions          |
+| `sessionTimeoutMs` | `1800000`              | Session idle timeout in ms (30 min)      |
+| `corsOrigin`       | `""` (none)            | CORS origin (`""`, `"*"`, or a URL)      |
+| `maxBodySize`      | `10485760`             | Max request body in bytes (10 MB)        |
+| `rateLimit`        | `100 req/min`          | Rate limit per client IP                 |
 
 Example custom server config:
 
@@ -366,8 +376,255 @@ Example custom server config:
 }
 ```
 
+**Note:** PID files are stored in OS-standard application directories:
+- **macOS**: `~/Library/Application Support/limps/pids/`
+- **Linux**: `$XDG_DATA_HOME/limps/pids/` or `~/.local/share/limps/pids/`
+- **Windows**: `%APPDATA%/limps/pids/`
+
+This enables `limps status-server` to perform system-wide daemon discovery when no project configuration can be resolved; when a limps config is found for the current directory, the CLI runs in project mode and reports status for that project instead.
+
 - **Remote clients**: Use an MCP-compatible HTTPS proxy for remote clients (e.g., ChatGPT).
 
+## Daemon Management
+
+limps v3 uses a persistent HTTP daemon with system-wide awareness. PID files are stored in OS-standard directories, allowing you to manage and discover daemons from any directory on your system.
+
+### PID File Locations
+
+PID files are stored in platform-specific application data directories:
+
+**macOS:**
+```
+~/Library/Application Support/limps/pids/
+```
+
+**Linux:**
+```
+$XDG_DATA_HOME/limps/pids/
+# or if XDG_DATA_HOME is not set:
+~/.local/share/limps/pids/
+```
+
+**Windows:**
+```
+%APPDATA%/limps/pids/
+```
+
+Each PID file is named by port number (`limps-{port}.pid`) to enable system-wide discovery. Example PID file structure:
+
+```json
+{
+  "pid": 12345,
+  "port": 4269,
+  "host": "127.0.0.1",
+  "startedAt": "2026-02-08T12:00:00.000Z",
+  "configPath": "/path/to/project/.limps/config.json"
+}
+```
+
+This port-based naming allows `limps status-server` to find all running daemons across different projects without needing a config file.
+
+### Starting the Daemon
+
+**Background mode (default):**
+
+```bash
+limps start
+# → Daemon starts on http://127.0.0.1:4269/mcp
+# → PID file written to OS-standard location
+# → Process detaches and runs in background
+```
+
+**Foreground mode (debugging):**
+
+```bash
+limps start --foreground
+# → Runs in foreground (blocks terminal)
+# → Logs appear in stderr
+# → Useful for debugging startup issues
+# → Still creates PID file for discovery
+```
+
+**Custom port/host (via config):**
+
+Configure `server.port` and `server.host` in your `.limps/config.json`:
+
+```json
+{
+  "server": {
+    "port": 8080,
+    "host": "0.0.0.0"
+  }
+}
+```
+
+Then start normally:
+
+```bash
+limps start
+# → Starts using server.port/server.host from config
+# → PID file: limps-8080.pid
+```
+
+The `start` command performs health verification by polling the `/health` endpoint for up to 5 seconds, issuing repeated HTTP requests. Each individual health-check request has its own shorter timeout (for example, ~1000ms). If any request fails during this window, you'll see one of these error codes:
+
+- **TIMEOUT** — A single health-check HTTP request exceeded its per-request timeout (e.g., ~1000ms). The daemon may be slow to start or system resources may be constrained. Try `limps start --foreground` to see logs.
+- **NETWORK_ERROR** — Cannot connect to daemon. Port may be blocked or already in use by another process.
+- **NON_200_STATUS** — Health endpoint returned a non-200 status code. Check daemon logs with foreground mode.
+- **INVALID_RESPONSE** — Health endpoint responded, but the response was invalid or could not be parsed as expected (for example, malformed or missing required fields).
+
+### Checking Daemon Status
+
+**Project mode (when config is found):**
+
+```bash
+# From within a project directory with .limps/config.json
+limps status-server
+# limps server is running
+# PID: 12345 | 127.0.0.1:4269
+# Uptime: 2h 15m
+# Sessions: 3
+
+# Or specify config explicitly
+limps status-server --config /path/to/.limps/config.json
+```
+
+**System-wide discovery (when no config is found):**
+
+```bash
+# From a directory without a limps config
+cd /tmp
+limps status-server
+# Found 2 running daemons:
+# 127.0.0.1:4269 (PID 12345)
+#   Uptime: 2h 15m | Sessions: 3
+# 127.0.0.1:8080 (PID 67890)
+#   Uptime: 45m 30s | Sessions: 1
+```
+
+When `limps status-server` cannot resolve a config file in the current directory (and no `--config` is provided), it scans the system PID directory and reports all running limps daemons. When a config is found, it shows only that project's daemon status.
+
+### Stopping the Daemon
+
+```bash
+# From the project directory (where your .limps config lives):
+limps stop
+# → Gracefully shuts down daemon
+# → Closes all MCP sessions
+# → Stops file watchers
+# → Removes PID file
+# → Process exits
+
+# Or from any directory, by specifying the config explicitly:
+limps stop --config /path/to/.limps/config.json
+```
+
+The `stop` command is project-specific and resolves the config to determine which daemon to stop. The daemon performs a graceful shutdown by:
+1. Closing all active MCP sessions
+2. Shutting down file watchers
+3. Removing the PID file
+4. Exiting the process
+
+### Port Conflicts
+
+If you try to start a daemon on a port that's already in use, limps will detect the conflict and provide resolution guidance:
+
+```bash
+limps start
+# Error: Port 4269 is already in use.
+# Process using port: node (PID 12345)
+# Command: /usr/local/bin/node /usr/local/bin/limps start
+#
+# To stop the process: kill 12345
+# Or use a different port: limps start --port <port>
+```
+
+On systems with `lsof` available (macOS, Linux), limps can identify which process is using the port and show its command line. If `lsof` is not available, you'll see a simpler error message suggesting a different port.
+
+### Foreground Mode
+
+Use foreground mode for debugging, Docker deployments, or CI/CD pipelines:
+
+```bash
+limps start --foreground
+```
+
+**Use cases:**
+- **Debugging** — See server logs in real-time to diagnose startup issues
+- **Docker** — Keep container alive with the daemon as the main process
+- **CI/CD** — Run tests against a limps daemon without background processes
+
+**Behavior differences from background mode:**
+- Logs to stderr instead of being silent
+- Blocks the terminal (press Ctrl+C to stop)
+- Still creates a PID file for discovery by other processes
+- Responds to SIGINT (Ctrl+C) and SIGTERM for graceful shutdown
+
+### Health Endpoint
+
+The HTTP daemon exposes a `/health` endpoint for monitoring and health checks:
+
+```bash
+curl http://127.0.0.1:4269/health
+```
+
+**Example response:**
+
+```json
+{
+  "status": "ok",
+  "sessions": 3,
+  "uptime": 8145,
+  "pid": 12345,
+  "sessionTimeoutMs": 1800000
+}
+```
+
+**HTTP status codes:**
+- **200** — Daemon is healthy and accepting connections
+- **429** — Rate limit exceeded (rate limiter may return this before the request reaches `/health`)
+
+Use this endpoint for:
+- Monitoring daemon health in scripts or dashboards
+- Verifying daemon is running before connecting MCP clients
+- Automated health checks in orchestration tools (Kubernetes, Docker Compose)
+
+### Multiple Daemons
+
+You can run multiple limps daemons on different ports for different projects by configuring different ports in each project's config:
+
+```bash
+# Project A with default port (4269)
+cd ~/projects/project-a
+# .limps/config.json has server.port: 4269 (or uses default)
+limps start
+# → Running on http://127.0.0.1:4269/mcp
+
+# Project B with custom port (8080)
+cd ~/projects/project-b
+# .limps/config.json has server.port: 8080
+limps start
+# → Running on http://127.0.0.1:8080/mcp
+```
+
+Each daemon has its own PID file:
+- `limps-4269.pid` — Project A
+- `limps-8080.pid` — Project B
+
+Discover all running daemons (run from a directory without a limps config):
+
+```bash
+cd /tmp
+limps status-server
+# Found 2 running daemons:
+# 127.0.0.1:4269 (PID 12345)
+#   Uptime: 2h 15m | Sessions: 3
+# 127.0.0.1:8080 (PID 67890)
+#   Uptime: 45m 30s | Sessions: 1
+```
+
+Each MCP client can connect to different daemons by configuring different URLs in their config files.
+
 ## CLI Commands
 
 ### Viewing Plans
@@ -383,9 +640,10 @@ limps next-task <plan>        # Get highest-priority available task
 
 ```bash
 limps init [path]             # Initialize new project
-limps start                   # Start HTTP daemon (required for MCP clients)
+limps start                   # Start HTTP daemon (background by default)
+limps start --foreground      # Start in foreground (debugging mode)
 limps stop                    # Stop HTTP daemon
-limps status-server           # Show HTTP daemon status
+limps status-server           # Show daemon status (current project or all daemons)
 limps config show             # Display current config
 limps config print            # Print MCP client config snippets
 ```
@@ -470,6 +728,191 @@ Config lives at `.limps/config.json` in your project directory, created by `limp
 
 **Precedence:** `config.tools` overrides env vars. If allowlist is set, denylist is ignored.
 
+## Troubleshooting
+
+### Daemon Won't Start
+
+**"Port already in use" error:**
+
+If you see this error, another process is using the port:
+
+```bash
+limps start
+# Error: Port 4269 is already in use.
+# Process using port: node (PID 12345)
+```
+
+**Resolution:**
+1. **Kill the existing process**: `kill 12345`
+2. **Or use a different port**: `limps start --port 8080`
+3. **Check if it's another limps daemon**: `limps status-server` (if so, use `limps stop` first)
+
+**"Daemon may have failed to start" error:**
+
+If the daemon starts but doesn't respond to health checks:
+
+```bash
+limps start
+# Error: Daemon may have failed to start. Check logs or try: limps start --foreground
+```
+
+**Resolution:**
+1. **Run in foreground to see logs**: `limps start --foreground`
+2. **Check for permission issues**: Ensure you have write access to the PID directory
+3. **Verify port is accessible**: Try `curl http://127.0.0.1:4269/health`
+4. **Enable debug logging**: `DEBUG=1 limps start --foreground`
+
+**Permission issues with PID directory:**
+
+If you can't create PID files:
+
+```bash
+# macOS
+ls -la ~/Library/Application\ Support/limps/pids/
+
+# Linux
+ls -la ~/.local/share/limps/pids/
+
+# Windows
+dir %APPDATA%\limps\pids
+```
+
+Ensure the directory exists and you have write permissions. If not, create it manually:
+
+```bash
+# macOS
+mkdir -p ~/Library/Application\ Support/limps/pids
+
+# Linux
+mkdir -p ~/.local/share/limps/pids
+
+# Windows
+mkdir %APPDATA%\limps\pids
+```
+
+### Health Check Failures
+
+**TIMEOUT error:**
+
+The daemon did not respond within the configured timeout. Each health-check request has its own timeout (for example, 1000ms during the final `limps start` check and 3000ms for `status-server`), and during startup limps will poll for up to about 5 seconds before reporting "Daemon may have failed to start".
+
+**Common causes:**
+- System resource constraints (high CPU/memory usage)
+- Slow filesystem (especially for index initialization)
+- Large document corpus requiring time to index
+
+**Resolution:**
+1. Check system resources: `top` or Activity Monitor
+2. Wait a bit longer and retry: `limps status-server`
+3. Run in foreground to see progress: `limps start --foreground`
+
+**NETWORK_ERROR:**
+
+Cannot establish connection to the daemon.
+
+**Common causes:**
+- Port is blocked by firewall
+- Daemon crashed after starting
+- Incorrect host/port configuration
+
+**Resolution:**
+1. Verify daemon is running: `limps status-server`
+2. Check firewall settings for port 4269
+3. Try `curl http://127.0.0.1:4269/health` manually
+4. Check daemon logs: `limps start --foreground`
+
+### Stale PID Files
+
+limps automatically cleans up stale PID files when:
+- Running `limps status-server` (discovers and removes stale files)
+- Running `limps start` (removes stale file for the target port)
+- The daemon shuts down gracefully with `limps stop`
+
+If you need to manually clean up PID files:
+
+```bash
+# macOS
+rm ~/Library/Application\ Support/limps/pids/limps-*.pid
+
+# Linux
+rm ~/.local/share/limps/pids/limps-*.pid
+
+# Windows
+del %APPDATA%\limps\pids\limps-*.pid
+```
+
+**When to manually clean up:**
+- After a system crash or forced shutdown
+- If `limps start` reports a daemon is running but it's not
+- Before uninstalling limps
+
+### Multiple Daemons Conflict
+
+If you accidentally try to start a second daemon on the same port:
+
+```bash
+limps start
+# Error: limps daemon already running (PID 12345 on 127.0.0.1:4269). Run 'limps stop' first.
+```
+
+This is expected behavior — limps prevents multiple daemons on the same port using PID-based locking.
+
+**Resolution:**
+1. **Check all running daemons**: `limps status-server`
+2. **Stop the existing daemon**: `limps stop`
+3. **Or start on a different port**: `limps start --port 8080`
+
+### Debugging Connection Issues
+
+If MCP clients can't connect to the daemon, verify connectivity step by step:
+
+**1. Check daemon status:**
+
+```bash
+limps status-server
+# Should show daemon running with healthy status
+```
+
+**2. Verify health endpoint:**
+
+```bash
+curl http://127.0.0.1:4269/health
+# Should return JSON with status "ok"
+```
+
+**3. Verify MCP endpoint:**
+
+```bash
+curl -X POST http://127.0.0.1:4269/mcp \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{}}}'
+# Should return MCP initialize response
+```
+
+**4. Enable debug logging:**
+
+```bash
+DEBUG=1 limps start --foreground
+# Watch for connection attempts and errors
+```
+
+**5. Check MCP client config:**
+
+Ensure the URL in your client config matches the daemon:
+
+```json
+{
+  "mcpServers": {
+    "limps-planning-myproject": {
+      "transport": {
+        "type": "http",
+        "url": "http://127.0.0.1:4269/mcp"
+      }
+    }
+  }
+}
+```
+
 ## MCP Tools
 
 limps exposes MCP tools for AI assistants:

package/dist/cli/config-cmd.d.ts

@@ -64,7 +64,7 @@ export declare function resetAll(configPath: string, options?: {
 import { type McpClientAdapter, type McpServerConfig } from './mcp-client-adapter.js';
 /**
  * Generate MCP server configuration JSON for a single limps project.
- * Always generates HTTP transport configuration (limps v3 daemon mode).
+ * Generates stdio or HTTP transport configuration depending on client support.
  *
  * @param adapter - MCP client adapter
  * @param configPath - Path to the limps config file
@@ -78,7 +78,7 @@ export declare function generateMcpClientConfig(adapter: McpClientAdapter, confi
 };
 /**
  * Generate config for printing.
- * Always generates HTTP transport configuration (limps v3 daemon mode).
+ * Generates stdio or HTTP transport configuration depending on client support.
  */
 export declare function generateConfigForPrint(adapter: McpClientAdapter, configPath: string): string;
 /**

package/dist/cli/config-cmd.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"config-cmd.d.ts","sourceRoot":"","sources":["../../src/cli/config-cmd.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAKH,OAAO,EAML,KAAK,aAAa,EAClB,KAAK,cAAc,EACnB,KAAK,aAAa,EAEnB,MAAM,cAAc,CAAC;AAGtB;;GAEG;AACH,MAAM,WAAW,UAAU;IACzB,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,EAAE;QACN,SAAS,EAAE,MAAM,CAAC;QAClB,QAAQ,EAAE,MAAM,CAAC;QACjB,SAAS,CAAC,EAAE,MAAM,EAAE,CAAC;QACrB,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;KAC3B,CAAC;CACH;AAED;;;;;;GAMG;AACH,wBAAgB,aAAa,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,UAAU,CAkB3E;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CA8FpE;AAED;;;;;GAKG;AACH,wBAAgB,aAAa,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CAIvE;AAED,MAAM,WAAW,0BAA0B;IACzC,MAAM,CAAC,EAAE,aAAa,CAAC;IACvB,OAAO,CAAC,EAAE,OAAO,CAAC,cAAc,CAAC,CAAC;IAClC,MAAM,CAAC,EAAE,OAAO,CAAC,aAAa,CAAC,CAAC;CACjC;AAED,wBAAgB,iBAAiB,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CA+C3E;AAED,wBAAgB,mBAAmB,CACjC,mBAAmB,EAAE,MAAM,MAAM,EACjC,OAAO,EAAE,0BAA0B,GAClC,MAAM,CAiGR;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CAEpE;AAED;;;;;;GAMG;AACH,wBAAgB,QAAQ,CAAC,UAAU,EAAE,MAAM,EAAE,OAAO,GAAE;IAAE,KAAK,CAAC,EAAE,OAAO,CAAA;CAAO,GAAG,MAAM,EAAE,CAwDxF;AAED,OAAO,EAAE,KAAK,gBAAgB,EAAE,KAAK,eAAe,EAAE,MAAM,yBAAyB,CAAC;AAEtF;;;;;;;;GAQG;AACH,wBAAgB,uBAAuB,CACrC,OAAO,EAAE,gBAAgB,EACzB,UAAU,EAAE,MAAM,GACjB;IACD,UAAU,EAAE,MAAM,CAAC;IACnB,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC;IACzC,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACrC,CAsCA;AAED;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,gBAAgB,EAAE,UAAU,EAAE,MAAM,GAAG,MAAM,CAgB5F;AAED;;GAEG;AACH,wBAAgB,2BAA2B,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,CA4BtE;AAED;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED;;;;;;;GAOG;AACH,wBAAgB,YAAY,CAAC,UAAU,EAAE,MAAM,EAAE,OAAO,EAAE,mBAAmB,GAAG,MAAM,CAoCrF"}
+{"version":3,"file":"config-cmd.d.ts","sourceRoot":"","sources":["../../src/cli/config-cmd.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAKH,OAAO,EAML,KAAK,aAAa,EAClB,KAAK,cAAc,EACnB,KAAK,aAAa,EAEnB,MAAM,cAAc,CAAC;AAGtB;;GAEG;AACH,MAAM,WAAW,UAAU;IACzB,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,EAAE;QACN,SAAS,EAAE,MAAM,CAAC;QAClB,QAAQ,EAAE,MAAM,CAAC;QACjB,SAAS,CAAC,EAAE,MAAM,EAAE,CAAC;QACrB,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;KAC3B,CAAC;CACH;AAED;;;;;;GAMG;AACH,wBAAgB,aAAa,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,UAAU,CAkB3E;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CA8FpE;AAED;;;;;GAKG;AACH,wBAAgB,aAAa,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CAIvE;AAED,MAAM,WAAW,0BAA0B;IACzC,MAAM,CAAC,EAAE,aAAa,CAAC;IACvB,OAAO,CAAC,EAAE,OAAO,CAAC,cAAc,CAAC,CAAC;IAClC,MAAM,CAAC,EAAE,OAAO,CAAC,aAAa,CAAC,CAAC;CACjC;AAED,wBAAgB,iBAAiB,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CA+C3E;AAED,wBAAgB,mBAAmB,CACjC,mBAAmB,EAAE,MAAM,MAAM,EACjC,OAAO,EAAE,0BAA0B,GAClC,MAAM,CAiGR;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,mBAAmB,EAAE,MAAM,MAAM,GAAG,MAAM,CAEpE;AAED;;;;;;GAMG;AACH,wBAAgB,QAAQ,CAAC,UAAU,EAAE,MAAM,EAAE,OAAO,GAAE;IAAE,KAAK,CAAC,EAAE,OAAO,CAAA;CAAO,GAAG,MAAM,EAAE,CAyDxF;AAED,OAAO,EAAE,KAAK,gBAAgB,EAAE,KAAK,eAAe,EAAE,MAAM,yBAAyB,CAAC;AAEtF;;;;;;;;GAQG;AACH,wBAAgB,uBAAuB,CACrC,OAAO,EAAE,gBAAgB,EACzB,UAAU,EAAE,MAAM,GACjB;IACD,UAAU,EAAE,MAAM,CAAC;IACnB,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC;IACzC,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACrC,CAsCA;AAED;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,gBAAgB,EAAE,UAAU,EAAE,MAAM,GAAG,MAAM,CAgB5F;AAED;;GAEG;AACH,wBAAgB,2BAA2B,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,CA4BtE;AAED;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED;;;;;;;GAOG;AACH,wBAAgB,YAAY,CAAC,UAAU,EAAE,MAAM,EAAE,OAAO,EAAE,mBAAmB,GAAG,MAAM,CAoCrF"}

package/dist/cli/config-cmd.js

@@ -297,10 +297,11 @@ export function resetAll(configPath, options = {}) {
         log.push('Run with --force to confirm.');
         return log;
     }
+    const httpConfig = getHttpServerConfig(config);
     const dataPath = config.dataPath;
     // Stop running daemon
     try {
-        const pidFilePath = getPidFilePath(dataPath);
+        const pidFilePath = getPidFilePath(httpConfig.port);
         const daemon = getRunningDaemon(pidFilePath);
         if (daemon) {
             try {
@@ -328,7 +329,7 @@ export function resetAll(configPath, options = {}) {
 }
 /**
  * Generate MCP server configuration JSON for a single limps project.
- * Always generates HTTP transport configuration (limps v3 daemon mode).
+ * Generates stdio or HTTP transport configuration depending on client support.
  *
  * @param adapter - MCP client adapter
  * @param configPath - Path to the limps config file
@@ -343,12 +344,12 @@ export function generateMcpClientConfig(adapter, configPath) {
     const parentDir = basename(dirname(configPath));
     const projectDir = parentDir === '.limps' ? basename(dirname(dirname(configPath))) : parentDir;
     const serverName = `limps-planning-${projectDir}`;
-    // Load HTTP server config
+    // Load server config for HTTP clients
     const config = loadConfig(configPath);
     const httpConfig = getHttpServerConfig(config);
-    // Build servers configuration (HTTP transport only)
+    // Build servers configuration (adapter determines stdio vs HTTP)
     const servers = {
-        [serverName]: adapter.createHttpServerConfig(httpConfig.host, httpConfig.port),
+        [serverName]: adapter.createServerConfig(configPath, httpConfig.host, httpConfig.port),
     };
     // Build full config structure
     const serversKey = adapter.getServersKey();
@@ -369,7 +370,7 @@ export function generateMcpClientConfig(adapter, configPath) {
 }
 /**
  * Generate config for printing.
- * Always generates HTTP transport configuration (limps v3 daemon mode).
+ * Generates stdio or HTTP transport configuration depending on client support.
  */
 export function generateConfigForPrint(adapter, configPath) {
     const { fullConfig, serversKey } = generateMcpClientConfig(adapter, configPath);