freecontext

# FreeContext routing At any phase, use read-only `tools.mcp__freecontext__gather_context` for one unresolved fact or relationship to replace the next substantial investigation you would otherwise do. If the small edit-context read Main needs anyway can settle it, stay native. Delegate as the unknown emerges; do not finish the investigation first, request a recap of already-read code, or call routinely at task start. Keep overall diagnosis, design, edits, tests, and local fixes in Main. ## Request Send one small object: ```js { question: "When parseRows emits two rows with the same key, which value reaches writeRow, and what condition can change that?", hints: "Current operation: per-row imports; last-row-wins semantics must be preserved. Checked: parseRows preserves input order. Unknown: whether a caller filters or reorders duplicates before writeRow. Batching is only a proposal; equivalence is unverified." } ``` FC sees only `question` and optional `hints`, not the original task or conversation. Include the original operation and semantics to preserve, relevant checked facts, and the remaining unknown; label proposed changes and unverified assumptions. Ask how the uncertain existing relationship works and under which conditions, rather than how to build the feature. Expect ordinary assistant text resolving that uncertainty with the decisive short code excerpt, signature, or branch, observed `path:line` and symbol, and adjacent conditions that affect the conclusion. Source-grounded inferences should state their assumptions; design choices remain with Main. Treat supported located facts and their conditions as already-read context; do not reread every listed file to confirm the answer. Read exact edit locations and narrowly check gaps, contradictions, or new design/test premises using existing evidence first. Any FC design suggestion is not a verified conclusion. Delegate a new substantial unknown when useful during work; no failed test, new module, or call count is required. ## Dispatch Call the exact method directly and alone. In the first gather code-mode cell, begin with `// @exec: {"yield_time_ms": 300000, "max_output_tokens": 12000}`. Await the terminal result; if it still returns a cell, call the outer `wait` tool with its returned `cell_id`, `yield_time_ms: 300000`, and `max_tokens: 12000`, with no native tools during the wait. If the call fails, continue directly with native exploration and do not repeat the same question.