cancel

Cancel Ouroboros executions by ID or in bulk via CLI.

5.4k|535|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Q00/ouroboros --skill cancel-q00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Q00/ouroboros/tree/main/skills/cancel
Command: npx skills add https://github.com/Q00/ouroboros --skill cancel-q00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel stuck or orphaned Ouroboros executions by session or execution ID, helping reclaim resources and reduce clutter.

Core Features & Use Cases

  • Bare mode: interactively list active executions and cancel one.
  • Explicit mode: cancel a specific execution by its ID.
  • Cancel all mode: terminate all running or paused executions at once.
  • Optional reason: supply a reason to log why the cancellation occurred for auditing.

Quick Start

Invoke with the cancel command to list active executions and pick one to cancel, or supply an execution ID to cancel directly.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel stuck or orphaned executions in an interactive CLI session?

To cancel stuck or orphaned executions in an interactive CLI session, use Bare mode to interactively list active executions and select the specific one to terminate. This quickly reclaims resources and reduces process clutter.

Can I cancel all running or paused executions at once?

Yes, you can cancel all running or paused executions at once by using the --all option. This terminates every active execution simultaneously, helping reclaim resources and reduce clutter from orphaned processes.

How do I log the reason for cancelling an execution by ID?

To log the reason for cancelling an execution by ID, use the optional --reason flag when invoking the explicit cancellation command. This supplies auditing context to the event store, recording why the termination occurred.

What happens to the event store when an execution is cancelled?

When an execution is cancelled, the process emits events directly to the event store via the Ouroboros CLI. This ensures the termination is properly logged and the execution state is updated across the system.

Do I need an execution ID to terminate orphaned processes?

No, you do not need an execution ID to terminate orphaned processes. You can use Bare mode to interactively list and select active executions, or use the --all option to cancel every running or paused execution without specifying individual IDs.