Page 1 • Showing 9 tweets
Here's how I'm coding with AI lately, might be helpful! 1. I write code primarily using agents, using models like Opus 4.5 and Codex Max for long-running tasks or tricky bugs, and Composer for frontend changes or fast updates (I still review the code). 2. Most of my web dev work happens inside the integrated Cursor browser. This is similar to using the Playwright or Chrome MCPs. Cursor can access network requests, console logs, and send elements on the page to the agent. It can also control the browser! Which can be fun for having it do automated testing: https://x.com/cursor_ai/status/1999147953609736464… 3. I start projects pretty simple: no upfront rules, commands, or anything. As the project grows, I end up adding the most minimal versions needed. Some examples in this thread: https://x.com/leerob/status/2006043265817071926… 4. I heavily review all the code! Just because I'm using agents, I'm still thinking deeply about the architecture and code quality. I review the code in three passes: first, while the agent is generating it. Second, using the in-editor "agent review" before I push a PR (similar to a custom /code-review command). And finally, using Bugbot (AI code review) on my PRs. This combination helps me fix a lot of silly bugs before I ask other people to take a look at the code. 5. I always start new features with a plan (using Plan Mode). This helps significantly and I would highly recommend planning first regardless of what tool you use. I do like the Cursor UX for visualizing, editing, and saving the plans. You can view some of my plans here: https://github.com/leerob/pixo/tree/main/.cursor/plans… 6. For really hard bugs, I use Debug Mode. It automatically instruments your app with logging, and then asks you to reproduce the issue. The agent then reads the logs and has much more helpful context to pinpoint the root cause. It also comes up with multiple theories on what the issue could be, and works through each one until it's fixed. Has been pretty helpful: https://x.com/cursor_ai/status/1998821350333440133… 7. Always make sure you give coding agents verifiable outputs! They can't fix what they don't know about. For this, I would prefer using typed languages, and set up tools like linters and good tests. These are normal software engineering best practices, but they matter more than ever. There's also newer tools here like tsgo and biome/oxlint and bun which make dev really nice. Worth trying some of those if you do web dev. 8. I use Cursor from mobile! There's really two modes here: quick bug fixes or really big tasks. Quick bug fixes, I just pop open http://cursor.com/agents and fire away, knowing I'll get back a PR that will work 99% of the time and I can merge away. Easier than writing it down on a todo list, my PR queue is now that list. For big tasks, again I start with a plan and then I give the agent an ambitious goal (that is verifiable!). This allows the agent to run for much longer. It will keep going until it hits that goal, and if it gets lazy, you can just say "keep going" and go back to what you were doing. This is all in the cloud, in remote sandboxes, so I don't have to worry about my local machine. 9. Since someone will ask about the theme... yes I'm rocking light mode most of the time, using Cursor Light here Oh and if you're a car person... more on my car below soon
Learn about tool calling in under 3 minutes! Tools give AI models superpowers. They can read and write files, search code, search the web, run shell commands, and more.
Cursor 2.3 is starting to roll out! We’ve spent the past two weeks fixing bugs and making reliability improvements based on your feedback. I’m so proud of our team for sprinting to make this our best release yet. We’ll be rolling 2.3 out over the week to ensure there are no regressions during your holiday coding. I also wanted to shout out @theo, who had a rough experience with Cursor and was kind enough to stop by our office and give the team a ton of feedback on how we can make the product better (including helpful reproductions of issues from their team). There are a number of bugs in this release, specifically around worktrees and plan mode, that were fixed thanks to him. Thank you! There’s also been feedback on layouts and the default panes in Cursor across X and Reddit in the past week. We’ve been digging in and listening, and I hope you’ll love where we’ve landed. It’s always been slightly annoying if you’re using Cursor with 3+ different windows open for different repos. I was talking to @schickling about this last month, and we wanted a way to better hop between different workspaces. I still think there’s more we can do here, but I really like the new Command+Option+Tab switcher to move between layouts and workspaces (thank you @JasonBud!). Since I use Command+Tab on macOS all the time, this feels very familiar. Especially when defining custom layouts like in the video below to keep my terminal always open. We’d love your feedback as we keep working to make Cursor more extensible and customizable. Another small but nice thing: we heard your feedback that it's frustrating to have releases rolled out before the changelog is live, so we made sure the 2.3 changelog was posted before you saw the update button. Speaking of the update button, while it's great we're getting updates out frequently... I also agree it can be annoying to see the update banner every time you open Cursor. We've made it so this banner will show less frequently Happy holidays everyone!
Nice quality-of-life improvement to Cursor. You can now create and save custom layouts, so Cursor will remember the exact position of sidebars, terminals, etc. We hope to make this even more customizable!
Cursor 2.0 can now: 1. Use any frontier model or our own agent model 2. Run multi-agents with built-in git worktrees 3. Create plans with one model, implement with another 4. Review + create a PR in one click 5. Close your laptop and handoff to the cloud What should we do next?
My year in code with Cursor! Well only my past 6 months since I got a team account, so I'm not making the top of any leaderboards haha. Whoever responds with the most tokens used building, I'll send you a bunch of Cursor credits
Cursor now has a built-in web browser. You can say "start my app" and it will run the dev server in a terminal and then navigate the browser to localhost:3000. It can take screenshots of the page for iterating on design, and you can send DOM elements to the agent with prompts!