u/0x1010101

We profiled the agent loop and found it waiting on things it never needed to wait for. Multi got up to %40 speed up on our internal tests.

Diagnostics check once per turn, not every step - Multi feeds IDE diagnostics back to the agent so it fixes its own errors. That check used to run after every step, stalling the loop on the language server mid task. Now it runs once at successful turn.

Better feedback, not just faster - diagnostics now reflect the finished state of the code, not a half-edited file that was going to change two steps later anyway.

Diff cleanup off the critical path - interrupted tools leave diff views open; we close them as a failsafe. That cleanup was sequential and blocking. Now all closes fire concurrently and the loop moves on immediately.

Also in 0.0.119: personas are now a simple startup selector (the dedicated settings view was overbuilt, so we killed it).

Multi now supports a .multiignore file at the root of your workspace, a simple, .gitignorestyle way to declare paths the agent must never touch.

• Full tool coverage  Read, Edit, and Write are all blocked from accessing ignored paths
• Works everywhere  enforced in both the VS Code and IntelliJ extension
• Hard refusal, not a suggestion  the agent is told the path is forbidden and instructed not to reach it by any other means (including Bash)
• Familiar syntax  same patterns you already know from .gitignore

Drop a .multiignore in your project root with entries like .env, secrets/, or *.pem, and Multi will keep its hands off.

Multi now supports the complete GPT-5.6 family across the OpenAI API and OpenAI Codex providers.

• GPT-5.6 Sol - OpenAI's frontier model for complex reasoning, coding, and professional work
• GPT-5.6 Terra - A balanced choice for everyday agentic work with strong intelligence per dollar
• GPT-5.6 Luna - The fastest, most affordable option for high-volume workflows
• Up to 1.05M context (via the OpenAI API) and 128k max output across all three models, with long-context and prompt-cache pricing built in

Head to Settings → Provider and choose gpt-5.6-sol, gpt-5.6-terra, or gpt-5.6-luna with your OpenAI API key or ChatGPT subscription.

Added support for Claude Fable 5, Anthropic's Mythos series model.

• 1M context by default
• Adaptive thinking with selectable effort
• Available on Anthropic, Vertex, Bedrock, and Claude Code providers

Pick claude-fable-5 and keep shipping.

title says it afaict a lot of agents conflate session reload with task resume. reloading a session is not the same as resuming a failed, aborted task.

Multi already supports task reload: open the task from task history.

some agents rely on what I call stochastic resume: type continue and pray.
its alright if you are fine saying goodbye to $10m tokens you burned before hitting provider is overloaded

what I haven’t seen done yet: deterministic restore of the full agent state. basically full/recursive agent state restoration without wasting tokens.

what do you do when your tasks fail?

type continue? or start over? or ??

Hey!

Erdem here, co-founder of Multi.

Multi just crossed 149k installs, and I owe you all an honest post about what we're actually building and why.

If you're in this subreddit, you've probably already installed Multi or you're about to. This post is the long version of who we are, why we built this thing, and what we're trying to do here.

Who we are

We're engineers. We've shipped code at big tech and at Silicon Valley startups. We've seen how engineering actually gets done, from few person teams hacking through the night to multinational orgs with 50 step deployment pipelines. We're not commentators. We're not influencers. We build.

What we believe about AI coding

We're not here to start a holy war. If you're happy coding without AI, genuinely happy for you. We're also not here to preach AGI or pretend the singularity is next quarter. Here's what we actually believe: AI gives engineers leverage. The kind of leverage that lets you think bigger and build better. Used well, it's the biggest shift in how we work since the IDE itself. Used badly, it's a faster way to lose track of your own codebase.

Why we built Multi

The first wave of generative coding tools (call it the V0 era) was built for vibe coding. We tried them. We were amazed by the power and appalled by the quality. Things have improved since then. But the fundamental problem didn't go away: engineers still have to provide the design, the steering, the inspection. The model can't do that part. It shouldn't. And yet, every tool we tried took that part away from us:

• They forced us to switch IDEs we'd spent years tuning.
• They broke the workflows we'd built.
• They gave zero visibility into their thinking.
• They were black boxes wrapped in nice UI.

We felt like passengers. We wanted to be pilots. So we built Multi.

What Multi actually is

Multi is an IDE-native coding agent: VS Code and JetBrains, both first-class built around one premise: max control, max visibility.

• See the plan before the agent executes it.
• Every change as a diff you can review.
• Pause, steer, fork, restore, time-travel.
• Autonomous when you want it. Manual when you need it. It's a dial, not a switch.
• 10s of providers, 100+ models. BYOK. No vendor lock-in.

Your taste. Your workflow. Your judgment. Your standards. Plus AI leverage.

What Multi is not

• Not for people who want AI to do everything while they watch.
• Not a magic black box.
• Not trying to replace your judgment.
• Not trying to be your IDE - we plug into the one you already love.

If you want to vibecode a weekend project and not look at the output, there are great tools for that. Use them. Multi isn't one of them. Multi is for engineers who read diffs before they merge.

What this subreddit is for

A few things:

1. Honest feedback. If something feels broken, missing, or wrong, post it. We read everything. The fastest way to shape Multi is to tell us where it failed you.
2. Setups and workflows. Profiles, model routing, subagent configs, weird worktree tricks. Show us how you're using it. We'll learn from you.
3. Changelog and what's next. We'll post what we ship, what we're working on, and what we're still figuring out.
4. Real talk about AI coding. Not hype. Not doom. Just engineers comparing notes on what actually works.

What this sub is NOT for: shilling, hype, doom posting or pretending AI coding is solved. It isn't. We're all figuring this out together.

Where we're going

The next big push is teams. Most coding agents today are built around a single developer in a single IDE. That's the floor, not the ceiling. We think the same principles: visibility, control, your standards should scale to how teams actually ship together. More on that soon.

The ask

If you've used Multi and it didn't make you feel like the pilot tell us what's missing. Comment here, open an issue, DM me. We'll fix it.

If you've used it and it clicked, spread the love. Tell us, tell others what worked. That's how we know what to double down on.

Welcome! Glad you're here.

Erdem,
Co-founder, Multi

Core contributor of Multi here 👋

Quick update for folks using DeepSeek for coding: Multi now supports DeepSeek V4.

Multi is an IDE-native coding agent that runs inside VS Code and JetBrains, so you can use DeepSeek directly in your editor with plans, diffs, tool calls, and agent workflows.

DeepSeek V4 Flash / Pro is wired up through the DeepSeek provider with toggleable thinking mode. Bring your own API key, pick speed or max capability, and go.

A lot of Multi users already run DeepSeek, so figured this community would care.

Happy shipping.

Core contributor of Multi here 👋

Quick heads-up for folks using GLM for coding: Multi now supports GLM-5.1 and GLM-5-Turbo through the Z.ai provider.

Multi is an IDE-native coding agent that runs inside VS Code and JetBrains, so you can use DeepSeek directly in your editor with plans, diffs, tool calls, and agent workflows.

GLM-5.1 brings native thinking mode and up to ~200k context, which makes it especially interesting for agent workflows, repo understanding, and heavier coding tasks.

Drop in your Z.ai API key and you’re good to go.

We already have Multi users running GLM, so figured this community would like the update.

Happy shipping.

-- edit: better clarity, description

Multi now supports DeepSeek V4 and GLM-5.1; next-gen models with native thinking mode for top-tier reasoning, coding, and agent workflows.

DeepSeek V4 (Flash & Pro) - 1M context, toggleable thinking mode, pick speed or maximum capability.

GLM-5.1 & GLM-5-Turbo - up to ~200k context with native thinking on by default

Wired up on the DeepSeek and Z.ai providers - just drop in your API key and go.

We recently shipped parallel subagents in Multi. The goal is the same as always: more AI leverage, while keeping visibility and control.

But parallel agents make one thing obvious: "best coding model" is the wrong framing.

When one agent runs the whole show, one default model kind of works.

With subagents, the task splits into different kinds of work: planning a refactor, searching a repo, editing one file, writing tests, debugging a failure, spinning up cheap parallel research workers

Those do not all need the same model.

Some need reasoning.
Some need speed.
Some need context.
Some need cheap tokens.

Curious how people want this to work in Multi.

Would you route models by task/role, or just pick one default and live with it?

Multi just passed 110k installs.

1 week after announcing 80k.

Thanks to everyone who tried it, reported bugs, and shared feedback.

Still shipping. More soon.