unswarm

Disables swarm mode by deleting the session swarm-mode marker file.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill unswarm-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unswarm
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/unswarm
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill unswarm-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When swarm mode is active for a session, the agent behaves differently than normal. This Skill turns swarm mode off so the agent returns to standard behavior for future tasks. ## Core Features & Use Cases - Session State Cleanup: Checks for and deletes the .zcode/session/swarm-mode.md marker file that enables swarm mode. - Behavior Restoration: Confirms swarm mode is disabled and resumes normal agent-runner behavior. - Use Case: After finishing a swarm-coordinated task, invoke this Skill to exit swarm mode and continue working with the default single-agent workflow. ## Quick Start Ask the agent to disable swarm mode for the current session and return to normal behavior.

Frequently Asked Questions about unswarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I disable swarm mode in an agent session?▼

Invoke the unswarm skill, which deletes the .zcode/session/swarm-mode.md marker file if it exists. Once removed, the agent resumes normal runner behavior for subsequent tasks.

What happens if the swarm-mode file does not exist?▼

The skill checks for the file first and only deletes it when present. If the file is missing, swarm mode is already inactive and the agent simply confirms normal behavior.

Does disabling swarm mode affect other sessions?▼

No. The marker file lives under the current session directory, so deleting it only affects the active session. Other sessions keep their own swarm-mode state.

When should I turn off swarm mode?▼

Turn it off when coordinated multi-agent work is finished and you want the default single-agent runner behavior. This avoids unintended swarm coordination on unrelated future tasks.