| name | accint-solve |
| description | Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence. |
| category | ai-agents |
| risk | safe |
| source | community |
| source_repo | maxbaluev/accreted-intelligence |
| source_type | community |
| date_added | 2026-06-15 |
| author | maxbaluev |
| tags | ["mcp","memory","ai-agents","coding-agents","workflow"] |
| tools | ["claude","codex","cursor","gemini","opencode"] |
| license | Apache-2.0 |
| license_source | https://github.com/maxbaluev/accreted-intelligence/blob/main/LICENSE-APACHE-2.0.txt |
AccInt Solve
Overview
AccInt is a local-first MCP memory server for coding agents. It keeps a scored
record of retrieved experience, open commitments, continuation frames, and
outcome feedback so the next agent run can build on what actually worked.
Use this skill when AccInt is already configured in the host as an MCP server.
The skill adapts AccInt's public solve Claude skill into a host-agnostic
workflow for Claude Code, Codex CLI, Cursor, Gemini CLI, OpenCode, and other
agent runtimes that can call MCP tools.
When to Use This Skill
- Use when starting non-trivial coding-agent work where prior decisions,
debugging history, repo-specific habits, or maintainer feedback may matter.
- Use when a task may require multiple attempts and you want an explicit
commitment ID that can later receive a real outcome.
- Use when AccInt returns a continuation frame and the agent must reason locally
before submitting a proposal back to the memory loop.
- Use after verification, merge, deployment, maintainer response, or other
reality signal to close the commitment with an honest outcome.
- Do not use when the host has no AccInt MCP tools configured; first install or
configure AccInt, then rerun the workflow.
How It Works
Step 1: Confirm the AccInt MCP tools exist
Use the host's available MCP/tool list to confirm an AccInt server exposes the
two verbs:
acc_retrieve(query)
acc_act(runtime, input)
If the host names the tools with a namespace prefix, use the equivalent
AccInt MCP verbs. If neither verb is available, stop and ask the user to
configure AccInt rather than inventing memory results.
Step 2: Retrieve before planning
Before a non-trivial step, retrieve relevant prior work:
{"query": "the concrete task or subtask you are about to perform"}
Read the returned memories and cite the [ids] you actually build on. Treat
retrieved memories as evidence to consider, not as a substitute for inspecting
the current repository, running tests, or checking live external state.
Step 3: Route the goal through solve
Open an AccInt commitment for the concrete goal:
{"runtime": "solve"
