Oops! Something went wrong
[next-mdx-remote-client] error compiling MDX: Expected a closing tag for `<final_answer>` (5:299-5:313) before the end of `paragraph` 3 | ## Key Findings 4 | - Separation pays: moving exploratory reads outside the solver reduces the main agent's token consumption by up to ~60% while improving end-to-end resolution rates by up to ~5.5% in reported benchmarks. This means the solver keeps a cleaner context window and spends more tokens on planning/editing rather than file hunting. > 5 | - Lightweight, trainable explorers: the paper trains 4B–30B exploration models (bootstrapped with supervised trajectories and refined with task-grounded RL) to optimize for broad first-turn coverage, multi-turn evidence gathering, and precise citation generation. Trained explorers produce compact <final_answer> blocks of file paths and line ranges instead of pasting large code snippets. | ^ 6 | - Practical tool set and workflow: FastContext exposes only read-only tools (READ, GLOB, GREP) and supports parallel tool calls per exploration turn. The intended contract is simple: the main coding agent invokes FastContext for context; FastContext returns focused citations; the main agent edits/tests/answers using that evidence. 7 | More information: https://mdxjs.com/docs/troubleshooting-mdx