Assistants

An assistant is an AI helper whose saved instructions and tools can be reused. Mobius calls this resource an agent in the app, API, and CLI, so those exact labels and identifiers remain in this page.

Northwind's Scout assistant can turn supplied service notes into an operations brief. Maya improves Scout's instructions once, then selected colleagues can use the same Scout in separate conversations. The useful behavior is shared; their messages are not combined.

What you save on an assistant

Open an assistant's Configure tab to see the choices that shape its work:

The organization can also hold shared background under Build > Context. Every member may read that company context, only administrators may change it, and it is included in later assistant work. Keep it to facts that every assistant in the organization should receive.

An assistant does not get an external account merely because that account is connected. Grant the assistant access to the exact account it needs. The same grant can support eligible conversations and routines, while the account's acting identity and allowed result audience still apply. See connect accounts and set access.

Create a focused assistant

You need permission to build resources. Making an assistant available to a group or the whole organization also requires organization administration.

1. In the app, open Build > Agents.
2. Click New agent.
3. Fill in Agent name, Agent description, and Agent instructions.
4. Leave Model on the available default for the first test.
5. Under Who this agent is for, leave Just me selected.
6. Click Create agent.

The app creates a private assistant by default. The employee API does the same when visibility is omitted, but API clients should set that field explicitly. A service principal that is preparing an assistant for other people must name the intended organization or restricted audience rather than relying on a default.

For a first version of Scout, these instructions are enough:

Prepare an operations brief from facts supplied in the request. Do not invent
missing owners, causes, or dates. Include Schedule and Risks. If a section has
nothing to report, say so.

The instructions describe a job you can check. Scout has no reason to contact another service yet.

Use before you equip

On the assistant's page, click Chat and give it facts you already know. Check the reply for unsupported claims and missing details. Open a fresh conversation after an instruction change so the same input gives you a clean comparison.

Add a tool or account only when the test shows why it is needed. Tools describe what the assistant may try, while account grants decide which connected identity it may use. Mobius revalidates the exact connection, live grant, account binding, and container audience before every external action. It does not automatically ask a person to confirm an action that changes data. Add a deliberate interaction to the instructions, and tell the assistant to wait for the answer, when the task should stop for human review. That review follows the instructions instead of acting as an automatic gate on every write.

Share use without sharing the conversation

An assistant's audience controls who may reach it:

• Just me keeps it with one person.
• Only listed people gives a named group the same saved behavior.
• Everyone in the org makes it available across the organization.

Audience is one part of access. A listed person still needs the organization permission to use assistants. Reading configuration, editing the definition, managing the audience, controlling an account, and receiving an external result are separate decisions. Who can use an assistant shows how they fit together.

When two people use Scout, each conversation becomes a separate session. A routine occurrence also gets its own session. The routine's saved setup names Scout, but it does not continue in the private chat where someone first suggested the routine.

Improve the assistant people already use

Open Build > Agents, choose the assistant, select Configure, and click Edit. Change the instructions, model, tools, skills, or other settings, then click Save.

The assistant keeps the same ID. Earlier conversations and completed turns do not change. Future turns read the current saved definition, including the next turn in an existing conversation. A conversation with an explicit model override keeps that model even if you change the assistant's model default.

Edit the existing assistant when you are improving the same job for the same access boundary. Create a separate one when the new job needs different people, accounts, or private knowledge.

Put information in the right place

Mobius does not learn a new team rule from everyone's conversations automatically. Someone has to promote the useful change into instructions, shared memory, a skill, or a maintained data source.

Disable or delete an assistant

Open Agent actions on its page. Disable agent stops new work and removes the assistant from available routing choices; it does not cancel work already in progress. Enable agent makes it available again.

Use Delete agent only when the company no longer needs that assistant. Check its routines, connected accounts, and records first so you know what will lose its active dependency.

Exact API fields live in the Agent configuration API guide. Terminal commands are in the CLI command reference. For a focused editing method, read assistant instructions and settings.