Embodiments
Summon a Subject into an Office, adjust its role and tools, read runtime logs, and choose whether dismissal keeps or erases its experience.
An Embodiment is a Subject working in one Office. Give it responsibilities here, limit its tools, and dismiss it when work ends. One Subject working in two Offices has two Embodiments, with separate conversations.
Summon a Subject into an Office
For example, send the purchasing reviewer to a supplier review Office to check delivery risks.
- Open the target Office and select Summon. The Embodiment joins this Office.
- Choose a Subject. To start blank, select New person; this also creates a blank Subject.
- Check Code and Name. An existing Subject’s code and name are used by default. If it already works in another Office, give the new Embodiment a different code. Use lowercase English letters, numbers, and hyphens; do not start with a hyphen.
- Enter Role, such as “Delivery risk reviewer,” then What that role does, such as “Compare delivery records and cite a source for every risk.”
- Select Summon.
The Embodiment appears at the top of the Office in a preparing state. It can participate once ready.
View Embodiments and their states
On the Subjects page, select Embodiments to see those you can access. Each card lists its name, role, Office, and Subject, with direct links to the Office and Subject.
| Card state | Meaning |
|---|---|
| Pending, Provisioning, Starting | Preparing; do not treat it as already working. |
| Idle | Running, with no current thinking or tool activity displayed. |
| thinking | Waiting for the model to generate content. |
| working | Recently reported tool execution. |
| Error, Degraded | An error or operational problem. Check Why it failed first. |
| Stopping, Stopped, Deleting | Stopping, stopped, or being removed. |
When an error is recorded, the card shows it instead of idle. It also shows restricted tools and restart count. Select Manage to open the management drawer, read the full error, and use the actions below.
Define its responsibilities here
To focus a purchasing Embodiment on risk rather than negotiation, change its role in this Office instead of the whole Subject.
- Select Manage on its card and find Role.
- Role in this Office: enter a title others can see, such as “Delivery risk reviewer.”
- What that role does: enter responsibilities for the Embodiment itself, such as “Compare supplier delivery records; do not decide prices for the purchasing lead.”
- Select Save role.
You see Saved. In effect from the next turn. A turn here means the next time the Embodiment processes the conversation. The title helps people choose whom to ask; the responsibilities tell it what to do. A title alone does not supply a full brief. Role changes do not require Reapply.
Limit this Embodiment’s tools
If you want it to read browser pages but not click or fill forms, restrict browser actions and reading separately.
- In Manage › Tool limits, check the tool categories to hide from this Embodiment.
- Select Save restrictions.
Checked means prohibited, not enabled. Uncheck to lift this Embodiment’s restriction. Limits affect only this Embodiment; they do not disable services for the Office or require Reapply.
Read startup and restart logs
When an Embodiment keeps restarting or shows an error, read the specific logs before judging the cause.
- Open Manage › Runtime logs and select Current logs.
- If it keeps restarting, select Previous container's logs. This is output from the run before the restart, often more useful than empty startup logs.
Logs appear in the drawer. The top also shows restart count and Why it failed. No output shows The logs are empty. A read failure shows an error.
Refresh its state
If a card stays in starting, open Manage › Upkeep and select Sync. You see State refreshed. This checks the current runtime state; it does not reapply settings.
Apply the Subject’s latest long-form instructions
After changing the Subject’s SOUL.md, apply it to existing Embodiments.
- Open this Embodiment’s Manage › Upkeep.
- Select Reapply.
You see Settings reapplied. It applies the latest settings while retaining memory and skills. Persona, expertise, decision principles, and role are read on the next conversation turn and do not need reapplying.
Dismiss an Embodiment and choose whether to keep experience
When a project ends, let the Embodiment leave the Office. Keep the Subject for the next job.
- Open Manage › Dismiss.
- Choose what to keep:
- Dismiss: stop working in this Office and keep this Embodiment’s experience and Subject.
- Dismiss and erase experience: dismiss it and permanently erase experience belonging only to this Embodiment. The Subject and knowledge already retained for it are unaffected.
- Read the confirmation, then select Yes, dismiss or Yes, erase and dismiss.
The Embodiment leaves the Office and disappears from the Embodiment list. The Subject stays and can be summoned again.