Remove markdown-emit endpoints (dispatch / structural-asks / agents-drift) #37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-14T22:48:41Z - https://github.com/coilysiren/repo-recall/issues/150
Make repo-recall fully read-only. Today three endpoints write markdown into discovered repos:
POST /api/repos/{id}/dispatches+mcp::recall_record_dispatch-><repo>/docs/repo-dispatch/<slug>.mdplus mirror at~/.repo-recall/dispatch/<repo>/<slug>.md<repo>/docs/structural-asks/<slug>.mdplus mirror<repo>/docs/agents-drift/<slug>.mdplus mirrorReasoning: the autonomous engineering flow that motivated these emitters belongs to the agent driving the MCP session, not to repo-recall. repo-recall reads. The agent writes through whatever its own tooling already supports (gh issues, direct git, etc.). Removing the writes simplifies the security model (cache-only writes), tightens the IO surface, and removes a feature that no consumer outside the autonomous loop calls.
Scope:
POST /api/repos/{id}/dispatchesandrecall_record_dispatchMCP toolsrc/display/dispatch_artifacts.rs(write-once emitter)src/process/structural_asks.rs(keep the read path that ingests existing files)src/process/agents_drift.rs(keep the read path)REPO_RECALL_DISPATCH_ROOT,REPO_RECALL_STRUCTURAL_ASKS_ROOT,REPO_RECALL_AGENTS_DRIFT_ROOTfrom config schemaOut of scope:
Designed in chat 2026-05-14.