Pick the model per task, see your usage, and memory that learns
New
- Pick the model for one task, in your own words
- Ask for it in the request: "use max effort", "think harder on this one", "switch to my Claude agent" or "use Alice's". Merlin moves the task to that runtime, model or reasoning effort before it starts, for this task or the rest of the thread, and the runtime's own settings stay as its owner set them. Devices and runtimes.
- When Merlin can't do what you asked, such as a model your runtimes don't offer, the line under the answer that names the device and model says so.
- See what your agents spend
- Settings › Usage shows cost, tokens, requests and run time for the whole workspace, and every member can read it. Pick a range, like the last 30 days or the current billing period, and break a metric down by person, model, runtime or surface. Track usage.
- Cost is an estimate at public API prices for what your agents used, not what Merlin bills you.
- Memory that learns from the channel
- With memory on, Merlin picks up durable facts from a channel's conversations in the background, so a decision made in a thread is there for the next task.
- Each fact keeps the Slack message it came from, and an answer that relies on it cites that message. Memory.
- More control over automations
- Choose an automation's model, reasoning effort and mode, so a quick daily digest and a careful weekly review can each run the way they need. Automations.
- Move an automation between workspace and personal with the pencil beside Scope, or by asking Merlin in Slack, and its destination moves with it. A request in Slack can also say "make it personal" or "post it to #eng".
- Use cases for every team
- Use cases collects ready-made packs for engineering, product, design, sales, support, legal, IT and more, each showing the tools it needs and how Merlin runs it.
Improvements and fixes
- Linux machines get their own path in setup's Connect your agent step
- The web app's Agent section is now called Agents
- Agents can read images attached to private Linear issues
- The desktop app's Tasks list updates a task that finished on another machine
- When your machine is offline, the notice tells you the next step for the app you run: open the desktop app, or the terminal command for the Linux daemon
- A Slack Text filter on an automation also matches attachments and message blocks
- A GitHub review comment that isn't attached to a line of code reaches Merlin
- A mention in a Linear issue's description no longer starts a run by itself. Mention Merlin in a comment or delegate the issue
- Reinstalling Merlin in Slack or approving new permissions no longer sends the installer another welcome
- Usage tips under Slack answers now cover newer features: choosing a model, Usage, webhooks and automations that stay quiet