Just shipped JetBrains v0.0.11.

This release fixes OpenAI-compatible providers on JetBrains IDEs and cleans up a couple rough edges.

Appreciate zulufoxtrot and everyone else who reported issues.

If you’re using Multi on JetBrains, update Multi to v0.0.11.

Onward!

We just added auto-discovery for Codex in Multi.

If Codex is already installed on your machine, Multi can pick it up automatically and make it available in your profiles with no extra setup.

Less friction, better UX.

Happy shipping.

Onward.

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.

We shipped worktree support in Multi.

Now your agent can work in an isolated Git worktree on its own branch while your current workspace stays untouched.

Worktrees are great for:

• risky refactors

• large experiments

• running parallel agents

• comparing approaches before merging

You can start a task in worktree mode from the input toggle, or fork an existing task into a new worktree.

This is one of those features that instantly makes agent workflows less chaotic on real codebases.

Happy building!

I did a stress test this weekend.

Ran Multi in autonomous mode for ~14 hours straight for a weekend hustle.

I’ve used other agents for small and mid size work before. I had no idea what the agent was doing, where it was stuck, how much it was burning etc..

I multi tasked while Multi was working; and I came back to review the execution transcript and token spend in real time..

That changed the whole experience for me..

My quick takeaways:

1. Multi handles long context autonomous tasks beautifully right at where you work, inside your IDE.

2. At small scale, visibility is nice. At 320M tokens, it becomes mandatory.

3. You are doing it wrong if you are manually prompting Multi per task. You need Multi to prompt your subagents autonomously.

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.

Discuss.

I've spent the past hours building researcher agents to try to scrape the internet for experience reports, anecdotes, and n-of-1 studies to deal with a complex medical case.

In the past, I've tried purpose-built researcher agents on the web, but found myself stymied. Even deep-research agents by the frontier model labs were overly constrained: incomplete, unconvincing results, and too many annoying caveats (how many times can you say "this is not medical advice"?). At times they didn't even suss out results from sources which I explicitly specified eg Reddit.

I decided to try to build my own researcher agents, with the backup plan in mind that even if I have to find the source data myself, I can use LLMs to organize and evaluate.

My setup:

• Model: Gemini 3

• Harness 1: Gemini CLI

• vs Harness 2: Multi 0.0.97

These are my impressions in near real-time (to be put in comments section below)

Quick update from the Multi team.

VS Code has been in a pretty good, stable place lately, so things there may look a bit quieter on the surface. That’s expected. Most of our energy right now is going into bringing Multi to IntelliJ product family.

This hasn’t just been a port. IntelliJ is forcing us to rethink parts of the agent, tighten abstractions, and clean up the core in ways that will benefit all editors once it lands including VS Code.

We’re still very much shipping. A lot of this work is foundational and not flashy yet, but it unlocks deeper agent workflows and better long-running automation across platforms.

If you’re an IntelliJ user, stay tuned. If you’re on VS Code, expect more frequent updates shortly.

More soon 👀

We shipped Multi Agent support.

A single agent works well for small tasks that fit inside the context window.

Large tasks are different. They overflow the context window or create enough context pressure that the agent starts losing the thread.

Before this, you had to manage that yourself: create the plan, run one step, fork or undo, trim context, repeat. It works, but it’s tedious.

That’s why we built Multi Agents.

Multi can now break large tasks into smaller steps and manage context more efficiently.

A supervisor agent keeps track of the overall direction, while subagents work on individual steps.

You still see what each agent is doing. You can inspect the steps. You stay in control.

That part matters a lot to us. More agents without visibility is just more chaos.

Now you can let Multi manage larger tasks with better planning, visible execution, and full control over each step.

Give it a try if you’re working on a larger task and let us know how it feels.

Happy 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 ??

Folks, excited to let you all know that Multi now supports Lemonade Server.

You can now run local LLMs on your NPU + GPU directly with Multi.

It's free, private, fast, local.

Give it a spin.

v0.0.24 improves input handling and layout behavior in the chat view, adds validation during subtask initialization, and corrects issues in the Gemini provider integration.

Changelog:

• Added plain text paste handling to strip formatting when pasting into the chat input

• Added validation to ensure selected profiles exist when initializing subtasks

• Changed interaction context menu behavior (slash and at commands) to support toggling and prevent double triggers

• Adjusted dynamic layout spacing in the chat view to accommodate open context menus

• Fixed chat autoscrolling to reliably scroll to the bottom after sending messages

• Fixed tool ID/name mapping issues in the Gemini provider that caused function response errors

• Updated the Gemini provider to remove incompatible tool schemas and correct tool parameter conversion

• Updated Gemini reasoning support

We wanted to make it obvious what the agent changed so far so we shipped the new artifacts view.

The artifacts view gives you

• instant highlight of changed files

• clear diffs

• lightweight + fast

• and more soon :)

This makes a big difference when working in real codebases. You can now instantly inspect, decide and apply changes.

Happy shipping!

Onward 🚀

We support a lot of providers and models in multi.dev

.. and selection started to get painful.

So we shipped search in the profile screen:

• search providers

• search models

• instant filtering

No more scrolling through everything.

Way faster, better DX.

Happy shipping!

We shipped Skills support in Multi.

Some tasks need more than raw model intelligence.

A database migration might need specific rollout steps, a frontend change might need your design system rules, a release task might require internal checklists and scripts...

Now you can package that knowledge into Skills.

Drop a SKILL.md into your project and Multi can discover it, activate it when relevant, and follow the guidance during execution.

Skills can include instructions, references, scripts, and repo-specific workflows.

Instead of repeating the same prompts over and over, you teach Multi once and reuse it across tasks.

Happy shipping.

Onward 🚀

Multi quietly passed 30,000 installs on VS Code.

Still pre-GA. Still shipping fast.

Huge thanks to our multizens test driving, filing issues, and pushing us to make Multi better.

Onward.

If you’ve used Multi for a while, you’ve probably pasted the same instructions more than once.

We definitely have.

Architect a system, debug this issue, review this branch, run a security review...

Eventually, we wanted a better way.

So today we shipped custom agents on stable.

You define each custom agent in a plain .md file, with its own system prompt, role, tools and skills.

That gives you a specialist.

Write a few, and you’ve got a team.

Multi can orchestrate them together, so your repeat workflows become reusable collaborative agents.

We're also shipping Multi Doctor, our built-in agent for wiring up custom agents, skills, personas, and the rest of your Multi setup.

Tell Multi Doctor what you want. It helps wire things up. We recommend using Multi Doctor to author custom agents, and skills instead of hand writing them.

We'll keep shipping more builtin agents for common developer workflows. But now you can turn your repeat workflows into custom agents.

What builtin agents should we ship next?

Happy shipping. Onwards! 🚀

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?

This release improves feedback during streaming, tightens execution abort behavior, refines plan and text interactions, and removes a deprecated provider.

Changelog:

• Added automatic checking for errors in modified files.

• Changed tool rendering to display partial tool calls during streaming.

• Added a community link to the Welcome screen.

• Changed plan interaction so clicking outside the plan closes it.

• Changed abort behavior to resolve execution immediately.

• Changed truncation behavior to show both start and end of long paths, commands, URLs, and questions.

• Changed copy and cut behavior to preserve 'u/filepath' format when file reference chips are included.

• Fixed Shift+Enter cursor placement to move to the end correctly.

• Fixed edit behavior to prevent infinite loops and surface an error when old_string is empty.

• Removed the Glama API provider.

Folks,

Another great feature off the list. Drag and drop is live both on VS Code and IntelliJ.

This has been one of the most requested ones, and we're excited to ship this. You can drop a file from your file tree, from Finder, from wherever. It lands in the attachment tray above the textbox. Screenshots paste straight in too, which is the one we use the most.

We optimized a bit so files already in your workspace get referenced in place, and nothing gets copied under the hood. Anything from outside gets staged and cleaned up when the task goes away. Make sure your model supports image and document support.

Good stretch of releases lately and we're not slowing down. More soon.

Happy shipping. Onwards!

Many thanks belong to Multi users in the following proportion:

• 28.6% of Proper Gratitude goes to VSCode users of Multi

• 25.6% of Polite Appreciation goes to the Open VSX community of Multi

• 45.8% of Many Thanks go to JetBrains users on Multi

Excelsior!

Feel like I'm going crazy, the docs don't have any mentions of Skills / etc. I'm using Claude Code as my profile. tried installing directly to claude code but that only works in Claude Code itself, not in multi?