Repository navigation
feat(mcp): history_for and history_search replace eleven history tools - #1449
Merged
Merged
Conversation
Contributor
SCIP oracle — resolution reportHeuristic→compiler edge resolution per corpus. Δ compares resolved-after to the
resolved = |
This was referenced Sep 23, 2026
skakri
force-pushed
the
feat/mcp-history-tools
branch
from
September 23, 2026 20:09
3520786 to
9bf1393
Compare
Refs #1440 (slice 3). An agent asking "why is this code like this?" had eleven tools to choose from, split by target type (path, symbol, chunk, commit) and source (git, tracker) rather than by the question. Two now cover them: - history_for: exactly one target — a symbol (symbol / ref / id), a path, a chunk_id or a commit — and returns { commits, blame, tracker } for the parts that target supports; include narrows, and naming a part the target lacks is an error naming what it does support. - history_search: { query, source } with source commits, changes (commit messages plus the files they changed), issues or rationale. Both dispatch to the handlers they replace, so their answers cannot drift from the old tools'. The eleven old names stay callable for one release but are no longer listed, and every result from one carries a separate content block naming the replacement call; the payload is unchanged. Because clients only let a model call listed tools, the using-rag-rat and dream-review skills, README, docs/mcp-tools.md and docs/distillation.md move to the new names in the same change; the skill's tool table also marks which tools now need the admin or graph toolset.
A --json client may join the text blocks before parsing; the prose note would break the JSON it expects. Like the stale-memory nudge, it is TOON only.
skakri
force-pushed
the
feat/mcp-history-tools
branch
from
September 23, 2026 20:09
9bf1393 to
7bd0517
Compare
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third slice of #1440. Stacked on #1442.
Why. An agent asking "why is this code like this?" had eleven tools, split by target type (path, symbol, chunk, commit) and source (git, tracker) rather than by the question.
New tools
history_for— exactly one target: a symbol (symbol/ref/id), apath, achunk_idor acommit. Returns{ commits, blame, tracker }for the parts that target supports (symbol/path → commits, tracker; chunk → blame, tracker; commit → tracker, withfallback).includenarrows; naming a part the target lacks is an error that names what it does support.history_search—{ query, source },source∈commits,changes(messages + the files they changed),issues,rationale.Both dispatch to the handlers they replace, so they cannot drift from the old tools' answers.
Deprecation. The eleven old names stay callable for one release, are no longer listed, and (TOON output) carry a separate content block naming the replacement call — payload unchanged;
--jsonoutput stays pure JSON.Docs and skills move in the same change, since clients only let a model call listed tools:
using-rag-rat(its tool table also marks what now needs theadmin/graphtoolset),dream-review, README,docs/mcp-tools.md,docs/distillation.md.Effect: the default list is 24 tools / 33.8 KB (33 / 38.0 KB after #1442).
Tests (each mutation-checked): each target returns its parts and
history_for {path}'s commits equalgit_history_for_path's; ambiguous targets and unsupported parts are refused; eachhistory_searchsource routes to its search (on a fixture with a real commit, so the commit searches differ —issuesvsrationaleboth answer[]without a tracker cache, noted in the test); a deprecated name answers with a note in TOON and pure JSON under--json. MCP and CLI suites pass; clippy clean.