Shadow Workspace: Iterating on Code in the Background
cursor.com · 4,000 words · saved by 1 readers
Hidden windows and kernel-level folder proxies to let AIs iterate on code without affecting the user.
Blog / research Here’s a recipe for failure: paste a few relevant files into a Google Doc, send the link to your favorite p60 software engineer who knows nothing about your codebase, and ask them to fully and correctly implement your next PR inside the doc. Ask an AI to do the same and it will also, predictably, fail. Now, instead give them remote access to your development environment, with the ability to see lints, go to definitions, and run code, and you may actually expect them to be somewhat helpful. Figure 1: Would you rather debug your pin-boxed future lifetimes in your code editor or i
related reading
- A Guide to Claude Code 2.0 and getting better at using coding agents – sankalp's blogsankalp.bearblog.dev
- Why We Built Our Own Background Agentbuilders.ramp.com
- How I Use Claude Code | Philipp Spiessspiess.dev
- Claude Code is My Computer | Peter Steinbergersteipete.me
- Cursor: AI coding agentcursor.sh
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- More problemscursor.com
- Best practices for Claude Code - Claude Code Docsanthropic.com
- How Claude Code is built - by Gergely Orosznewsletter.pragmaticengineer.com
- Effective harnesses for long-running agents \ Anthropicanthropic.com
- Cursor: AI coding agentcursor.com
- Cursor: AI coding agentcursor.com