Sweep Away Orca Residue in Your Agent Stack

Where this fits

You removed Orca from your workstation, but your Codex, Claude, or Cursor agents still attempt to call Orca CLI or Computer Use on every new run. Orca Agent Cleanup finds and reversibly quarantines the forgotten skill definitions, hooks, config entries, and CLI residue that cause those ghost calls.

Why agents benefit

• Gives the agent an explicit audit path: scans known Windows/macOS/Linux locations for Orca-managed artifacts and reports them deterministically.
• Uses quarantine, not delete: leftover hooks and skill files move to a recoverable location, so an agent can roll back if removal was too aggressive.
• Covers the full blast radius: agent skills, hooks, CLI binaries, speech/voice model metadata, and app data—not just obvious config files.
• Reduces hallucinated fixes: the skill reports what residue exists instead of guessing at commands that may not exist on the user's platform.
• Works in the existing agent loop: after npx skills add, the agent can invoke the skill as a normal cleanup step and verify the result.

Practical scenarios

Orca has been uninstalled but agents still try to use it

A developer uninstalls Orca, then opens Claude Code. The session tries to call Orca for a browser-automation step and fails. Running the cleanup skill surfaces the stale skill folders and hook registrations, quarantines them, and lets the agent continue without rerouting around phantom tools.

Preparing a clean machine image for new agents

A team ships a dotfiles or devcontainer setup that includes many agent skills. Before committing the image, an agent scans for Orca CLI residue left by an earlier install, preventing every future agent from inheriting broken hooks.

Standardizing uninstall across Windows and macOS workstations

In a mixed environment, teammates uninstall Orca differently. The cleanup skill gives each agent a cross-platform procedure, so Windows Registry-side entries, macOS LaunchAgent hooks, and Linux shell profile exports all get the same reversible treatment.

Add it to your agent workflow

Install the skill with:

npx skills add wilgon456/orca-agent-cleanup

Then ask your agent to run a cleanup pass:

Scan this machine for Orca-installed agent skills, hooks, and CLI residue and quarantine them without deleting anything permanently.

The agent uses the skill to identify residue, show a summary, and move artifacts to a timestamped quarantine folder. If a quarantine is too aggressive, restore from that folder.

Compare before adopting

Before wiring this into every agent, compare a few signals:

• Quality: 37 stars, v1.2.0, a CI workflow with tests, and a license are good starts; check the test matrix covers your OS.
• Maintenance freshness: look at recent commits and issues, because cleanup logic depends on file paths and hook formats that change quickly.
• Alternatives: manual uninstall checklists and generic file-search prompts work, but they lack a cross-platform quarantine concept.
• Workflow fit: confirm target locations match the agent tools you use (Codex, Claude, Cursor) and that rollback fits your tolerance.

Why it is worth tracking

This utility sits in the useful middle ground between agent skill and system maintenance tool: small enough to audit, broad enough to matter when agent behavior regresses. The project has visible signals—automated tests, cross-platform badges, a versioned release, and 37 stars—while staying small enough to reason about. Keep it in mind whenever an agent references Orca features after an uninstall, or a fresh machine inherits leftover hooks. For more on evaluating this utility in a broader agent-skill workflow, see https://www.openagentskill.com/skills/wilgon456-orca-agent-cleanup.