Know where the storage went, and clean it safely
DiskKind shows where each Mac's storage went and what is safe to remove. An AI can look and suggest; removing anything waits for the Mac's owner.
Free to look; Pro $29 once. Its own account, its own site.
- Maya's MacBook96% full
- Dev's MacBook71% full
- Studio iMac48% full
- Storage across the office's Macs
- What was cleaned, with its receipt
Works with the assistants your team already uses
ChatGPT
GeminiCopilot
Cursor
Slack
Notion
From request to recorded action
One move in DiskKind, from the AI that asked to the line on the record.
- Step 1 of 4
The request
Anyone on the team asks the AI they already use, in the place they already work. Here, Dev asks through Copilot.
CopilotDev
Which Macs in the office are nearly full?
I'll ask DiskKind. Checking your limits for Dev first.
Limits that apply- Reading storage: allowed
- Removing files waits for the owner
- Step 2 of 4
What DiskKind does
The product does its own job, the way it always does. The AI only asks it, and reads the answer.
DiskKindThe office's Macs- Maya's MacBook96% full
- Dev's MacBook71% full
- Studio iMac48% full
41 GB of caches safe to remove - Step 3 of 4
The clearance
Every move is checked against the limits set for that person and that AI. Inside them it runs; past them it waits for whoever owns the decision.
InsightronClearance
- Reading storage: allowedCleared
- Removing files waits for the ownerHeld
YOUAnything past a limit comes to the person who owns it, with Approve, Redirect and Take over. - Step 4 of 4
The record
Auditant seals the move: who asked, through which AI, what changed and who cleared it. Undo is offered wherever it can honestly be done.
AuditantSealed
- Who
- Dev
- Through
- Copilot
- Product
- DiskKind
- Change
- suggested, nothing removed
- Cleared
- Inside the limits
- Entry
- #88
- Seal
- 7f3a…c91e, chained
Anyone can check the chain offline
From request to recorded action
One move in DiskKind, from the AI that asked to the line on the record.
Which Macs in the office are nearly full?
I'll ask DiskKind. Checking your limits for Dev first.
- Reading storage: allowed
- Removing files waits for the owner
- Maya's MacBook96% full
- Dev's MacBook71% full
- Studio iMac48% full
- Reading storage: allowedCleared
- Removing files waits for the ownerHeld
- Who
- Dev
- Through
- Copilot
- Product
- DiskKind
- Change
- suggested, nothing removed
- Cleared
- Inside the limits
- Entry
- #88
- Seal
- 7f3a…c91e, chained
- Step 1 of 4
The request
Anyone on the team asks the AI they already use, in the place they already work. Here, Dev asks through Copilot.
- Step 2 of 4
What DiskKind does
The product does its own job, the way it always does. The AI only asks it, and reads the answer.
- Step 3 of 4
The clearance
Every move is checked against the limits set for that person and that AI. Inside them it runs; past them it waits for whoever owns the decision.
- Step 4 of 4
The record
Auditant seals the move: who asked, through which AI, what changed and who cleared it. Undo is offered wherever it can honestly be done.