Macro Runner

The Macro Runner lists the macros you installed from the Macro Marketplace and applies them to the workspace you are looking at. Applying a macro replays its commands in your browser, one every half second, from top to bottom.

Where to find it

View > Machine Learning > Macro Runner.

Sign-in is required: without a session the panel shows “Please sign in to use macros.”

What it shows

Only macros whose installed list contains your email. If you have not installed anything, the panel reads “No macros installed. Visit the Macro Marketplace to install macros.”

Each installed macro gets a row with its name, By <author>, and its description.

Controls

• View Operations: opens a modal titled <macro name> - Operations showing the macro’s raw command list. This is the only preview available; it does not simulate the run.
• Apply Macro: runs the macro.

Applying a macro

1. Open the map or panel the macro expects. Commands act on the current workspace, so a macro that assumes a map is open will do nothing useful if one is not.
2. Click View Operations to check what the macro will do.
3. Click Apply Macro. Commands dispatch in order with a fixed 500 ms gap between them, so a twenty-line macro takes about ten seconds.

Limits

This panel is deliberately thin. It does not do any of the following:

• No progress display. There is no per-command status, progress bar, or spinner. Watch the workspace itself to see the macro land.
• No logs. Nothing is written to a panel log; failures only reach the browser console.
• No pause, stop, or cancel. Once applied, a macro runs to completion. Re-running means clicking Apply Macro again.
• No run history. Nothing records that a macro ran.
• Errors are not specific. If a command throws, the whole panel is replaced with “Failed to execute macro. Please try again.” The panel does not say which line failed, and the remaining commands are skipped.
• Macros only. Agents and workflows are not run from here; they belong to the Composer, Jarvis, and the Agno Workflow Builder.

Commands the language does not implement, such as search and create_bag, are skipped without complaint. See the macro language page for the full list.

Read nextMacro languageWhat each command does, and which ones are no-ops.