Macros

A macro is a saved prompt or action you trigger quickly, slash-style, instead of typing the same request out again. If you catch yourself asking the operator the same thing every Monday — same wording, same shape of output — that ask is a macro waiting to be saved.

What a macro is (and is not)

A macro is the smallest unit of reuse in Kaer: one saved ask, fired on demand. It does not run on a schedule (that is an automation) and it has no multi-step canvas (that is a workflow). Its whole job is to make a common request instant and consistent.

Creating and editing

1. Take a prompt that has already worked well in a real turn — that is your raw material.
2. Save it as a macro with a short, sayable name that describes the output ("release-notes" beats "rn1").
3. Trigger it slash-style from the chat input whenever you need it.
4. When the wording needs improving, edit the macro — every later trigger uses the new version.

Macros being editable is most of their value: the phrasing improves over time, and everyone triggering the macro gets the current best version rather than their own slowly drifting copy.

Naming

Name macros after what they produce, not how they work. "weekly-status" and "release-notes" invite use; an internal abbreviation makes people hesitate. In a shared workspace the name is the whole interface — it is what everyone sees when they reach for the slash.

Per-workspace

Macros belong to the workspace they were created in. Your workspace for one client can have a "weekly-status" macro tuned to that client's tone, while another workspace's macro of the same name reads completely differently. Switching workspaces switches the set of macros on offer, the same way it switches threads, files, and memory — see Workspaces.

A worked example

You write release notes every Friday, and the prompt that produces the format you like has stabilised: gather the week's changes, group them by area, one plain-English line each, flag anything user-facing. Save it as release-notes. Friday now looks like:

You    /release-notes
Blob   Drafting release notes for this week... 12 changes, grouped into 3 areas.

Two keystrokes and a confirmation, instead of re-typing (and slightly mangling) a paragraph-long prompt. The output is finally consistent because the input finally is.

Edge notes

• A macro fires as if you had typed the prompt yourself, so the run is metered like any other agent work and logged in Activity.
• Editing a macro changes future triggers only — runs that already happened keep their trails exactly as they were.
• If a macro has grown conditions and multiple stages, it has outgrown the format. Rebuild it as a workflow, where the steps are visible on a canvas.

Good to know

• Are macros shared? They are per-workspace, so people working in the same workspace use the same set.
• Does keeping macros cost anything? No — a macro only costs credits when a trigger actually runs work.
• Macro, automation, or workflow? You fire a macro; a schedule fires an automation; a workflow is for processes with multiple connected steps. A repeated ask on human timing is a macro.