Reported issues for limps

Pod holds 13 of 13 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to limps.

Most discussed

fix: HTTP GET /mcp returns 400 instead of 405 Method Not Allowed

Severity: Medium

`GET /mcp` returns `400 Bad Request` with `{"error":"Missing mcp-session-id header"}` instead of the semantically correct `405 Method Not Allowed`.

Current behavior

``` GET /mcp → 400 {"error":"Missing mcp-session-id header"} ```

Expected behavior

``` GET /mcp → 405 {"error":"Method Not Allowed"} Allow: POST, DELETE ```

Fix

Add a method check before the session-id check in `src/server-http.ts`:

```typescript if (url.pathna

Read the thread · 2026-03-02 · open · 0 comments

feat(acp): wire ACP create_artifact to the document model pipeline

Problem

The ACP create_artifact tool in src/acp/tools.ts returns a delegation message without actually creating any files. Agents calling it via ACP get no artifact back.

Current behavior

async create_artifact(req) {
  return { ok: true, message: 'Artifact creation delegated to AI agent', request: req };
}

Expected behavior

create_artifact calls the same generateArtifactHandler logic used by the generate_artifact MCP tool — creating the file via the `IDo

Read the thread · 2026-03-02 · open · 0 comments

feat(acp): wire ACP validate_invest tool to invest.ts

Problem

The ACP validate_invest tool in src/acp/tools.ts returns a hardcoded stub (score: 0) instead of calling validateInvest() from src/utils/invest.ts.

Current behavior

async validate_invest(req: { content: string }) {
  return { score: 0, warnings: ['INVEST validation not yet connected to document model'] };
}

Expected behavior

The tool accepts either raw markdown content or a taskId, parses frontmatter + body via gray-matter, runs `validateInves

Read the thread · 2026-03-02 · open · 0 comments

CLI: add `manage-tags` command

Feature

The manage_tags MCP tool manages frontmatter tags on documents but has no CLI equivalent.

Verified ✅

// List tags
{"name": "manage_tags", "arguments": {"path": "plans/0001.../000_spike.agent.md", "operation": "list"}}
// → {"tags": ["spike", "mcp", "rmcp", "tauri-channel"]}

// Add tags
{"name": "manage_tags", "arguments": {"path": "...", "operation": "add", "tags": ["test", "cleanup"]}}
// → OK

// Remove tags
{"name": "manage_tags", "arguments": {"path": "...", "ope

[Read the thread](https://github.com/paulbreuler/limps/issues/125) · 2026-02-10 · closed · 0 comments

### CLI: add `process-doc` and `process-docs` commands

## Feature

The `process_doc` and `process_docs` MCP tools allow JavaScript-based document querying and transformation, but have no CLI equivalents.

### `process_doc` (verified ✅)
Processes a single document with JavaScript code. Has built-in helpers: `extractSections()`, `extractFrontmatter()`, `extractCodeBlocks()`, `extractFeatures()`, `extractAgents()`, `findByPattern()`, `summarize()`.

```json
{"name": "process_doc", "arguments": {
  "path": "plans/0001-ai-control-via-mcp/0001-ai-control-

[Read the thread](https://github.com/paulbreuler/limps/issues/124) · 2026-02-10 · closed · 0 comments

### CLI: add document management commands (list-docs, search-docs, create-doc, update-doc, delete-doc)

## Feature

5 MCP tools for document CRUD have no CLI equivalents. All work correctly via MCP:

| MCP Tool | Description | Verified |
|----------|-------------|----------|
| `list_docs` | List files/directories with depth and glob patterns | ✅ |
| `search_docs` | Full-text search across planning documents | ✅ |
| `create_doc` | Create a new document (with optional template) | ✅ |
| `update_doc` | Update document (overwrite, append, prepend, patch) | ✅ |
| `delete_doc` | Delete document (with con

[Read the thread](https://github.com/paulbreuler/limps/issues/123) · 2026-02-10 · closed · 0 comments

### CLI: add `create-plan` command

## Feature

The `create_plan` MCP tool works (creates plan directory + scaffold), but there's no CLI equivalent.

## Expected

```bash
limps create-plan "My Feature Name" --description "Optional description"

Should create the same directory structure as the MCP tool: plans/NNNN-my-feature-name/ with plan doc and agents directory.

MCP tool reference

{"name": "create_plan", "arguments": {"name": "My Feature Name", "description": "..."}}
// → OK: Plan "0017-My Feature Name" crea

[Read the thread](https://github.com/paulbreuler/limps/issues/122) · 2026-02-10 · closed · 0 comments

### Bug: `update_task_status` MCP tool fails with 'Feature #N not found in document'

## Bug

The `update_task_status` MCP tool fails for all task IDs with:

Feature #N not found in document


## Reproduction

```json
{"name": "update_task_status", "arguments": {"taskId": "0001-ai-control-via-mcp#005", "status": "GAP"}}
// → ERR: Feature #5 not found in document

{"name": "update_task_status", "arguments": {"taskId": "0001-ai-control-via-mcp#000", "status": "PASS"}}
// → ERR: Feature #0 not found in document

Also tried with agentId param — same error.

Expected

Read the thread · 2026-02-10 · closed · 0 comments

Most recent

CLI: `limps status` has no flag to update agent status

Feature Gap

limps status can only show plan/agent status. There's no CLI flag to update agent status (e.g., GAP → WIP → PASS).

Expected

limps status 0001-ai-control-via-mcp#000 --set PASS --notes "Completed in PR #116"

Current Workaround

Manually edit the agent .agent.md file frontmatter:

status: PASS  # was GAP

Context

The MCP server exposes update_task_status which can set status, but there's no CLI equivalent. This makes it impossible to up

Read the thread · 2026-02-10 · closed · 0 comments

refactor: remove dead code and standardize tool error handling

Context

During the security hardening work (#94 follow-up), an anti-pattern analysis identified two areas for cleanup.

1. Dead code in indexer.ts

Two exported functions in packages/limps/src/indexer.ts are never called externally:

indexAllDocuments() - Appears to be a legacy wrapper around indexAllPaths(). No callers in the codebase.
findMarkdownFiles() - Legacy file discovery function. All callers now use findFiles() directly.

Both should be removed (or unexport

Read the thread · 2026-02-07 · closed · 0 comments

Plan status / next task stale after closing plan on disk

Summary

When a plan is closed by updating agent files on disk (e.g. bulk Status: GAP → Status: PASS), MCP tools get_plan_status and get_next_task can continue to return stale data until the MCP server is restarted. A client using runi Planning has observed this.

Tools involved

get_plan_status (planId)
get_next_task (planId)

Expected behavior

After agent files are updated on disk (e.g. all agents in a plan s

Read the thread · 2026-01-31 · closed · 0 comments

create-feature-plan output incompatible with extractFeatures

Problem update_task_status fails with "Feature #N not found in document" for plans generated by /create-feature-plan. The plan format produced by create-feature-plan does not match the parser used by extractFeatures() (used by MCP task status updates).

Current file format Example: plans/0043-limps-analysis-ir-overhaul/0043-limps-analysis-ir-overhaul-plan.md

Section headings: ## Feature 0: Component IR + Module Graph Foundation
Status line: **Status:** GAP
No TL;DR: l

Read the thread · 2026-01-31 · closed · 0 comments

feat(sync-mcp): Update local .mcp.json files in addition to global settings

Feature Request

The limps config sync-mcp command currently only updates the global Cursor settings file (~/Library/Application Support/Cursor/User/settings.json), but does not update local workspace .mcp.json files.

Current Behavior

When running limps config sync-mcp --client cursor, the command:

✅ Updates global Cursor settings.json (in mcp.servers section)
❌ Does not update local workspace .mcp.json files

Desired Behavior

The sync-mcp command should:

Update

Read the thread · 2026-01-28 · closed · 0 comments

The remaining reports are on the project's issue tracker.

Reported issues for limps

Most discussed

fix: HTTP GET /mcp returns 400 instead of 405 Method Not Allowed

Severity: Medium

Current behavior

Expected behavior

Fix

feat(acp): wire ACP create_artifact to the document model pipeline

Problem

Current behavior

Expected behavior

feat(acp): wire ACP validate_invest tool to invest.ts

Problem

Current behavior

Expected behavior

CLI: add manage-tags command

Feature

Verified ✅

MCP tool reference

Expected

Most recent

CLI: limps status has no flag to update agent status

Feature Gap

Expected

Current Workaround

Context

refactor: remove dead code and standardize tool error handling

Context

1. Dead code in indexer.ts

Plan status / next task stale after closing plan on disk

Plan status / next task stale after closing plan on disk

Summary

Tools involved

Expected behavior

create-feature-plan output incompatible with extractFeatures

feat(sync-mcp): Update local .mcp.json files in addition to global settings

Feature Request

Current Behavior

Desired Behavior

CLI: add `manage-tags` command

CLI: `limps status` has no flag to update agent status