Ghostty author runs agent loop to cut renderer frame times 88ms to 1.5ms, warns of agent psychosis
stuffyokodraws · x · 2026-09-28
Ghostty creator Mitchell Hashimoto shared an experiment letting a coding agent optimize a renderer in a loop.
- He rewrote Ghostty's core render state in Go as a deliberately naive renderer: 88ms per frame with 150K allocations, backed by identical validation tests
- Constraints: agent can't touch input data structures, public API, or tests — anything else was fair game
- After 4 hours and $350, the agent got frame times from 88ms to 1.5ms and allocations down to 500
- But he stresses this is exactly why "agent psychosis" is a serious problem: impressive surface results demand scrutiny of what shortcuts the agent actually took
More from coding & agent
- Baseten's Guide: Evaluate Open Models for Coding Agents on Your Own PRs — baseten · 2026-11-16
- Google Research open-sources PaperOrchestra, a multi-agent framework for writing AI papers — google-research · 2026-11-16
- ffmpeg-skill gives coding agents local video editing via 42 FFmpeg tools and MCP — kajisho5 · 2026-11-16
- Agents Now Reply to Slack Messages on Their Own, Resolving a Prod Incident Ghost-to-Ghost — iamrobotbear · 2026-11-16
- Engineer's Interview Prep Method: Use Claude to Find Which Answers Undersell Your AI Work — brandon_galang · 2026-11-16
- DeepSeek open-sources its app frontend "chat-demo", already at 3.9k stars — NielsRogge · 2026-11-16