Skip to content

Getting started

Concepts

Learn the vocabulary behind workspaces, runtimes, conversations and shared context.

Merlin connects the places where a team discusses work to agents running on machines its members control. These concepts describe the boundaries you will see across the product.

Workspace

A workspace is the team boundary for members, integrations, devices, skills, automations, memory, settings and billing. A workspace can be connected to one Slack team, either at creation or later. One Merlin account can belong to several workspaces.

Member

A member is a registered Merlin user who joined the workspace. Members can have the effective role member, admin or owner. People seen through Slack, Linear or GitHub before joining are not automatically registered workspace members.

Device

A device is a machine connected through the desktop app or CLI daemon. A machine can be approved for several workspaces, but the client serves one active workspace at a time.

Runtime

A runtime is Claude Code or Codex on that device. Its status, access, model settings and capacity decide whether it can accept a request. A connected device can still have an unavailable runtime.

Integration

An integration connects a workspace to Slack, Linear or GitHub. Any member can make the first installation or reconnect one that needs reauthorization. Once it works, owners and admins manage it. Individual identity connections tell Merlin which member a person on that service represents.

Surface

A surface is where a request begins and where progress returns. Today those task surfaces are Slack threads, Linear agent sessions and GitHub issue or pull request comments. Automations post new Slack messages when they run.

Conversation

A conversation holds one task and its follow-ups together. In Slack it normally maps to a thread, in Linear to an agent session, and in GitHub to the issue or pull request thread that mentioned Merlin.

Reply in the same conversation to steer active work or continue after the result. Start a new conversation for unrelated work so its context stays separate.

Skill

A skill is a package of reusable instructions and supporting files. Skills can originate on a member's machine or be managed in the workspace catalog. Publishing makes a package available in the catalog, and installing it makes the package available to a chosen local agent.

MCP server

An MCP server gives a local agent tools for another service or data source. Merlin reports safe inventory metadata, while configuration and credentials remain on the device. MCPs are execution capabilities, not workspace-managed catalog items.

Automation

An automation is work Merlin runs without a prompt each time, with a creator, a trigger, a run instruction and a destination. Its trigger is either a schedule, which runs at set times (fixed times follow the workspace timezone for a channel automation and the creator's personal timezone for a direct-message one), or an event, which runs when a connected product such as GitHub, Linear, Slack or a webhook product reports something that matches it. Each run executes on behalf of its creator and posts a new root message, unless its destination is None and it only takes actions. See Automations.

Memory

Memory is durable team context that Merlin saves as short Markdown notes. It is scoped to the Slack channel where it was learned: public-channel notes can inform the workspace, while private-channel notes remain in that channel. Memory starts off in a new workspace. An owner or admin turns it on from the Memory page.

Read How Merlin works to see how these pieces interact during a request.