Repository navigation
graph read steps: describe the graph by what it holds - #136
Merged
Merged
Conversation
…tadata graph-search told the model it searches 'the strut knowledge graph … workflows, steps, runs, chats'. An explore agent with repositories on disk read that as strut metadata and grepped instead (swarm38 explore 1791645592048: 15 fulltext_search, 0 graph calls), though the graph holds the code parsed from those repositories (File, Function, Endpoint with descriptions). The read steps now say 'the knowledge graph', and graph-search names the code types and the type filter.
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.
An
exploreagent with repositories checked out never called the graph tools. Swarm38 run1791645592048made 15fulltext_searchcalls and 0 graph calls, even though the swarm's graph holds those repositories parsed (File,Function,Endpointnodes with written descriptions). Part of the reason:graph/graph-searchdescribed itself as searching "the strut knowledge graph … workflows, workflow versions, steps, runs, agent sessions, tool calls, chats, turns".graph-search's description now says it searches any type the graph holds, names the code types a swarm ingests, and points totypefor narrowing (e.g.Function,File,Endpoint).graph-get,graph-neighbors,walkandget-ontologynow say "the knowledge graph" instead of "the strut knowledge graph". The write steps keep their wording.Checked on swarm38:
graph/get-ontologylistsFile,Function,Endpoint,Repository, and a typedgraph-searchreturns code nodes.The other half, a prompt that says which repos are in the graph, is the mcp
exploreseed (separate stakgraph PR).Description text only. tsc clean,
npm test1416/1416.