Coco: An Agentic Copilot for the Hardware--Software Co-Design Lifecycle
On the map: LLM agents and tool use → Software engineering coding agents
Abstract (arXiv)
Co-designing ML models and the accelerators that run them is an unusual reasoning task: architects must draw confident, high-stakes conclusions about systems that do not yet exist, and the pace of both model evolution and hardware cadence means the analysis burden grows every quarter. The evidence behind each decision--hundreds of gigabytes of fresh simulation sweeps over novel design points--is by construction absent from any LLM's pretraining corpus, and there is no external literature to retrieve; naive "chat-with-your-data" approaches hallucinate exactly where correctness matters most. We present Coco (Copilot for Codesign), an agentic platform deployed with TPU architects that accelerates the co-design lifecycle of setting up experiments, sweeping simulators, and deriving insights. Coco is built as four layers: (i) a datastore that automatically registers every simulation sweep into a normalized relational schema, so agents ground every number in a SQL query rather than scraping heterogeneous files; (ii) a library of tools with typed APIs that agents compose without human orchestration; (iii) agents that encode recurring analysis workflows--most notably iso-execution analysis, which compares systems at matched execution configurations, including swept-but-dominated points off the Pareto frontier; and (iv) a platform UX whose navigation state doubles as agent context. We report early deployment experience toward a reduction in time-to-simulation and time-to-insight, and argue that co-design is a distinct agentic domain: its data must be retrieved rather than memorized, its workflows are recurring but context-dependent, and expert adoption hinges on UX that balances IDE-style control with interactive exploration.
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. First posted on arXiv 1 Oct 2026.
Builds on
No reference list yet.
Built on by
Not cited yet.
Similar, not cited
Close in wording, no citation either way
- 2026Agentic Hardware Design as Repository-Level Code Evolution
- 2026Agentic Architect: An Agentic AI Framework for Architecture Design Exploration and Optimization
- 2026Is Agentic AI Ready for Real-World Hardware Engineering? A Deep Dive with Phoenix-bench
- 2025DUET: Agentic Design Understanding via Experimentation and Testing
- 2026From Pragmas to Partners: A Symbiotic Evolution of Agentic High-Level Synthesis
- 2026Benchmarking AI Agents for Hardware Design Automation via MCP Tool Calling
- 2026RefEvo: Agentic Design with Co-Evolutionary Verification for Agile Reference Model Generation
- 2026Grounding SWE-Agent Decisions in Architecture-0 Design: Navigating Unknown Unknowns through Physical Mapping