Changelog

Better with every update.

New features, thoughtful improvements and the details that make Merlin better.

  1. 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
  2. Merlin acts when something happens

    New

    • Work that starts on its own, not only on a timer
      • Work that used to wait for someone to notice, like a new pull request, a fresh Linear issue or a message in a support channel, can now start on its own. Schedules are now Automations: each one runs on a schedule or when an event arrives, so routine follow-up happens without anyone remembering to ask. Automations.
      • You decide exactly which events count. A trigger reads as a plain sentence, such as "Pull request is opened in Any repository", and you narrow it with your own repositories, projects, labels and people, so Merlin skips the noise.
    • Your other tools can hand work to Merlin too
      • A gate rollout in Statsig, an incident in incident.io, a failed payment in Stripe, a signal in PostHog or meeting notes in Granola can each start an automation. Merlin picks up where those tools stop, with no glue code in between. Webhooks.
      • When something doesn't run, you can see why. Each webhook keeps seven days of history showing what every automation did with each event and the reason it skipped one.
    • Set up an automation in one sentence
      • No form needed. Tell Merlin in Slack "whenever a pull request gets the bug label, triage it", and it creates the automation and tells you what it set up. It asks only about the parts it can't work out.
    • Automations that do the work quietly
      • Not every result needs a message. An automation can just file the Linear issue or leave the pull request comment and post nothing, which also means teams that don't use Slack can rely on automations.
      • Fewer pings: a run that finds nothing to report can stay silent, and you can get a direct message only when a run fails or needs you.
    • Delete your account yourself
      • Leaving Merlin is in your own hands. Delete your account from Settings › Account. Merlin first makes sure any workspace you share with others has a new owner.

    Improvements and fixes

    • Work keeps moving when a provider plan runs out: Merlin moves to your other agents and tells you which plan is used up
    • Commits Merlin makes for a GitHub request are credited to the person who asked, so history shows who asked for each change
    • New DMs go to the agent you chose as preferred, so your setup is respected from the first message
    • Linux machines set up with version managers connect without manual path fixes
    • Linear guests can work with Merlin just like members
    • Signing in is faster: paste or type the six-digit code and it submits on its own
    • Setup shows where you are and what's left at a glance
    • Long Slack updates no longer fail partway through
  3. Several accounts, Stop from Slack, and Linear sessions that show the work

    New

    • Several accounts at once
      • Sign in to more than one Merlin account in the same browser. The workspace switcher groups workspaces by account, Add an account signs in another, and Sign out ends only the current one. Workspaces.
      • The desktop app groups its workspaces by account too, and asks before a switch that would cancel tasks running on your computer. Installation.
    • Stop a task from Slack
      • Slack's own stop control next to a running task ends it. Anyone in your Merlin workspace can use it, and what Merlin already posted stays. Slack.
    • Usage tips under answers
      • Now and then a Slack answer carries one short tip for what you just did. Owners and admins can turn tips off on the Slack integration page.
    • Linear sessions show the work
      • A Linear agent session shows Merlin's thoughts, a live status while a step runs, its plan, and one action per step with the tool's result. Linear.
    • Easier agent setup
      • Sign in to Claude Code or Codex from the desktop app's Connection view, with no terminal needed.
      • When no agent is usable, setup says why and offers the Claude or ChatGPT desktop app or an install command. Check again looks for agents right after you install or sign in. Set up Merlin.
      • Connect Merlin in setup opens the desktop app to connect this machine.
      • A Getting started card in the web app sidebar walks you through the setup steps that apply to you.

    Improvements and fixes

    • A request waiting in the queue shows as Queued in the desktop app's Tasks list and turns into Running when it starts
    • Disconnecting or signing out while tasks run on your computer asks first, and the tasks end as cancelled
    • A preferred runtime is cleared when its owner unlinks it, makes it private or leaves the workspace
    • A Claude Code runtime on Provider default runs the model the web app and desktop app show
    • New work no longer goes to a computer that has stopped responding, and a run that never starts no longer hangs
    • An @mention waits while your agent recovers from a crash instead of failing
    • Merlin picks the newest Claude Code it can find on your computer
    • Linear sessions start in organizations that set agent guidance
    • GitHub: a request for a repository outside the installation gets a clear refusal
    • GitHub: the integration page names the @usemerlin-ai handle to mention
    • Only your own edit to a Slack message revises the request
    • Schedule run history loads again
    • The desktop app shows the runtime access set in the web app
    • A dropped update download no longer shows as a desktop crash
    • The Mac app icon displays correctly in Finder and the installer
    • Integration and Billing pages fit on phones
  4. Start without Slack, and schedules that suggest themselves

    New

    • Start without Slack
      • Create a workspace right away and choose where your team works: Slack, Linear, GitHub or several. Setup adds a connect step for each one. Set up Merlin.
      • If you can't install Merlin yourself, ask a Slack, Linear or GitHub admin to do it from setup.
    • Schedules
      • An empty Workspace or Personal tab suggests schedules to start from, each opening a filled-in form. Schedules.
      • Set a timezone for the workspace and one for yourself in Settings. Workspace schedules follow the workspace's, personal schedules follow yours, and changing either moves the next run.
      • Personal schedules always post to your own DM.
    • Answers cite their sources
      • Slack answers link the messages they draw on as numbered citations, and the footer has a Configure link to your device settings.
    • Files on Linear issues
      • A run can attach its files, like a screenshot from a Slack thread, to the Linear issue it names. Linear.

    Improvements and fixes

    • Settings › Devices has a Connect Merlin button that opens the desktop app, next to a download for your OS
    • Invite teammates with a role for each address
    • The Billing page shows your plan's price and usage bars, and the trial notice goes away once a payment method is on file
    • Runs in the same project no longer wait for each other
    • Linear: a mention in a comment thread reaches the run with its thread
    • GitHub: a mention in an issue's opening body reaches the run
    • The desktop app opens a Linear task on its agent session page
    • Schedules and Memory say when Slack still needs connecting
    • Timezone pickers are searchable
  5. Easier setup, and Merlin in your own projects

    New

    • Easier setup
      • Use a teammate's shared agent instead of your own computer, invite your team at the end of setup, or ask a Slack admin to install Merlin for you. Set up Merlin.
      • Sign-in emails have a one-click link, and signing in on a phone offers to continue on a computer.
    • Your own projects
      • A run can move into your Claude Code or Codex project mid-run, and the thread stays there.
    • Change settings by asking
      • Ask Merlin in Slack to change a channel's mode or your guidance. Owners and admins can also change workspace guidance and the Linear issue policy. Custom instructions.
    • Linear status follows the work
      • Delegated issues move to In Progress, and can move to In Review or Done when Merlin finishes. Linear.

    Improvements and fixes

    • Slack: a welcome DM for new members, and "can't run this now" notices only the requester sees
    • The desktop app checks Claude Code and Codex before you connect
    • Slack messages with lists are no longer ignored, and replies can @-mention people again
    • Web app feedback accepts .log files
  6. Introducing Merlin: Claude Code and Codex, in the tools your team already uses

    New

    • Merlin in Slack, Linear and GitHub
      • Mention Merlin in a Slack thread or DM, delegate a Linear issue, or mention it in a GitHub issue or pull request comment, and the answer comes back where you asked.
      • Everyone in the thread sees the same run and can steer it with a follow-up. Read about Slack, Linear and GitHub.
    • Your agents, on your own Mac
      • The Merlin desktop app connects the Claude Code and Codex you already run to your team's requests. Approve the machine in your browser and it works with the files, tools and subscriptions already on that Mac. No API keys, no separate model bill.
      • Follow each task's status from the app and choose the runtime you prefer from the web app. Download Merlin for macOS or read Devices and runtimes.
    • Shared skills
      • Publish a skill from your machine to the workspace catalog, or draft one in the browser. Anyone installs it on their Claude Code or Codex. Shared skills.
    • Schedules
      • Put recurring work such as a team digest or a routine review on a schedule, and each run delivers its result to Slack. Schedules.
    • Memory
      • Channel memory keeps the short, durable facts a team learns in Slack, so later tasks do not have to rediscover them. Memory.
    • Workspaces and access control
      • Invite your team, set roles and choose who can use Merlin in Slack and who can reach your devices, skills, memory and schedules. One account can belong to several workspaces. Members and roles, Workspaces.
    • Plans
      • Starter includes up to 3 active users and 1,000 requests and automation runs per month, Team includes 5,000 and Scale is unlimited. Every new workspace starts on a 14-day Team trial without a card. Pricing, Billing and plans.

    Improvements and fixes

    • Final Slack answers name the device, agent provider and reported model behind the work
    • Proactive responses can bring Merlin into a channel discussion without a mention
    • Custom instructions let a workspace and each member shape how Merlin works
    • The desktop app reports connection and runtime status, restores task history after a relaunch and checks for updates
    • Workspace-wide notices make plan limits and trial reminders visible beyond the billing page
    • Contact us in the web app reports a problem or shares feedback, or email support@usemerlin.ai