Detect orphaned OCS artifacts and delete per-opp clones safely.
npx skills add https://github.com/dimagi-internal/ace --skill sweep-ocs
Please help me install this Agent Skill. Skill: sweep-ocs Source: https://github.com/dimagi-internal/ace/tree/main/skills/sweep-ocs Command: npx skills add https://github.com/dimagi-internal/ace --skill sweep-ocs
OCS (Open Chat Studio) resources like chatbots, pipelines, collections, and sessions accumulate orphaned per-opp copies after Connect opportunities close, wasting storage and incurring unnecessary embedding API costs. Manually identifying and safely deleting these orphans is error-prone, as accidental deletion of shared resources like the golden template chatbot or shared collection would break all active opportunities.
Use the sweep-ocs skill to generate a triage report of orphaned OCS artifacts for your current Connect opportunity.
High-intent search queries and answers about installing and using this skill.
To clean up orphaned Open Chat Studio resources, scan your OCS inventory against the current opportunity live set to identify unowned chatbots, pipelines, collections, and sessions. This process distinguishes safe-to-delete per-opp clones from protected shared assets like the golden template chatbot.
Orphan artifact triage in Open Chat Studio identifies chatbots, pipelines, collections, and sessions no longer referenced by active Connect opportunities. This triage is needed because accumulated orphaned per-opp copies waste storage and incur unnecessary embedding API costs after opportunities close.
Yes, you can safely delete per-opp OCS chatbots, their paired pipelines, and per-opp collections without damaging shared resources. Explicit guardrails prevent accidental deletion of critical shared assets like the golden template chatbot and shared collection.
The best way to reclaim storage from expired Open Chat Studio sessions is to soft-close them during an automated cleanup sweep. This reclaims storage and reduces embedding costs while preserving auditability of the closed session data.
Run OCS orphan cleanup in report-only recommendation mode to generate a triage report of orphaned artifacts for human approval. This mode surfaces safe-to-delete candidates and protected shared resources without performing any actual deletions or session closures.
A key limitation is the risk of deleting critical shared assets like the golden template chatbot, which would break all active Connect opportunities. To mitigate this, use approved execution mode with explicit guardrails that only delete pre-approved orphaned per-opp resources.
dimagi-internalParse opp.yaml and run_state.yaml files to generate a timestamped live-set.yaml artifact.
dimagi-internalDetect orphaned Connect artifacts and generate prioritized triage reports.
dimagi-internalGrade OCS widget handoff artifacts for URL resolution, link accuracy, and credential hygiene.
dimagi-internalDetect orphaned Google Drive folders under ACE/ and generate triage reports.
