v0.7.0: full GitNexus 1.6.x tool coverage, TOON output, TUI renderers - #20
Open
yolonir wants to merge 10 commits into
Open
v0.7.0: full GitNexus 1.6.x tool coverage, TOON output, TUI renderers#20yolonir wants to merge 10 commits into
yolonir wants to merge 10 commits into
Conversation
- 9 new tools: trace, explain, check, route_map, tool_map, shape_check, api_impact, group_list, group_sync - gitnexus_query absorbs pdg_query via pdg: controls|flows param - existing tools catch up with 1.6.x schemas: branch, service, kind, impact mode=pdg/line/target_uid/limit/offset/summaryOnly/crossDepth, cypher params, list_repos limit/offset - settings toggle "PDG analysis": run analyze with --pdg
- MCP JSON re-serialized to TOON (~45% token cut on real payloads), trailing guidance text preserved - renderCall: tool name + key args; renderResult: 15-line preview with expand hint (pi grep renderer pattern) - dep: @toon-format/toon
…us <Name> <args>'
Verified against live MCP: [:TYPE] fails ('Table X does not exist' — rels are
one generic table, filter r.type), type() is missing, schema resource documents
labels/props. Prevents the error loops agents hit when writing Neo4j-style queries.
The 8KB cap sliced raw JSON in the MCP client, so large responses (e.g. detect_changes with 252 symbols) arrived as broken JSON and bypassed formatting entirely. Now callTool takes an optional cap: tool results pass 0 (untruncated) and the budget is applied to the TOON-formatted text, so valid JSON always reaches the formatter. Augment injections keep the raw cap.
When the analyzePdg setting is on, the gitnexus_query description tells the model the PDG layer is present and to prefer pdg:'controls'/'flows' for data/control-flow questions. No auto-routing — search stays search, PDG is opt-in per call, so no information is lost.
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
1 participant
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.
What
Brings the extension up to date with GitNexus 1.6.x and improves output economics:
gitnexus_queryas apdgparam), check, route_map, tool_map, shape_check, api_impact, group_list, group_sync; existing tools gained new params (branch, service, mode, line, crossDepth, ...){markdown}payloads print verbatimGitnexus Cypher query=...) + 15-line result preview with ctrl+o expandanalyze --pdg), startup-notice toggle[:TYPE]syntax, notype(), filterr.type) — verified against live MCP; prevents agent error loops with Neo4j-style queries--pdg,gitnexus_querydescription advertises the pdg paramVerification