Retro — learning from mistakes
Retro is Makion's learn-from-mistakes loop. It reviews past sessions, finds where the agent went wrong, and proposes concrete improvements — a tightened rule, a better example, or a bug report for Makion support. You review each proposal and decide. Retro is a superadmin surface.
You reach it two ways:
- Open the Proposals sub-tab of Admin chat.
- Type
/retro since=YYYY-MM-DDin Admin chat to mine sessions from a given date.
What a proposal is#
Makion turns each mistake it finds into a proposal of one of four kinds:
| Kind | What it does | Where it goes |
|---|---|---|
| Rule fix | Adds or changes a base rule so the mistake doesn't recur. | Applied to this server. |
| Knowledge fix | Adds or corrects a knowledge-base file (a standard or example). | Applied to this server. |
| Code defect | The problem is in Makion itself, not your configuration. | Sent to Makion support. |
| Discard | Not worth acting on — noise or a one-off. | Closed with no change. |
What each proposal shows#
Every proposal is evidence-backed so you can judge it quickly:
- Symptom — what went wrong, observably.
- Root cause — why it happened.
- Evidence — the session detail that supports the diagnosis.
- A possible-duplicate warning when it resembles an existing rule or an earlier proposal.
- The exact change — spelled out before you approve, e.g. "Will add this rule…" or "Will replace the content with…" — so nothing is applied blind.
Acting on a proposal#
| Action | What it does |
|---|---|
| Approve & apply | Applies the change to this server. Changes are versioned and reversible — you can roll them back. |
| Approve & send to support | Sends the proposal to Makion support (used for code defects). |
| Reject | Declines the proposal; you give a reason, which is kept. |
| Measure effect | Compares correction counts before → after the change, so you can see whether a fix actually helped. |
Approving a rule or knowledge fix is reversible and versioned, so it is safe to try one and later Measure effect. If the numbers don't improve, roll it back.
Filtering the queue#
A status filter narrows the list to Pending / Applied / Sent / Rejected / All, so you can work through new proposals or review what you've already actioned.
How Retro fits the methodology#
Retro is the feedback loop on top of Methodology: the base rules and knowledge base you write by hand are refined over time by proposals mined from real work. Applied fixes land in the same base rules and knowledge base the agent reads on every run — see Configuring projects for how those layers steer the agent.
Where to go next#
- Admin chat — where the Proposals sub-tab lives.
- Methodology — the rules and knowledge base that proposals refine.
- Audit trail — the record of what the agent actually did.