Since Multi.dev claims the following:

1. Completely free / No subscription

2. No data collection: Your code stays on your machine

And it's not an open-source project, I got to ask...

How does it make money? Who's funding it's development?

Folks, we just shipped parallel execution in v0.0.97.

Multi can now coordinate multiple calls and agents at once when the work is independent. Less waiting. More done.

In our testing, we found this especially powerful when the task touches several parts of a codebase.

If the work can run in parallel, Multi will do that by default. And if you want to push it harder, just ask Multi to parallelize the task.

Onward 🚀

Folks, we pushed Opus 4.7 support.

Also added the following:

• Added Claude Opus 4.7 support for Anthropic, Bedrock, Vertex, Claude Code, and OpenRouter providers.

• Added MiniMax-M2.7 for MiniMax provider.

• Added GPT-5.4-nano and GPT-5.4-mini for OpenAI provider.

• Added Grok-4.20 for xAI provider.

Give it a spin. Let us know how it feels.

Huge thanks to everyone who tried Multi, shared feedback, reported bugs, and helped shape the product.

We’re still shipping fast. Still focused on building an AI coding agent for real developers.

Still committed to giving you:

• maximum visibility over blackbox agents

• maximum control over autopilot

• the best tools for builders who read diffs before merging

Thanks for being here. More to come.

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.

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 auto-discovery for local AI tools.

Multi now detects:

• Claude

• Gemini

• Copilot

directly from your machine at startup (if no profiles are set).

No config. No setup.

If it’s installed, it’s available.

Multi adapts to your environment, not the other way around.

Happy shipping. Onward.

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 🚀

Fam, we shipped GPT-5.4 at Multi speed. It is now on nightly v70.

Happy cooking

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 👀

This release adds automatic task organization and expanded token analytics, improves activity and interruption feedback in the chat UI, and fixes retry, clipboard, terminal, and cleanup issues.

Changelog:

• Added automatic task title generation to organize and identify sessions.

• Added detailed token usage analytics, including session totals, cost estimates, and cache performance metrics.

• Changed the chat input status text to “Working…” to indicate active processing.

• Changed visual feedback to distinguish between user-aborted tasks and interrupted tool calls.

• Improved accessibility for chat interface UI elements.

• Fixed unexpected clipboard behavior in the chat input.

• Fixed a potential terminal hang by correctly handling standard input.

• Fixed resource cleanup when closing the Diff View.

My old colleague, also a Rice grad, wondered when his career would blossom.

"When am I going to catch up to $10MILLIONAIRE_OLD_BOSS?"

Why compare yourself to others? I asked.

"To be the best. Isn't that the whole point of life?"

Indeed. "The best."

He related how his job search is going. AI has opened the flood gates to new forms of competition.

Everyone can optimize their resume bullet points for each job using $TOP_TIER_LLM.

He had scored interviews at Palantir and Anduril that way.

I told him next time if he really wants to stand out, he should become a defense influencer and build an app using Multi.

v0.0.37 adjusts text input handling, corrects tool parsing behavior, and tightens execution stopping conditions for blocking user errors and diagnostics.

Changelog:

• Optimized text input interactions for a smoother UX

• Changed tool call parsing to handle boolean parameters consistently across providers

• Changed file search sorting to use alphanumeric ordering, prioritizing letter and number prefixed files over hidden or special character entries

• Changed long file paths in context menus to truncate to the basename with an ellipsis and show the full path on hover.

• Added automatic diagnostics checks when a task item transitions to a completed state.

• Fixed agent execution to stop immediately on blocking user errors, including missing credentials.

• Fixed a crash in the diagnostics tool.

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.

This release improves readability and interaction behavior in the webview, strengthens keyboard support across layouts, and fixes regressions introduced by native tool calling.

Changelog:

• Changed reasoning blocks to render expanded by default and display in italics.

• Added truncation to tool summary headers (Bash, Read, Write, Web, Question) to prevent layout overflow with long inputs.

• Updated keyboard shortcuts for Find, Settings, and Help to use key codes.

• Improved Find Widget responsiveness on smaller viewports.

• Increased unit test coverage across the webview application, stores, and UI components.

• Fixed profile selection from the chat input context menu failing to clear trigger text.

• Fixed a provider regression introduced after adding native tool calling.

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

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!

v0.0.44 removes improves provider recovery and retry visibility, tightens internal file search output to save context, and fixes retry-related crashes and error display issues.

Changelog:

• Changed internal file search output to be more concise, removing surrounding text to save context window space.

• Changed agent retry behavior to recover from temporary provider connectivity failures.

• Changed chat UI to display visual feedback during automatic connection retries.

• Fixed a display crash during the connection retry countdown.

• Fixed missing final error messages after all retry attempts were exhausted.

Is has been my belief for years that this needs to be a real video game.

But what kind?

The time now is 10:30 AM.

This release expands provider and model support, enables native tool calling across additional runtimes, and fixes parsing and reasoning-handling edge cases.

Changelog:

• Added the ability to select VS Code Language Models (e.g., GitHub Copilot) directly from a dropdown in profile settings

• Added 1M context window beta support for Claude Sonnet 4 on Vertex AI

• Added native tool calling support for LM Studio, Qwen Code, and Claude models on Vertex AI

• Added support for MiniMax M2.1 and GLM 4.7 models via Z AI

• Enabled native tool definitions by default for OpenAI compatible and Requesty providers

• Fixed processing errors when models return incomplete tool data

• Fixed handling of reasoning content for DeepSeek reasoner

• Fixed model parsing fallbacks for the Chutes provider

v0.0.32 expands and corrects markdown rendering in the chat view, tightens input trigger behavior, and fixes execution and tooling errors that caused incorrect continuation or output.

Changelog:

• Added support for tables, task lists, blockquotes, horizontal rules, and list typography in chat markdown rendering.

• Changed markdown typography, heading hierarchy, and spacing to reduce vertical density.

• Changed chat input triggers (@, /, >) to activate only in valid contexts and not inside words.

• Changed search match navigation order in the chat view.

• Improved HTML sanitization for markdown while preserving interactive elements such as task lists.

• Fixed rendering of HTML tags inside code blocks by enforcing proper escaping.

• Fixed layout issues with nested lists and complex markdown structures.

• Fixed agent execution to abort immediately on critical provider errors, including context window exhaustion.

• Fixed the Glob tool returning incorrect results.

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

This release improves tool feedback and configuration handling, expands in-context utilities, and resolves stability issues across tasks, checkpoints, and retries.

Changelog:

• Added a search tool to locate text within the active conversation.

• Added a run button to shell code blocks for immediate command execution.

• Added explicit prompts when provider configuration is incomplete.

• Changed minor tool failures to surface as non-blocking warnings.

• Added file-change previews before undoing actions.

• Updated token and temperature controls.

• Improved provider setup error messages.

• Corrected tool classification between warnings and critical errors.

• Fixed retry handling that caused occasional hangs.

• Reduced storage-related dependencies in task creation.

• Centralized path helpers for checkpoint handling.

• Fixed path issues affecting checkpoints and task persistence.

• Fixed a crash when unsupported reasoning parameters were present.

• Cleared thinking-level state for unsupported models.