# Plans

> A plan lists the actions an agent, or you, want to carry out. Review it, approve or refuse it, resume it after a failure, undo it.

Source: https://docs.fransys.cloud/en/agents/plans/ Checked against the console on 2026-10-23.

## What a plan is

A list of actions on your projects and clusters (create a service, set a variable, deploy…), with what each one will do. Nothing runs until a person on your team approves it.

A plan comes:
- **from an agent**, through the MCP: it lands in **To decide**;
- **from the console**: your changes are recorded in a plan under your name (“Changes made in the interface”), completed by the next deployment;
- **from an import**: **Import a plan** accepts a plan in JSON format, shown for review.

## The Plans page

One section per state: **Running**, **Failed**, **To decide**, **To deploy**, then the **History**. Filter by project with **Filter by project**.

| Status | What it means |
|---|---|
| Draft | Being prepared, not submitted yet. |
| To decide | Waiting for your decision. |
| Approved | Approved, not started yet. |
| Running | The actions are running. |
| Done | All the actions are done. |
| Failed | An action failed; the plan stopped. |
| Refused | Refused, with the reason given. |
| Cancelled | Cancelled by its author, or abandoned. |
| To deploy | Changes saved, waiting for the project to be deployed. |

## Review a plan

Click **Review**. The plan page says who prepared it and lists its actions, run in order with your permissions. It points out:
- actions with a **direct effect**: deployment, deletion or machines;
- other changes already pending on the project, which will go out with the deployment.

Secret values are masked. **Show the plan's JSON** shows the plan as it's stored.

## Approve or refuse

- **Approve and run**: Fransys runs the actions in order. You can close the page; the run keeps going.
- **Refuse**: say why; the author, agent or person, will see it.
- **Cancel plan**: for a plan you prepared yourself.

## When a plan stops

If Fransys refuses an action, the plan stops. **What Fransys answered** details the calls made by the failed action. Actions already done are kept.

- **Resume**: resuming starts again from the action that failed. What was already created is found again; nothing is created twice.
- **Abandon**: the plan moves to the history as cancelled. Actions already done stay in place.

## Undo a plan

On a plan that has run, **Undo this plan** prepares a new, opposite plan, which you review and then run like any other. The window lists what will be undone and what can't be (a deleted service, for example).

Settings go back to the value they had before this plan, even if they've been changed since.

## The activity log

Every plan leaves a trace in **Activity**: who prepared, submitted, approved or refused it, and the result of each action. Filter by **People** or **Agents**.