What problem does it solve? Writing a rigorous, citation-backed history of a research field requires hours of literature searching across eras, and generic search often misses either foundational classics or the latest arXiv frontier work. ## Core Features & Use Cases - Two-track parallel retrieval: Runs the mechanic-db SEARCH service twice in parallel β one pass with temporal_mode=history for the long arc and one with temporal_mode=recent for the modern frontier. - Web supplementation: Uses WebSearch to fill gaps for pre-database classics and arXiv papers from the last 1β6 months that the database has not yet indexed. - Graceful degradation: If the database service is unavailable, the article is still produced from WebSearch and model knowledge, with an explicit availability note. - Use Case: Ask for a development history of mechanistic interpretability and receive a 2500β4500 word markdown article organized by eras, with verified citations, a frontier section, and a Tensions and Open Questions section saved to development_history.md. ## Quick Start Ask the agent to trace the development history of your research topic, for example by invoking /mhistory followed by the topic name.