Continue
@continue.dev
Ship faster with Continuous AI
continue.dev
continue.dev
Reposted by Continue
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...
briandouglas.me/posts/2025/1...
CodeBunny: Privacy-First AI Code Reviews with Continue
AI code reviews that run in your GitHub Actions environment, keeping your code in your repository. Built on Continue for flexible, privacy-focused code analysis.
briandouglas.me
October 21, 2025 at 12:40 AM
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...
briandouglas.me/posts/2025/1...
Reposted by Continue
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
- 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
Vibe coding is irresponsibly building software through dice rolls, not caring what code is produced
What about when engineers at the top of their game use AI tools responsibly to accelerate their work?
I propose "vibe engineering"!
simonwillison.net/2025/Oct/7/v...
What about when engineers at the top of their game use AI tools responsibly to accelerate their work?
I propose "vibe engineering"!
simonwillison.net/2025/Oct/7/v...
Vibe engineering
I feel like vibe coding is pretty well established now as covering the fast, loose and irresponsible way of building software with AI—entirely prompt-driven, and with no attention paid to …
simonwillison.net
October 8, 2025 at 9:10 PM
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
- 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
Reposted by Continue
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
Runnable with @ollamabot.bsky.social and available today in VS Code
September 4, 2025 at 6:20 PM
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
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...
blog.continue.dev/beyond-the-e...
Beyond the Editor: How I'm Using Continue CLI to Automate Everything
AI can feel magical when you’re filling in a function, but when you step back and try to build a real application—with security layers, architecture, testing, or CI/CD—their usefulness drops off. The ...
blog.continue.dev
August 27, 2025 at 11:04 PM
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...
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...
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...
August 20, 2025 at 4:08 PM
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...
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.
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.
August 20, 2025 at 4:00 PM
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.
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.
August 19, 2025 at 7:01 PM
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...
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...
August 19, 2025 at 4:05 PM
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...
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 🧵👇
August 18, 2025 at 9:14 PM
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.
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.
August 18, 2025 at 7:06 PM
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.
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 sharing our definition, the Continuous AI Maturity Model, and the metric that matters most. Read now: continue.ghost.io/ghost/#/edit...
August 13, 2025 at 8:19 PM
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 sharing our definition, the Continuous AI Maturity Model, and the metric that matters most. Read now: continue.ghost.io/ghost/#/edit...
Reposted by Continue
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...
August 12, 2025 at 1:30 PM
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.
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.
The Psychology of Coding: Why Developers Avoid Planning (and How AI Planning Tools Like Continue Fix It)
Why do developers resist planning? Discover how AI planning tools like Continue’s Plan Mode and a 15-minute workflow turn planning into your coding superpower.
dub.sh
August 6, 2025 at 8:23 PM
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.
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...
whatthedev.buzzsprout.com/673192/episo...
319: Rules and guardrails for AI coding assistants (with Continue's Brian Douglas) - What the Dev?
In this episode, Dave interviews Brian Douglas, head of developer experience at Continue, about the importance of rules for AI tools.They discuss: How to implement rules for AI assistantsUsing ru...
whatthedev.buzzsprout.com
July 29, 2025 at 8:47 PM
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...
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/
reddit.com/r/AIMemory/comments/1m6f3xd/cognee_mcp_is_my_new_ai_memory_for_making_rules/
From the AIMemory community on Reddit: Cognee MCP is my new AI Memory for making rules
Explore this post and more from the AIMemory community
reddit.com
July 22, 2025 at 3:38 PM
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/
reddit.com/r/AIMemory/comments/1m6f3xd/cognee_mcp_is_my_new_ai_memory_for_making_rules/
Reposted by Continue
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 📊
@chiphuyen.bsky.social tracked AI interruptions (24.5%), found the patterns, fixed her codebase structure.
Intervention rates are the new build times 📊
July 21, 2025 at 5:52 PM
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 📊
@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
July 17, 2025 at 5:14 PM
Introducing Plan Mode! Read more about it in the July Continue Newsletter
Reposted by Continue
July 15, 2025 at 2:05 PM
Reposted by Continue
Every dimension of designing, delivering, and operating software is changing dramatically.
Software Maximalism is the way
Software Maximalism is the way
For over a decade, we've backed and partnered with talented technical founders behind category-defining companies like @tailscale.com, @launchdarkly.bsky.social and PagerDuty as well as emerging leaders like Groundcover, @localstack.cloud, @unikraft.cloud and @continue.dev.
July 8, 2025 at 3:54 PM
Every dimension of designing, delivering, and operating software is changing dramatically.
Software Maximalism is the way
Software Maximalism is the way
Reposted by Continue
There is so much room for context engineering improvements at large organizations
July 3, 2025 at 7:26 PM
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...
Code Offline with Context Engineering
I ride BART every day, and I've turned those underground stretches into productive coding time using Continue's agent mode with Ollama. No internet required.
The reality of offline development
We'v...
blog.continue.dev
July 1, 2025 at 6:29 PM
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...
blog.continue.dev/building-a-s...
Building a Semantic Code History Search with LanceDB
Ever wished you could ask "who wrote all the authentication logic?" instead of manually running git blame on every auth-related file? What if your AI coding assistant could understand not just who cha...
blog.continue.dev
June 26, 2025 at 8:43 PM
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...
blog.continue.dev/building-a-s...
Reposted by Continue
I wrote AI code offline on a BART train
youtu.be/TbJ0gaC0T-E
youtu.be/TbJ0gaC0T-E
I wrote AI code on offline on a BART train
YouTube video by bdougie
youtu.be
June 24, 2025 at 4:47 PM
I wrote AI code offline on a BART train
youtu.be/TbJ0gaC0T-E
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...
Check out his full interview here: techstrong.tv/videos/inter...
Why Open Source AI Coding Tools Are the Future – Insights from Continue CEO Chad Metcalf - Techstrong TV
Continue CEO Chad Metcalf explains why an open source-based approach to AI coding tools will soon gain traction with application development teams.
techstrong.tv
June 17, 2025 at 8:41 PM
@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...
Check out his full interview here: techstrong.tv/videos/inter...