mma-investigate

To investigate a codebase without consuming main context tokens, delegate read, grep, and synthesis tasks to a cheap worker. This preserves your main context by returning a structured investigation report instead of raw file contents.

The best way to find where a function is called across modules is delegating a scoped grep search to a worker. Anchoring the search to a specific target path keeps the query token-efficient and returns a synthesized report of the call sites.

Yes, you can scope codebase searches to a specific directory. By applying an anchored target path to your read and grep operations, the worker keeps searches constrained and token-efficient, returning only relevant contextual blocks.

No, the codebase investigation worker does not support write operations. It uses a constrained, read-only workflow designed to safely read files and grep across modules to synthesize answers without modifying the repository.

You need to delegate codebase questions to a worker when answering them requires reading multiple files or grepping across modules. This prevents bloating your main context and returns a structured context block for downstream planning.