Cursor should add a direct Grok Build backend, says a new ACP integration proposal
Daniel_Farinax · x · 2026-07-27
Proposal: let Cursor run Grok Build as a direct backend via ACP
The post argues that Cursor should add a “Direct Grok Build” mode: strip out Cursor’s own agent middleware and turn the desktop app into a pure GUI frontend that talks directly to Grok Build.
It says Grok Build already exposes the Agent Client Protocol (ACP) through grok agent stdio or grok serve --protocol acp --port 9120, and Cursor already has ACP client support plus an Agent Backends setting. The suggested integration would:
- auto-detect a local Grok binary and auth
- surface plan mode, parallel subagents, worktrees, skills, MCP, and clean diffs natively
- let Grok Build become the actual runtime instead of Cursor’s own agent loop
The image shows a mock Cursor/Grok setup with coding UI and project controls, reinforcing that the idea is about a first-class developer workflow integration rather than a general consumer feature.
More from coding & agent
- New tool puts Claude, Codex, Grok in shared sessions with your teammates — sergeykarayev · 2026-09-23
- Dev claims 20k more commits coming: Opus 5.5 and GPT-6 Sol supercharge his output — doodlestein · 2026-09-23
- A JEV-powered Wireshark classifier accidentally uncovered real backdoors on a home network — multiply_matrix · 2026-09-23
- 299 real intents tested: classifier routing trails GLM-4-Flash by 3 points but is 6.5x faster — Sufficient_Flower860 · 2026-09-23
- OpenExecutive: open-source virtual executive team of 8 specialist AI agents hits 5.1k GitHub stars — tom_doerr · 2026-09-23
- Framer launches Skills: teach your design agent reusable workflows, design systems and CMS rules — soleio · 2026-09-23