Create your account

Use case · By risk

Make a deletion request specific

For engineers cleaning up files, databases or old environments.

“Clean up the old build” leaves the target and recovery plan unstated. The person reviewing it needs both. Use a Work task to name the exact target, assign the cleanup owner and record the next check. Add evidence of the backup or recovery procedure before the work starts.

Create your accountWatch Security run →

Destructive operations

Review the old environment cleanup

Example content

  1. Next action

    Verify the target and recovery procedure

  2. Context

    Exact cleanup target

  3. Evidence

    Backup or recovery evidence

What to put in the task

  • Assign the task to the person responsible for the next action.
  • Add evidence links and explain what they show in a comment.
  • Update the task when the work changes so the next reader has the current state.

Before you rely on it

Command interception depends on your client's hooks or proxy; see the setup guide for Claude Code, Codex, Cursor and other MCP clients.

  • Recording a task does not stop a shell command or database operation. Access controls and recovery checks still belong in the system being changed.
  • Work must be enabled for the selected account, and you need permission to read or change the task. Security access and device setup are separate.

Related use cases and clients

By riskProtected branchesA maintainer can follow the request from its reason to the review without reconstructing it from terminal messages.By riskSecrets and env filesThe next person can see which configuration changed and who handled it without asking for the secret in chat.By clientClaude CodeSetup requirements for Claude Code.
All use cases →