Skip to main content

Loop Studio: what's changing and why

On July 31, all building and editing moves to Loop Studio. Migration is automatic — here's what to expect and what to check.

Loop Studio is becoming the main workspace for building, editing, testing, running, and troubleshooting Caddi loops.

What's changing

On July 31, 2026, Caddi will retire the previous building and editing experience. Loopy will also move fully to Loop Studio, so all loop changes and questions should go through Studio chat.

Your existing loops will be migrated automatically. You will not need to rebuild them, and scheduled loops will continue running on their current schedules. Caddi will let you know when your migration is complete.

Build, test, and manage loops in one place

This isn't just a new home for the old workflow — Studio makes the whole loop lifecycle faster and safer:

  • Provide context however is easiest.
    Describe the process in plain English, share your screen, or upload PDFs, screenshots, and business rules. Loopy interprets the context, identifies inputs, surfaces edge cases, and asks smart questions early so builds are ready for real-world use.

  • Build and edit in minutes.
    Create or update loops in one conversation instead of waiting hours or days.

  • Test before going live.
    Run the real automation, review results step by step or all at once, and quickly see what was expected versus what happened.

  • Edit without interrupting live loops.
    Changes are saved as a test version. Your live loop keeps running until you select Make it Live.

  • Investigate runs in plain English.
    Ask questions like “Why was this document skipped?” and get a direct answer from Loopy.

  • Manage everything in one place.
    Build, edit, test, schedule, troubleshoot, and escalate to the Caddi team from the same chat.

Why we're making this change

The previous experience split building, editing, testing, and troubleshooting across different places. Loop Studio brings everything into one conversation with Loopy, which has context on your loop and its runs.

You can describe changes in plain English, test them before making them live, investigate unexpected results, and get help from the same place.

What you need to do

Migration itself requires no action. Once Caddi confirms your loops have been migrated:

  1. Open your most important loops in Loop Studio.

  2. Run a test using appropriate test data.

  3. Verify the result in the destination system and confirm the inputs and schedule are correct.

  4. Use Studio chat for all future builds, edits, and loop questions.

If something looks wrong, tell Loopy. If it cannot resolve the issue, you can escalate to the Caddi team from the same chat.

What if the new version is incorrect?

Do not select Make it Live. From the loop page, select Edit Loop, or open Loop Studio from the left navigation, then tell Loopy what needs to change. Your current live version will continue running unchanged while you update and retest the new version.

If Loopy cannot resolve the issue, click the support icon or ask to be connected with the Caddi team. You can say, “Connect me with the Caddi team,” “I need help from a person,” or “Please escalate this.”

Timeline

  • Now through July 30: Caddi is migrating loops account by account. Start using Studio once your migration is confirmed.

  • July 31: The previous building and editing experience retires, along with the old chat.

  • After July 31: All building and editing happens in Loop Studio. Existing schedules continue running.

Learn more

Did this answer your question?