Disable or Delete an Agent Stack

You sometimes need to take a stack out of service — for an experiment, after a bad deploy, or because the team it served has gone away. There are two operations: disable (reversible) and delete (permanent).

When to use each

• Disable — Pause a stack temporarily. Config stays intact. New conversations skip it. — Yes — toggle back on
• Delete — Remove a stack permanently. Config, specialists, and assignments are dropped. — No — only the change history of the deletion remains

Disable a stack

1. Open Settings → Agent Stacks and click into the stack.
2. On the General tab, find the Enabled switch (in the header row).
3. Toggle it off.
4. The change saves immediately. The stack now skips routing for any new inbound conversations on its enabled channels.

What stays the same: every specialist’s config, knowledge access, capabilities, personality, handover settings — all preserved. Toggle the switch back on whenever you want to resume.

What changes: in-progress conversations the stack was already handling continue until they reach a natural conclusion or get handed off. New conversations that would have routed to this stack go to the channel’s fallback (often a team queue or another stack, depending on your channel settings).

Delete a stack

1. Open Settings → Agent Stacks and click into the stack.
2. Click the Danger Zone tab.
3. Type the stack name in the confirmation field. Click Delete stack.
4. The stack and all its specialist agents are deleted. Existing conversations that were assigned to it lose the assignment — they don’t get re-routed automatically; treat them as orphaned and clean them up via the inbox.

Once you click delete, this is final. There’s no undo. The Change History tab on the parent settings (or the audit log) records the deletion event.

Verify it worked

• For disable: the Alia tab in Conversations should stop accumulating new conversations from this stack’s channels (existing ones still complete).
• For delete: the stack disappears from the Settings → Agent Stacks list. Any reference to it in change-history will still resolve, but you can’t open it.

Troubleshooting

• Symptom: I disabled a stack but conversations are still being routed to it. Fix: confirm the toggle saved (look for the success toast). If the stack is wired to channels via channel-level settings, the channel may take a moment to pick up the change — wait 30 seconds and re-test.
• Symptom: I want to disable just one specialist, not the whole stack. Fix: open the specialist from the Orchestrator canvas and toggle that specialist’s enabled flag on its Setup sub-tab. The stack stays live; only that specialist stops getting routed to.
• Symptom: I deleted a stack and the channel it was wired to is now broken. Fix: the channel’s AI agent assignment may still reference the deleted stack. Open the channel’s settings and pick a different stack (or none) as the AI agent.

See also

• Create an Agent Stack
• What are Agent Stacks?