Feature Memory (MCP)

ToolYour auto-records completed features for cross-project agent memory — system-first, free meta-tools.

Feature Memory is ToolYour’s institutional record for AI agents. When a harness run reaches loop.gate=pass, ToolYour persists requirements and a 10-dimension evaluation matrix automatically. Agents consult memory via plan_task before rebuilding similar work in another repo.

Related: MCP Quickstart · Account & keys · Dashboard → Feature memory

System-first (default)

When	What ToolYour does
`verify_task` / `run_playbook` / `solve_task` → `loop.gate=pass`	Writes `featureMemoryRecord` with `featureId`
Every `plan_task`	Returns `featureMemory.recordKeeping` (+ prior matches when found)
Matrix improves	Dashboard notification + optional email

Opt out (exceptional): input.featureMemory.capture=false

Manual refine only: capture_feature — adjust title/requirements or supersedesFeatureId.

Meta-tools (free — no credits)

Tool	Role
`plan_task`	`featureMemory.recordKeeping` + hybrid match reminders
`list_feature_memory`	Browse your private library
`compare_feature_memory`	Matrix diff between two features
`publish_feature_pattern`	Opt-in community share (project redacted)
`list_community_patterns`	Browse anonymized community patterns

Typical loop

1. plan_task("add OCR for invoices")     → read featureMemory.recordKeeping + priorInstances
2. run_playbook / solve_task + fixes     → verify_task until loop.gate=pass
3. ToolYour records featureMemoryRecord  → fm_… stored (no extra agent step)
4. Later in another project              → plan_task surfaces reminder + capabilityGaps

`plan_task` envelope

{
  "featureMemory": {
    "schemaVersion": "toolyour.featureMemory@1",
    "recordKeeping": {
      "policy": "toolyour_auto_record",
      "message": "ToolYour is your cross-project institutional memory…"
    },
    "domain": "ocr",
    "matchConfidence": "high",
    "bestKnown": { "featureId": "fm_…", "compositeScore": 87 }
  }
}

On gate pass

{
  "featureMemoryRecord": {
    "status": "recorded",
    "policy": "toolyour_auto_record",
    "featureId": "fm_…",
    "message": "ToolYour recorded this completed feature…"
  }
}

Dashboard

Signed-in developers: toolyour.com/dashboard/feature-memory — captured features, improvement notifications, opt-in community publish.

CI capture (optional)

If verify ran outside MCP, use npm run ci:capture-feature in the toolyour-mcp repo (scripts/ci-capture-feature.mjs). See examples/github-actions/capture-feature.yml.

Matching

Hybrid 35% token + 65% embedding on requirements (matchMethod: "hybrid_embedding"). Optional communityPatterns from opt-in publishes.

Privacy

Private per account by default
Community publish redacts projectName / repoHint

Feature Memory (MCP)

On this page