SkillsMay 12, 2026·2 min read

MiroThinker — Open Deep Research Agent with 256K Context

MiroThinker is an open deep-research agent stack with long context, tool-heavy configs, and benchmarked BrowseComp results for serious evaluation work.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Stage only · 29/100Stage only
Agent surface
Any MCP/CLI agent
Kind
Skill
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Universal CLI install command
npx tokrepo install 7f3da23a-cf7d-541d-beeb-01a11a3c895b
Intro

MiroThinker is an open deep-research agent stack with long context, tool-heavy configs, and benchmarked BrowseComp results for serious evaluation work.

  • Best for: research teams benchmarking long-horizon, tool-rich open agents
  • Works with: Python 3.10+, uv, E2B sandbox, Serper, Jina, summary LLMs, YAML agent configs
  • Setup time: 30-60 minutes

Practical Notes

  • Quant: MiroThinker-1.7 is documented with 256K context and up to 300 tool calls per task; older v1.0 notes mention up to 600 calls.
  • Quant: the README highlights BrowseComp 74.0 and BrowseComp-ZH 75.3 for the 1.7 line, plus multiple keyed environment variables for the minimal tool set.

Rollout pattern

  • Treat the minimal tool set as the baseline and resist adding optional tools until you can reproduce one benchmark-like task.
  • Log environment variables and configs per run so your benchmark notes are reproducible.
  • Use it to learn what long-horizon research agents require operationally, not as a trivial one-command chatbot replacement.

Watchouts

This stack has more moving parts than a typical app-facing agent, so missing keys or mismatched tool configs will produce noisy failures unless you document the environment carefully.

FAQ

Q: Is it a simple local chat app? A: No. The README positions it as a tool-enabled research agent with multiple required services and configs.

Q: Why is it worth studying? A: Because it publishes measurable context, tool-call, and benchmark facts that are useful for replication.

Q: What should I verify first? A: One recommended YAML config plus the three-tool minimal setup for search, scraping, and execution.

🙏

Source & Thanks

Source: https://github.com/MiroMindAI/MiroThinker > License: Apache-2.0 > GitHub stars: 8,223 · forks: 626

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets