What it does

You describe a task in a sentence. Magic plans it as numbered steps, each run by an agent, and hands back the files. The Magic page shows the four parts in order: Describe, See the plan and its price, Run and Get the files.

Modes

Auto uses several agents, Fast uses one, and Deep asks you questions first. Auto and Deep pause after planning so you can review the plan. Fast runs straight away.

Review and change the plan

Each step shows its agent and its cost, and the plan shows a total. You can change a step’s instructions, swap its agent, remove a step, or add one with Add a step. Steps cannot be reordered, because their order follows what each step needs from the others.

Under the total, Budget cap takes an optional number of credits. The run halts before the next group of steps whose cost would take it past the cap.

The button that starts the plan states the total, for example Run this plan · 12 cr. Save as template and Start over are on the same row.

Nothing is charged while a Magic plan waits for your approval.

When the plan cannot start yet

A step that needs a service you have not connected turns the run button into Connect Google Drive, named for the service. When more than one service is missing, the button reads Connect what this needs. Both open Settings → Connections.

A plan that costs more than your balance turns the button into Add credits · 4 cr short, which opens the Billing page. The plan is kept in both cases. Reopen it from Past runs on the Magic page when you come back.

Pauses during the run

The plan screen asks how often the run should pause for you. There are three settings, and new users start on the first.

Before each step: Pauses after every step for your approval. Slowest and safest.
Only when unsure: Pauses on clarifications and irreversible actions only.
Never: Runs to completion. Still pauses for a missing connection.

Cancel a run

To cancel a Magic run, press Stop this run on the progress screen. Steps that are already running complete, and no new step starts. Completed steps and their files are kept.

A cancelled Magic run is charged for completed steps only.

When some steps fail

The result heading counts the steps, for example 3 of 5 steps finished, and lists each failed step with its reason.

When some steps of a Magic run fail, only the completed steps are charged.

Retry the failed steps runs the failed steps and anything after them. The note under the button says Only the failed steps and anything after them run again. Completed steps are kept and are not charged twice.

Retrying the failed steps of a Magic run does not charge the completed steps again.

Other endings

Each ending below says what happened and the one thing to do on the screen it shows. Not every ending lands on the result screen: a plan that could not be built has its own screen, and a refusal for credits before the run started returns you to the request box or to a plan that can no longer be started.

Budget cap reached: The run halted before the next group of steps whose cost would take it past your cap. Completed steps are kept. A Magic run that reaches your budget cap is not charged for the credits it did not use. Use Run again. The plan comes back for review, and you can set a higher Budget cap before you start it.
Plan could not be validated: No step ran. The screen says We could not turn that into a plan. and shows what was unclear. Use Try rewording to edit your sentence, or Start from scratch. If a Magic plan cannot be validated, no step runs and nothing is charged.
Time limit: The run passed 30 minutes and was ended. Use Run again.
Failed: The run ended without delivering. Read the reason under each failed step. If Retry the failed steps is shown, use it. If no step is listed as failed, the reason is in the status line; use Run again.
Not enough credits before the run started: Nothing ran. The screen says Could not start and gives the reason. Add credits on the Billing page, then come back to Magic, type the request again and press Plan this task. This is the same whether the refusal came on the request box, which does not keep what you typed, or when you approved a plan, which cannot be started again after a refusal.
Not enough credits while retrying failed steps: The retry did not start. The screen shows Run failed with the reason above the result, and completed steps are kept. Add credits on the Billing page, then come back to Magic, open the run from Past runs and press Retry the failed steps again.

What it costs

Magic runs

Nothing is charged while a Magic plan waits for your approval.
When some steps of a Magic run fail, only the completed steps are charged.
A cancelled Magic run is charged for completed steps only.
A Magic run that reaches your budget cap is not charged for the credits it did not use.
If a Magic plan cannot be validated, no step runs and nothing is charged.
Retrying the failed steps of a Magic run does not charge the completed steps again.

Agent runs from the marketplace follow different rules.

Change a result

Refine re-runs only the steps your change affects, and shows the cost before you send it. A run can be refined up to five times, when it is done or when it reached your budget cap. Run again plans the same request again from the start.

Files

On a run that is done, the result screen exports it as PDF, Word (DOCX), Excel (XLSX), PowerPoint (PPTX, when the run made a deck) or Markdown. On any run, each file that can be downloaded has its own Download button.

Find past Magic runs

Past Magic runs are listed in Runs, filtered to Magic. The old address /magic/history redirects there. On the Magic page, Past runs reopens one.

From the API

POST /magic/execute takes query (required), mode (auto, fast or deep), and optional require_approval and budget_cap_credits. An API key needs the magic scope.

With require_approval: true the response has status: "planned" and nothing runs until you call POST /magic/execute/{execution_id}/approve, optionally with budget_cap_credits.

A run that reached its budget cap can be carried on with POST /magic/execute/{execution_id}/continue and a higher budget_cap_credits. The web app does not offer this; it uses Run again. A request returns 504 if the pipeline runs past 30 minutes.

Magic: tasks that need several agents