Quality control for your software factory.
We just launched Continue on Product Hunt.
Source-controlled AI checks on every pull request.
Would love your support: www.producthunt.com/products/con...
this one goes out to the agents in the factories
30 tickets of product debt. 8 waves of parallel Claude Code sessions. Between waves, a trip to the post office. By the end: +283 net lines and a map of every moment that actually required a human.
Yesterday I shipped 29 PRs, renewed my passport, and had two conversations that landed on opposite ends of the same question.
blog.continue.dev/283-net-line...
11 checks for one HTML file. Each protects a decision easy to violate when agents open PRs. Writing them forced us to say what "good" means. Tests for your taste.
See the checks: github.com/continuedev/amplified.dev/tree/main/.continue/checks
Try it: continue.dev/walkthrough
"Resist Complexity": "The site is HTML, CSS, and images. That's the point. Don't add what you don't need."
No npm. No Tailwind. No React. CSS in a style tag. Not a problem to solve — a decision. The check enforces it every PR, especially from agents that love adding deps.
The site has two hidden features. Type "amplify" and the text lifts, lavender glows: "↑ the work moves up." There's also j/k navigation — zero UI. If you know, you know.
Each has its own check. Both share one rule: zero visual footprint.
"Accessibility as Care" — "The site should work for everyone — not just developers on MacBook Pros, but the people you love who don't have a framework for what's happening."
Reduced motion. Descriptive alt text. WCAG contrast. Each rule is a small act of noticing someone exists.
"No Product Creep" watches for the site drifting from essay toward marketing. Analytics scripts, newsletter signups, CTAs to commercial pages.
The site's power comes from what it is not. The moment it starts selling, it stops being the thing people share.
The essay has a six-section narrative arc. A check called "Editorial Voice & Narrative Arc" protects it.
Flags corporate language. Enforces second-person voice — peer to peer, not product to customer. Pull quotes must be turning points, not summaries. No linter can do this.
amplified.dev is a single-page essay arguing developers are amplified, not automated. One HTML file, inline CSS, vanilla JS. No frameworks.
We wrote 11 checks for it. Checks don't have to protect code — they can protect taste. Here's what ours look like.
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
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.
We are evolving from vibe coding → vibe engineering → Continuous AI
- Vibe coding = fast AI experimentation
- Vibe engineering = sophisticated AI-assisted production development as individuals
- Continuous AI = orchestrating agents across your entire dev lifecycle as a team
So 🔥
I love when startups do research and just ship in product. Skip the benchmarking theatre.
Introducing Instinct 🐺, a new state-of-the-art open Next Edit model trained by @continue.dev
Runnable with @ollamabot.bsky.social and available today in VS Code
There is so much room for context engineering improvements at large organizations
“Developers will be the ones who drive how many languages we have. Their actions and their stewardship of their niche programming languages will determine whether we have more or less”
- @ty.energy in 'The programming languages facing an AI-driven existential crisis' by @karimcmack.bsky.social
@continue.dev is hosting the AI Native Dev - SF Meetup at GitHub HQ (thanks to Kevin Crosby!) with @jedi.be and friends ️🔥
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 👍
@ty.energy joined Balaji Sivasubramanian on the DevAI podcast to discuss the open architecture that we believe will underlie the future of AI-native software development 😎
www.youtube.com/watch?v=FwZq...
Read the entire discussion: news.ycombinator.com/item?id=4349...
We launched on Hacker News yesterday! There was a great discussion on custom AI code assistants. In case you, missed it:
It’s critical that an open architecture underlies the future of AI-enhanced software development. This is why we are launching Continue 1.0 with hub.continue.dev today: techcrunch.com/2025/02/26/c...
@continue.dev 👋
I am now @ty.energy 👋
