Creating, pausing and retiring
What happens to work in flight when an agent changes, and the one change that needs care.
Agents are standing, so they change while work is in progress. Most changes are safe to make at any time; one is not.
| Change | Applies | Work already running |
|---|---|---|
| Brief | Next run | Finishes under the old brief |
| Model | Next run | Finishes on the model it started with |
| Tool list | Next run | Finishes with the tools it started with |
| Spending ceiling | Next run | Finishes inside the ceiling it started under |
| Control mode | Next run | Finishes under the routing it started with |
| Pause | Immediately for new work | In-flight runs complete rather than being cut |
The change that needs care
Rotating a provider credential. Everything about the agent survives — connection, workspace selections, tool list, brief — but a run already talking to that provider with the old credential can fail. Rotate at a quiet hour if the provider is one an agent polls continuously.
Retiring an agent
- Its run history stays with the workspace. Removing an agent does not remove the record of what it did.
- Items it owned need a new owner. They do not silently return to triage.
- Anything of its sitting in the approval queue is still a decision somebody has to make.