Matrix recipes

A Matrix recipe is a reusable task brief. It describes the inputs an agent needs, the work to perform, the expected result, and what you should review.

Browse Matrix recipes for research, weekly reports, bug fixes, campaign briefs, meeting follow-ups, and software spend reviews.

Use a recipe today

1. Open a recipe and choose Open in Matrix. Public inspiration cards use Build in Matrix.
2. On a computer with recipe handoff support, Matrix opens a new Chat draft for the selected recipe. Review the draft and choose your model before sending.
3. You can also choose Copy recipe and paste the instructions into Chat or Electron Desktop. If copying is blocked, expand Read the full instructions and copy the visible text.
4. Provide the requested files or source material. Connect required tools through their supported authentication flows.
5. Review the result and its sources before using it or approving an external action.

These are manually started task briefs. They do not install a bot, connect an account, or create a schedule. Results depend on the agent, tools, and inputs you provide. Missing access should be reported as a blocker.

Opening a recipe does not send the draft or install an Agent. If an older Matrix computer opens without the draft, use Copy recipe instead.

On computers where Chat Agents is enabled, you can ask Chat to create a reusable Agent. Agree on its role, then review the saved Agent through Manage agents in the Chat rail. Available Codex and Hermes models are supported. A saved Agent appears in the rail; selecting it prepares a request with its configuration. Confirm its access before sending. If setup or saving fails, Chat should report the blocker rather than claim the Agent is ready.

Repeat a successful task

Start with a single run. Refine the instructions after reviewing the output, then save your preferred brief in your workspace. Scheduling is a separate setup and requires an eligible plan and runtime capability. Builder and Max support always-on work; Starter sleeps when inactive and excludes scheduled and always-running agents.

Recipes, agents, skills, and schedules

• A recipe describes a job and the result you want.
• An agent does the work using the tools available to it.
• A skill supplies reusable instructions for a capability.
• A schedule determines when a recurring task runs.

A recipe can reference skills and be used for recurring work, but copying its text does not grant permissions or enforce a security policy. Review the chosen agent's permissions and approve external actions deliberately.

Keep credentials out of recipe text. Share reusable instructions without private source files, account tokens, or previous run results.