Your software factory is only as good as what gets fed into it. We found a gap in ours: engineers spotting jank in staging and moving on because filing a bug was too much work. So we one-shotted a bug report tool: screenshots, network requests, console logs, straight to Linear

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...

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...

🔊

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.

Introducing Metrics in Continue Mission Control 🚀 Visibility, clarity, and accountability are foundational paths toward trustworthy Continuous AI. Your agents produce real engineering output, and now you can see it all in one place. 🔗 blog.continue.dev/metrics-for-...

If your tools can emit it, Continue should be able to act on it. Introducing Integrations. Now your cloud agents can intake signals from Snyk, PostHog, Sentry, and more to automatically investigate issues and generate PRs. Let Continue Integrations handle the first pass 👇

🚀 Mission Control just got a major upgrade. Your Agents, Tasks, Workflows, and Integrations are now in one clean, fast developer dashboard. From GitHub to Sentry to Snyk, every signal in your stack can now trigger real action inside your repo.

I wrote a post on how I use @continue.dev config to own my AI code review data. Looking forward to improving AI with code reviews I can fine tune. briandouglas.me/posts/2025/1...

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

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

Continuous AI means less intervention, more sophisticated automation, and new enterprise features like audit trails. As these tools mature, the most transformative advances will come from developers who dare to automate beyond the expected. blog.continue.dev/beyond-the-e...

Most of the time, maintaining your codebase and fixing what's broken is the difficult part. That's one of the reasons why we built Next Edit. From callback-to-async conversions to comprehensive bug fixes, it understands real developer editing patterns. 🔗 blog.continue.dev/next-edit-po...

Code editing just got a lot faster.⚡Introducing Next Edit⚡ Next Edit delivers real-time, multi-line suggestions at up to 1100 tokens/sec, powered by @inceptionlabs.bsky.social Mercury Coder, the world’s first commercial-scale diffusion LLM for code.

No one wants to wait for sequential tool calls if they don't have to. That's why at Continue, we have parallel tool calling.

Another great Continue feature: Parallel Tool Calling. Instead of read file A → wait → read file B → wait → read file C, it requests them all at once. 📝 Learn more in our blog: blog.continue.dev/parallel-too...

Want to dig deeper into Plan Mode? We’ve pulled together resources to help you see how it works and why it matters 🧵👇

We're doing something different this week.We're sharing 5 features that show how we think about AI coding tools. Each day, we'll share: The problem we're solving → Why we built it → Developer stories. Follow along if you’re interested in AI tools that fit into your workflow.

Continuous AI is a practical way to transform how teams write, review, and ship code. We’re sharing our definition, the Continuous AI Maturity Model, and the metric that matters most. Read now: continue.ghost.io/ghost/#/edit...

We're excited to have Brian Douglas (@bizza.pizza), Head of DX for @continue.dev, presenting "Continuous AI Best Practice" at #AllThingsOpen! 2025.allthingsopen.org/sessions/con...

Your brain loves shortcuts. So does AI. But fast answers don’t expose deep complexity. They hide it. Dependencies, data flow, edge cases… You won’t see them unless you slow down. Plan Mode forces the pause. So you can think first and build better.

When working with AI agents to write code, the difference between good and great results often comes down to the quality of your rules. Listen to @bizza.pizza talk about the importance of it with Continue. whatthedev.buzzsprout.com/673192/episo...

Your AI assistant forgets everything after each conversation. But what if it didn't? 🧠 reddit.com/r/AIMemory/comments/1m6f3xd/cognee_mcp_is_my_new_ai_memory_for_making_rules/

I once turned a day-long build into 10 minutes by learning cross-compilation. Same energy is happening with AI tools. ‪@chiphuyen.bsky.social‬ tracked AI interruptions (24.5%), found the patterns, fixed her codebase structure. Intervention rates are the new build times 📊

Introducing Plan Mode! Read more about it in the July Continue Newsletter

I loved Docusaurus but it was time to try Mintlify blog.continue.dev/how-we-migra...

I wrote another post on Context Engineering with @continue.dev blog.continue.dev/recurse-ml-r...

Every dimension of designing, delivering, and operating software is changing dramatically. Software Maximalism is the way

There is so much room for context engineering improvements at large organizations

It takes 52 minutes of uninterrupted time to reach flow state. What if that flow state is on your commute? blog.continue.dev/go-offline-w...

Ever wished you could ask "who wrote all the authentication logic?" instead of manually running git blame on every auth-related file? blog.continue.dev/building-a-s...

I wrote AI code offline on a BART train youtu.be/TbJ0gaC0T-E

@chadmetcalf.com was recently a guest on Mike Vizard’s Techstrong show on DevOps sharing his insights and thoughts on AI Coding tools, open-source AI and more Check out his full interview here: techstrong.tv/videos/inter...

Leverage rules as a context provider now in Continue 📜

First post on the @continue.dev blog today. The Anatomy of Rules. blog.continue.dev/the-anatomy-...

"You can both have a great time watching an idea come to life despite barely touching the keyboard and use that experience to sharpen your intuition for what AI can reliably automate in your development process" - @ty.energy in blog.continue.dev/vibe-code-to...

I think there is a way we can all be happy with AI. youtu.be/8fkLZ5oB8Do?...

"They don't want the thing they love, that they were present as kids at the beginning of, to be automated, replaced by human shepherding of natural language and remote agent workflows. I believe folks still yearn to type curly braces" - @chadmetcalf.com from "Am I Nuts or Just Old?"

In the current wave of AI assistant-focused IDEs, it's easy to forget that @continue.dev for #vscode and #intellij was there first. With new ideas & features to use local and remote models, they're working hard to compete & I got a hands-on demo. www.youtube.com/watch?v=iSaI...

“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

I start a new role with @continue.dev next week. What a better way to celebrate than joining me at GitHub for the next AI Native Meetup? lu.ma/87kr0w9r

Check out "Building an AI coding assistant on AWS: A guide for federal agencies" on the AWS Public Sector Blog 🍊 aws.amazon.com/blogs/public...

You ask Claude to refactor your authentication logic. It responds with 80 lines of beautiful code. Now what? Copy the whole thing? Manually find where each piece goes? Watch your indentation break? Answer: Morph Apply 📝 blog.continue.dev/morph-faster...

I'm so happy that SF meetups are back. AI is changing how we code daily. Let's share what's actually working. GitHub SF office. No pitches, just day to day dev experiences. Great warm-up for AI Engineer World's Fair 🚀 lu.ma/87kr0w9r

Claude 4 is ready to go in Continue! ✅ And...It's good. Very good. Just add `anthropic/claude-4-sonnet` or `anthropic/claude-4-opus` to your config.yaml, or add them from the hub:

💻 Agent mode just went local! Today, Mistral AI released Devstral, an Apache-2.0, 24B-parameter model trained for tool calling in real-world software development environments To try it out, just add `ollama/devstral` in Continue. See below for a quickstart with Ollama 👇

I'm excited to join @continue.dev as CEO. After working with @ty.energy and @natesesti.bsky.social first as a user, then advisor, I'm thrilled to have the opportunity to help build what I believe in: open developer tools that amplify developers' work without trying to replace them.

@continue.dev is hosting the AI Native Dev - SF Meetup at GitHub HQ (thanks to Kevin Crosby!) with @jedi.be and friends ️‍🔥

⚡️ Agent mode got a bit faster this week Even in large, multiple-hundred-line files, Continue can now make small edits in seconds

@docker.com MCP Catalog 🤝 @continue.dev Agent mode