clear-old-outputs

To prune old Pixie runs and artefacts safely, run a dry-run preview against the target tool to see exactly what will be deleted, then provide explicit confirmation to execute deletions through the prune flow.

Yes, you can preview deletions before pruning Pixie artefacts by running a dry-run, which shows exactly what would be removed while respecting per-tool retention settings and preserving starred or labelled runs.

Yes, pruning outdated Pixie runs respects starred or labelled items by preserving them during the deletion process, ensuring only artefacts exceeding per-tool retention caps are removed.

The best way to apply per-tool retention policies to stale Pixie artefacts is using a controlled deletion flow that operates across tools or a single tool, reclaiming disk space while providing safety checks and status reporting.

When deleting entire Pixie tools or archives, the system triggers safety warnings and may switch to safer maintenance actions, requiring explicit confirmation before proceeding with any destructive pruning operations.

You reclaim disk space from outdated Pixie runs by applying per-tool retention policies that identify and prune stale artefacts while preserving active, starred, or labelled items through safety checks.