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

Disable a stack

1. Open Settings → Agent Stacks and click into the stack.
2. On the General tab, find the Enabled switch in the Stack settings card.
3. Toggle it off.
4. The change saves immediately — that switch has its own save and doesn’t wait for Save changes. 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 stay where they are. New conversations on a channel pointed at this stack fall through to your workspace’s default stack instead — the catch-all that handles channels with no other stack assigned. If the default stack is itself disabled, routing fails and no AI reply is produced.

Delete a stack

1. Open Settings → Agent Stacks and click into the stack.
2. Click the Danger Zone tab.
3. Click Delete this stack permanently, then Delete in the confirmation dialog. There is no name to type.
4. The stack is deleted. Conversations it already handled stay in your history, but they lose their AI assignment and drop out of the inbox tab that lists Agent Stack conversations (named after your default stack, or Agents if you have none); new messages on the affected channels fall through to the default stack.

The default stack can’t be deleted. On that stack the Danger Zone tab shows a note instead of a delete button, and the server refuses the request.

Once you click delete, this is final. There’s no undo, and nothing records the deletion as an event.

Verify it worked

• For disable: the inbox tab that lists Agent Stack conversations (named after your default stack, or Agents if you have none) 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. Tuning changes that were applied to it survive in the change log, but they no longer point at a stack, so the Change History tab is not a way to look them up afterwards.

Troubleshooting

• Symptom: I disabled a stack but conversations are still being handled by it. Fix: first confirm the toggle saved — you should see an “Agent stack updated successfully” toast. Then check whether those are existing conversations: the enabled flag is only consulted when a conversation is first assigned to a stack, so a conversation already assigned keeps running on it. Only brand-new conversations skip a disabled stack.
• Symptom: I want to disable just one specialist, not the whole stack. Fix: open Settings → Agent Stacks → [stack] → Orchestrator → [specialist] → Setup and turn Active off. The specialist row stays visible with an Off badge, but routing skips that specialist. A stack must keep at least one active specialist; to pause the whole stack, disable the stack instead.
• Symptom: I deleted a stack and the channel it was wired to no longer answers with AI. Fix: deleting the stack clears that channel’s AI agent field, so the channel now has none. Open the channel’s settings and pick a different stack as the AI agent.

See also

• Create an Agent Stack
• What are Agent Stacks?