To change a loop you already have, describe the change to Loopy in Loop Studio. You do not file a ticket and you do not edit anything by hand.
Loopy is in Studio, not in the support chat. The message icon in the bottom-right corner of Caddi reaches the Caddi support team. It is not where loop changes are made — Studio has the context on your loops and runs, so that is where to ask.
1. Open the loop in Studio
Either route works:
From the loop's page, select Edit Loop.
Or select Studio in the left navigation and choose Edit existing loop. If something has gone wrong rather than needing to change, choose Fix an error instead.
2. Say what should be different
Plain English is enough. Useful changes to ask for include adding or removing a step, changing a rule or a filter, pointing at a different source of truth, changing an output's format, adding a scenario the loop does not handle yet, or sending results somewhere else.
Include the following:
Say what you expected and what happened instead. "The client name should come from HubSpot, not the calendar title" beats "the names are wrong".
Point at a specific run when the change is prompted by one.
Attach the evidence. A revised template, a screenshot, the incorrect output — Studio takes attachments.
If Loopy is not sure which loop you mean, or needs a detail you have not given, it asks.
3. Loopy may ask to watch you
For a change that touches how a person decides, prioritises or judges something, Loopy will ask for a short recording rather than guess. Mechanical changes — a different folder, a renamed field — do not need one. See How To Record a Loop.
4. Your live loop keeps running the whole time
An edit builds a test version. Your active version carries on running, unchanged, while you work. Nothing you say in Studio reaches the live loop until you test the new version and select Make it Live.
Two kinds of change behave slightly differently:
A fix to the same goal — the loop was meant to do this and did not — is a repair. Loopy revises and rebuilds in the same turn; there is no new approval step.
A change to the goal itself — a different outcome, not a fix — re-opens the plan. Loopy re-checks that the new version can be built and shows you an approval card with the revised "Done when" criteria before rebuilding.
5. Test the change, then promote it
Loopy offers a test run when the rebuild is done. Run it, then check the real result in the system the loop writes to — a test that completes is not the same as a test that is correct. If it is right, select Make it Live. If it is not, say what is still wrong; the request stays open, so a follow-up fix is cheap.
If Loopy cannot do it
Ask it to bring in a person — "Connect me with the Caddi team", "I need help from a person", or "Please escalate this". Loopy opens a support conversation for you with the context from your Studio session attached, and the Caddi team picks it up from there. If the same fix fails several times in a row, Loopy escalates on its own without waiting to be asked.