Gather context
before the move.
One knowledge graph across every repo, surfaced to your AI assistant.
One graph, every repo.
Not a federation of isolated per-repo indexes. A single knowledge graph that spans the whole workspace.
Event flows across services.
Producer to consumer, at shared virtual nodes. Your AI finally sees the edges between repos, not just inside them.
Derived from source, not docs.
Re-indexes incrementally on every file save. What the code looks like today, not what a README said two years ago.
It maps what no other tool maps: event-driven topology.
Producer-to-consumer graphs across repos. Cross-repo edges meet at shared virtual nodes, so blast radius is a query, not a guess.
Six things no other codebase tool ships together.
Partial context is worse than no context. Gather Step commits to completeness: every repo, every event stream, every cross-service edge.
Event-driven topology mapping
Producer-to-consumer graphs across Kafka, NATS, SQS, Redis Streams, and NestJS. No other tool, OSS or SaaS, ships this.
Native polyrepo graph with virtual-node edges
A Kafka producer in repo A and a consumer in repo B share the same Topic node. Not a federation of isolated graphs, one graph.
Framework-aware extraction
NestJS (@Controller, @MessagePattern, DI), Mongoose @Prop, Bull/BullMQ. It understands what decorators mean, not just that they exist.
Contract drift detection
Field-level payload comparison between producers and consumers. Catch a missing required field before it becomes an incident.
Ownership, hotspots, bus-factor
Derived from commit history, not CODEOWNERS. Who actually touches this service, how often, and where concentration risk lives.
Task-shaped context packs
Plan, debug, and review packs shape context to the task at hand. 8K tokens of precision, not 50K of noise.
Context packs, shaped to the step you're on.
Precision over noise. Three canonical packs cover planning, debugging, and review, each returns exactly the subgraph the task requires.
Plan pack
Entry points, cross-repo dependency chains, convention conformance, affected event surface.
Debug pack
Hotspot history, recent co-changes, ownership, upstream producers, downstream consumers.
Review pack
Blast radius for this diff, convention checks, contract drift, cross-repo impact.
Complementary, not competitive.
Gather Step is one thing, done completely, a unified, accurate, always-current knowledge graph of what your system actually looks like. It fits next to the tools your team already ships with.
Memory remembers. Gather Step tracks truth.
Search answers "where?". Gather Step answers "what breaks?".
One unified graph, not a federation.
Install, index, ask.
No API keys. No account. No data leaves your machine.
Point it at your repos.
Gather Step parses source, routes, entities, event producers and consumers, cross-repo dependencies, and builds one graph across the whole workspace.
Run the MCP server.
Your AI coding assistant (Claude Code, Cursor, Copilot) connects over Model Context Protocol and pulls task-shaped context packs on demand.
Ask what actually matters.
Every prompt arrives with structural ground truth. Blast radius. Event consumers. Ownership. Conventions. No more 30K tokens of exploratory prompting.
Index your repos.
No API keys. No account. The graph runs entirely on your machine.