mobius

Get started free
Get started free

Start

Quickstart

This guide turns rough backup notes into a client update draft. The notes are included in the instructions, so you will know which facts the agent received and can check that it did not invent anything important.

You will create three types of Mobius resource:

  • Scout, an agent that writes short service updates.
  • Client update draft, a loop with one agent step. A loop is a process you save so you can run it again.
  • A run, which is the record of one time the loop ran.

The loop starts only when you click Run. It does not connect to a backup system, contact a client, or run on a schedule.

Before you start

You need:

  • a Mobius account;
  • a project you can edit; and
  • at least one model available in the agent form. A model is the AI, such as Claude or GPT, that writes the response.

Mobius creates a default project during account setup. A run may use paid model services, so make sure you are allowed to use your organization's model access. If the model menu is empty, ask your Mobius organization administrator to check that access before continuing.

Northwind IT and Ridgeline Dental are fictional companies used throughout this guide. Replace them with your own names when you adapt the example.

1. Create Scout

  1. Click Open app in the docs header, or open the app directly. Sign in if asked. Mobius opens your default project. Use Switch project at the top if you need a different one.

  2. In the sidebar, open Build, then click Agents.

  3. Click Create agent.

  4. Set Agent name to Scout.

  5. Set Agent description to Turns service notes into clear client updates.

  6. In Agent instructions, enter:

    You write short updates for clients of Northwind IT. Use only the facts in the
request. Do not guess at causes, dates, people, or work that was not mentioned.
State the current result first, then explain what happened. End with any action
the client needs to take. If no action is needed, say so. Keep the update under
120 words.

  7. Leave the model on its available default.

  8. Click Create agent.

Mobius opens Scout's page and shows the message Scout is ready. If you miss the message, seeing Scout's page is enough to confirm it was created. The agent's instructions are the standing rules Mobius sends with Scout's assignments. The next section gives it one specific assignment.

2. Create a one-step loop

  1. In the sidebar, open Build, then click Loops.

  2. Click New loop.

  3. Click the Untitled loop title and replace it with Client update draft.

  4. Under Triggers, leave Manual run as the only trigger. The Always on badge means the Run button is always available; it does not mean the loop starts automatically.

  5. Under Steps, use the Agent card that Mobius added to the new loop. If it is missing, click Add step, then choose agent. In agent instructions, replace the placeholder text with:

    Write a client update from these notes:
 
- Ridgeline Dental's overnight backup reported a failure at 2:14 AM.
- The automatic retry started at 2:29 AM.
- The retry completed successfully at 2:47 AM.
- The latest backup is complete. No client action is needed.
 
Do not say that anyone was notified. Do not add a cause for the first failure.

  6. At the bottom of the Agent card, click Select agent, then choose Scout.

  7. Under Settings, leave Time limit 10m and the other settings at their defaults.

  8. Click Create.

The loop page should now show one Agent step assigned to Scout and no automatic triggers.

3. Run it and inspect the record

Warning: A run may use billable model or tool services even if it fails.

  1. On the loop page, click Run.
  2. Mobius opens the new run. Stay on Timeline while the agent step is running.
  3. At the top of the run page, wait for the status to change from running to completed. A short stay in queued means the work is waiting to start. If it has not completed after the ten-minute run limit, reload the page and read the final status and error.
  4. Read Scout's response in the agent step. Then open Output. Because this loop did not select a smaller set of final fields, Output contains all saved step results, including Scout's response under agent.

The wording will vary because an AI model wrote it. Check the facts instead. The result should name Ridgeline Dental, say that the backup failed at 2:14 AM, the automatic retry ran from 2:29 AM to 2:47 AM, the latest backup is complete, and the client does not need to act. The current result should come first. The draft should be under 120 words and should not name a cause for the first failure or claim that someone was notified.

If the run shows failed, open the failed step and read its error. The run keeps the error message. If it names a setting you cannot change, such as model access, copy the error for your Mobius organization administrator. If the agent or instructions are missing, edit the loop and add them. For any other error, keep the run open as a record and follow the specific message before trying a new run.

4. Change one fact and run it again

Now make a change with an obvious result.

  1. Return to Build > Loops > Client update draft.

  2. Click Edit loop.

  3. In the agent step, change the last note to:

    - The latest backup is complete. Northwind will review the backup logs today;
  no client action is needed.

  4. Click Save changes.

  5. Click Run again.

The second result should say that Northwind will review the logs today and that the client does not need to act. It must still satisfy the first result's fact checks. To compare it with the first, click the Client update draft loop link at the top of the run page. Under Recent runs, confirm there are two completed runs, then open the older one. Its agent step still shows the original notes and result. Editing a loop changes future runs; it does not rewrite runs that already finished.

What you just learned

The model produced the response. Scout supplied the standing writing rules. The loop's agent step supplied this assignment and its backup facts. The manual start created a run, which kept the facts, activity, result, and final status from one attempt. Timeline shows the activity and status. Output shows the saved result.

Most Mobius work follows the same sequence:

  1. start with facts you can check;
  2. run the smallest useful version by hand;
  3. inspect the run;
  4. change one thing; and
  5. add an outside event or schedule only after the result is dependable.

Next