Ty Dunn
@ty.energy
Read more on the Continue Blog: blog.continue.dev/from-vibe-en...
From Vibe Engineering to Continuous AI
Vibe coding emerged earlier this year to describe fast, loose experimentation with AI.
Now, Simon Willison has proposed "vibe engineering":
Vibe coding is irresponsibly building software through dic...
blog.continue.dev
October 8, 2025 at 9:10 PM
Read more on the Continue Blog: blog.continue.dev/from-vibe-en...
Continuous AI isn't about removing developers—it's about working at the right abstraction level.
Sometimes that's hands-on vibe coding
Sometimes careful vibe engineering
Increasingly, it's orchestrating remote agents while staying accountable for what ships
Sometimes that's hands-on vibe coding
Sometimes careful vibe engineering
Increasingly, it's orchestrating remote agents while staying accountable for what ships
October 8, 2025 at 9:10 PM
Continuous AI isn't about removing developers—it's about working at the right abstraction level.
Sometimes that's hands-on vibe coding
Sometimes careful vibe engineering
Increasingly, it's orchestrating remote agents while staying accountable for what ships
Sometimes that's hands-on vibe coding
Sometimes careful vibe engineering
Increasingly, it's orchestrating remote agents while staying accountable for what ships
The shift happens when you trust an agent to run 5+ minutes unsupervised. You get bored waiting, so you spin up a second agent. Then three. Four. Five.
Suddenly your whole team is doing this and you need: secure execution, event-driven triggers, overnight runs, monitoring, etc.
Suddenly your whole team is doing this and you need: secure execution, event-driven triggers, overnight runs, monitoring, etc.
October 8, 2025 at 9:10 PM
The shift happens when you trust an agent to run 5+ minutes unsupervised. You get bored waiting, so you spin up a second agent. Then three. Four. Five.
Suddenly your whole team is doing this and you need: secure execution, event-driven triggers, overnight runs, monitoring, etc.
Suddenly your whole team is doing this and you need: secure execution, event-driven triggers, overnight runs, monitoring, etc.
It's hard to tell from your screenshot, but it looks like it didn't use your MCP server. You need to be in Agent mode, and the MCP needs to be connected, which you can verify in the notch. Then you should see the tool from the MCP being used 👍
April 29, 2025 at 6:03 PM
It's hard to tell from your screenshot, but it looks like it didn't use your MCP server. You need to be in Agent mode, and the MCP needs to be connected, which you can verify in the notch. Then you should see the tool from the MCP being used 👍
Read the entire discussion: news.ycombinator.com/item?id=4349...
March 28, 2025 at 4:10 PM
Read the entire discussion: news.ycombinator.com/item?id=4349...