Jac team rewrites compiler errors to link language docs, helping coding agents fix bugs
JaseciLabs · reddit · 2026-10-21
The Jac language team (JaseciLabs) shares how they adapted their compiler output for coding agents.
The problem: typical errors like "type mismatch on line 12" tell the agent something failed but give it nothing to work with, so it guesses, fixes the wrong thing, or finds workarounds that silence the error without solving it.
Their approach: jac check now points each error to the relevant section of the language guide, giving the agent context on both what went wrong and how the language expects it to be handled—especially valuable for new languages, frameworks, or internal tooling agents don't know.
They ask the community: do you pass through raw output from tsc, ruff, or cargo, or enrich errors with explanations, examples, or doc references? And does enriching actually improve agent fixes?
More from coding & agent
- 90% of big-company knowledge lives in heads, and "company brain" startups are in for pain — gabriel1 · 2026-10-21
- EAU: Co-evolving user simulator, environment, and RL setup for training LLM agents — UAlberta · 2026-10-21
- Meta's Self-Credit: Dense Rewards from Sparse RLVR via Intra-group Rescaling — meta · 2026-10-21
- Notion details its Auto model router: Elo-based evals, 62-93% cheaper than flagship models — ivanhzhao · 2026-10-21
- Dev sets up automation so agents proactively pick up stale issues and PRs — vikvang1 · 2026-10-21
- Tamper-proof agent logs still can't prove the agent did the job: who reads the record back? — ZealousidealAct9661 · 2026-10-21