DocsStart

Quickstart

Create Scout, improve its saved instructions, and let a colleague use the same assistant in a separate conversation.

This guide turns supplied service notes into a short operations brief. You can check every fact, improve the saved instructions, and then give a colleague the same working setup without sharing your conversation.

Northwind is a fictional services company. Its operations lead, Maya, is building an assistant named Scout for the operations team.

Before you start

You need a Mobius account, permission to create assistants, an available model, and organization funding or a connected provider key that permits that model. The app calls assistants agents in its current labels.

To complete the sharing steps, you also need:

  • permission to make an assistant available beyond Just me;
  • a second member of your Mobius organization whom you may add to Scout; and
  • a way for that colleague to sign in separately.

An organization owner or administrator can publish an assistant to a group. If the wider audience choices are disabled for you, complete the private setup and ask one of them to make the audience change with you. Audience membership lets the colleague use Scout. It does not, by itself, give them permission to edit Scout or read its private configuration.

Create Scout

  1. In the app, open Build > Agents.

  2. Click New agent.

  3. In Agent name, enter Scout.

  4. In Agent description, enter Turns supplied operations notes into a brief the team can scan.

  5. In Agent instructions, enter:

    You prepare a daily operations brief for Northwind, a services company.
Use only facts in the request. Do not guess at people, causes, times, or
work that was not mentioned. Start with Today. Include Schedule and Risks.
If a section has nothing to report, write None reported. Keep the brief
under 120 words.

  6. Leave Model on the available default.

  7. Under Who this agent is for, leave Just me selected.

  8. Click Create agent.

The notice Agent created with Scout is ready confirms that the saved assistant exists. Scout is private at this point.

Check the first brief

  1. On Scout's page, click Chat.

  2. Send this message:

    Prepare Wednesday's operations brief from these notes:
 
- Northwind has 14 client visits scheduled.
- The 9:00 AM visit at Harbor Dental does not have a technician assigned.
- Replacement filters for Juniper Market arrived yesterday and are on shelf B4.
- The office closes at 4:00 PM for fire alarm testing.
- No other delays were reported.

The wording may vary. Check the facts instead. Scout should mention 14 visits, the unassigned Harbor Dental visit at 9:00 AM, the filters on shelf B4, and the 4:00 PM office closure. It should not invent an owner, a reason for the missing assignment, or another delay.

If the turn fails, open its saved error before changing Scout. An available model can still be refused when the organization's plan, credits, or provider credentials do not permit the call. Ask an administrator to repair the named funding or credential issue, then retry the same facts.

This conversation holds Maya's message and Scout's reply. The instructions on Scout are saved separately, ready for another conversation.

Improve the saved instructions

The first brief identifies the assignment gap, but Maya wants it to stand out every morning.

  1. Open Build > Agents, then open Scout.

  2. On the Configure tab, click Edit.

  3. At the end of Agent instructions, add:

    End with a heading called Owner needed. List any work that has no named
owner. If there is none, write None.

  4. Click Save.

  5. Click Chat to start a fresh conversation with Scout.

  6. Send the same Wednesday notes again.

The new brief should end with Owner needed and identify the unassigned Harbor Dental visit. The first conversation remains unchanged. Editing saved instructions affects later turns; it does not rewrite an earlier request or reply.

Share Scout with one colleague

Widening Scout's audience publishes its shared knowledge to more people, so the app requires organization administration and asks you to review the change.

  1. Return to Build > Agents > Scout.
  2. On Configure, click Edit.
  3. Under Who this agent is for, select Only listed people.
  4. Keep yourself in the list and add the colleague who will test Scout.
  5. Click Save.
  6. Review the audience preview, then click Confirm audience.

Scout's page should now show Only listed people and the audience count. Only the listed people can reach Scout, subject to their organization permissions.

Have the colleague use the same Scout

Use the colleague's own signed-in account for these steps. A solo reader can prepare the audience and hand off here, but a second account is required to check reuse and privacy.

  1. In the colleague's account, click New Chat.

  2. Choose Scout from the Agent menu.

  3. Send:

    Prepare Thursday's operations brief from these notes:
 
- Northwind has 10 client visits scheduled.
- Every visit has a technician assigned.
- The Cedar Cafe visit moved from 10:00 AM to 2:00 PM.
- No supply delays were reported.
- The office is open normal hours.

The colleague did not copy Scout's instructions. The reply should still use the saved headings, stay under 120 words, and end with Owner needed: None.

Open Chats in the colleague's sidebar. The colleague's conversation with Scout should appear. Maya's Wednesday conversations should not. Both people used the same assistant definition, while each conversation kept its own messages.

Continue with live work

After the colleague completes the check, Scout's saved improvement helps more than one person. The next useful move is to connect the account that holds the live operations source, grant Scout access to that specific account, and repeat the same fact check with a harmless read.

Once the connected result is dependable, create morning-brief as a weekday 7:00 AM routine. Choose its custody deliberately. A business-owned routine must name a responsible person, such as operations@northwind.example, and each occurrence runs in its own conversation. Follow the morning brief to Slack guide to set the source, allow the result audience, run the routine once, and verify its post to #operations before you leave the schedule active.