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 🧵👇

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

Leverage rules as a context provider now in Continue 📜

⚡️ Agent mode got a bit faster this week

Even in large, multiple-hundred-line files, Continue can now make small edits in seconds

💭 If you're looking for an easy way to use DeepSeek's R1 in your IDE:

1. Download Continue
2. Run `ollama run deepseek-r1`

You'll have a completely local reasoning model in your IDE

📝 Continue can now edit multiple files automatically

- Update logic that spans multiple files
- Generate tests for new features
- Reference files as context without editing them

Using docs as context is now easy! And if you are using Python or TypeScript, you'll automatically get suggestions based on your dependencies. We'd love contributions for more languages ☀️

🎯 Ensure coding standards are followed with rules:

📁 Place a .continuerules file in your project’s root directory
✍️ Define project-specific system messages with ease
💡 Ideal for reinforcing coding standards and best practices (e.g. React guidelines)