How Noodlbox Works
Noodlbox analyzes a repository once, then retrieves a small, relevant slice for each task.
Analyze once
Section titled “Analyze once”nbx analyze .Analysis parses source, resolves symbol identity across files, and records typed relationships such as calls and imports. From that model, Noodlbox derives functional communities and ordered execution workflows.
This is why Noodlbox can distinguish a large file from an important entry point, or a matching name from the definition actually used by a workflow.
Retrieve per task
Section titled “Retrieve per task”nbx search "auth refresh flow"Search starts from relevant symbols, follows their resolved connections, and returns the workflows and definitions that belong together for the task.
Inspect precisely
Section titled “Inspect precisely”nbx def refreshTokenDefinition context gives one symbol’s location, body, callers, dependencies, and community. Use nbx query when you need to ask an exact graph question.
Review current work
Section titled “Review current work”nbx diffnbx verify --digestThese commands compare the working tree with the analyzed baseline and surface structural changes that deserve review.
The practical model
Section titled “The practical model”- Repository → analyze once → local structural model
- Task → search → relevant code paths and definitions
- Change → diff and verify → structural review evidence
Noodlbox supplies code-structure evidence. Source inspection, project tests, logs, and runtime traces remain the authority for behavior.