Skip to main content
A canned response is a catalog resource that stores a reusable pair: a message body and a persona override. Pick one in a running agent’s follow-up box to fill in the follow-up text and set the persona for that message in a single click — useful for the replies you send over and over, like “rebase and re-run the tests” or “looks good, open the PR.” A canned response is either tenant-level or workspace-scoped, decided by its name. A bare name (rebase-retest) is available to agents in every workspace; a name with a workspace prefix (backend/rebase-retest) appears only for agents in that workspace. In the dashboard they are managed under Organization Settings → Canned Responses.

Fields

NameTypeRequiredDescription
namestringyesEither a bare DNS label (rebase-retest, tenant-level) or {workspace}/{slug} (backend/rebase-retest, workspace-scoped). Each segment matches [a-z][a-z0-9-]{0,62}.
textstringyesThe message body, inserted verbatim into the follow-up field when the response is picked. Maximum 16 KiB (16384 bytes).
personastringyesPersona override applied to the follow-up. A bare name (programmer, resolved against the canned response’s own workspace scope — tenant-level when the name is bare) or a pinned {workspace}/{slug} (backend/programmer). Must resolve to an existing agent-persona when the canned response is created.
titlestringnoHuman-readable label shown in the picker (e.g. Rebase and re-run tests). Display only — never inserted into the message. Maximum 1024 bytes.
Both text and persona are required. A canned response always carries a persona override, so picking one both fills the message and switches the persona for that follow-up.

Examples

Create a tenant-level canned response

name: rebase-retest
title: "Rebase and re-run tests"
text: |
  Please rebase onto the latest main, resolve any conflicts, and
  re-run the full test suite before pushing.
persona: programmer
cat <<'EOF' | murmur set canned-response rebase-retest
name: rebase-retest
title: "Rebase and re-run tests"
text: |
  Please rebase onto the latest main, resolve any conflicts, and
  re-run the full test suite before pushing.
persona: programmer
EOF

Create a workspace-scoped canned response

A name with a workspace prefix appears only for agents in that workspace. The prefix workspace must exist.
cat <<'EOF' | murmur set canned-response backend/lgtm
name: backend/lgtm
title: "Approve and merge"
text: "Looks good. Approve the PR and merge once checks are green."
persona: backend/reviewer
EOF

Listing canned responses

murmur get canned-response
NAME                  TITLE                    PERSONA
rebase-retest         Rebase and re-run tests  programmer
backend/lgtm          Approve and merge        backend/reviewer

Reading a single canned response

murmur get canned-response rebase-retest

Errors

CodeMeaningWhat to do
INVALID_ARGUMENTname is requiredProvide a name.
INVALID_ARGUMENTcanned response name must be a DNS label or {workspace}/{name}Use a bare DNS label or a {workspace}/{slug} name; each segment is [a-z][a-z0-9-]{0,62}.
INVALID_ARGUMENTtext is requiredProvide the message body in text.
INVALID_ARGUMENTtext exceeds 16384 byte limitShorten text to 16 KiB or fewer.
INVALID_ARGUMENTtitle exceeds 1024 byte limitShorten title to 1024 bytes or fewer.
INVALID_ARGUMENTpersona must be a DNS label or {workspace}/{name}Use a bare persona name or a pinned {workspace}/{slug}.
INVALID_ARGUMENTpersona "<name>" does not resolve to a usable agent personaReference an existing agent-persona. Create it first if needed.
INVALID_ARGUMENTworkspace "<name>" does not existThe workspace prefix names a workspace that does not exist. Create it or fix the name.
  • agent-persona — the persona a canned response sets on the follow-up
  • Agent personas — concept overview
  • Dashboard — where you pick a canned response in the follow-up composer
  • Workspaces — the scope a prefixed canned response belongs to
  • murmur set — CLI command for creating and updating catalog resources
  • murmur get — CLI command for reading catalog resources