Create your account

Use case · By risk

Review the change before the deploy

For engineers responsible for production releases.

The code is ready, but the deployment plan, test results and rollback instructions are in different conversations. Put the deployment in a Work task. Assign an owner, name the next action and add evidence links in the comments.

Create your accountWatch Security run →

Production changes

Review the production deployment

Example content

  1. Next action

    Confirm the rollback procedure

  2. Context

    Target environment and change

  3. Evidence

    Test results and rollback instructions

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.

  • A task does not block a deploy. Keep deployment permissions and required approvals in your delivery system.
  • 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 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.By clientCodexSetup requirements for Codex.
All use cases →