Query the local AST-derived code graph (functions, classes, calls, imports) for structural codebase questions — what calls X, what does Y import, where is Z defined, blast radius of a change. The graph rebuilds automatically after each agent turn; use hivemind_graph_search and hivemind_graph_neighborhood tools (no manual build step).
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
A deterministic, AST-derived map of the current repository — every function,
class, method, interface, type, enum, const, and module, plus the edges between
them (calls, imports, extends, implements, method_of).
The graph builds and refreshes automatically after each turn (gated by rate limit + git diff). You never run a build command — just call the graph tools.
Set plugins.entries.hivemind.config.tuning.HIVEMIND_GRAPH_CWD in
~/.openclaw/openclaw.json to the git root of the project you want indexed
when the gateway's working directory is not the repo (then restart the gateway).
Use the graph as a fast INDEX to locate the few files/symbols that matter, then use the host's read/exec tools on the real source. It is not a substitute for reading source files.
Activate when the user asks a structural / relational question about the code:
pushSnapshot?" / "Who uses this function?"deeplake-pull.ts import?" / "What depends on X?"GraphSnapshot defined?" / "Find the function that handles Y."hivemind_graph_search({ pattern }) — search symbols by substring (or
multi-token AND with +, e.g. auth+handler). Returns matches with 1-hop
neighbors (callers, callees, imports). Start here.hivemind_graph_neighborhood({ file }) — every symbol in a repo-relative
file path plus its cross-file neighbors.hivemind_graph_search({ pattern: "<symbol>" }).hivemind_graph_neighborhood({ file: "src/hooks/capture.ts" }).source_file:line from the tool output with
the host read tool — don't answer from the graph alone.pattern is lexical, not semantic — try multiple keywords if the first misses.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.
The English summary is being prepared. Showing the original description.
Create, track and update team goals in Hivemind via the `hivemind` CLI. Use whenever the user mentions a goal, objective, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy `hivemind tasks` CLI and now covers both objectives and tasks.
The English summary is being prepared. Showing the original description.
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/. Use whenever the user mentions a goal, objective, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy `hivemind tasks` CLI and now covers both objectives and tasks.
The English summary is being prepared. Showing the original description.
Create, track, and read team goals via Hivemind from openclaw. Use whenever the user mentions a goal, objective, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X", or any actionable work item — the goal system replaced the legacy `hivemind tasks` CLI and now covers both objectives and tasks.
The English summary is being prepared. Showing the original description.
Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of changing this?". The graph is an AST-derived map of the repo, queried as files (no build needed — it rebuilds automatically).
The English summary is being prepared. Showing the original description.
Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what is the architecture / which subsystems exist?". The graph is an AST-derived map of the repo, queried as files (no build needed — it rebuilds automatically).
The English summary is being prepared. Showing the original description.