Free tools

AI agent notification hook

Generate the hook file for Claude Code, Codex CLI, or Cursor so you get a push when the agent finishes. Free, in your browser, no signup.

Events

Hook config

 
Script
 
 
     
        
     
     
      
    Runs in your browser. Nothing you enter is stored.
     
     
      
     
    Get the key, then let the hook call it
     
    The script uses TRIGV_API_KEY. Create the key, export it, and run one task before you rely on the hook.
     
    curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"agents","title":"Claude finished","level":"success"}'
     
     
     Get an API key AI agents guide 
     
     
     
    How to use it
     
       
    1. Pick the agent. The hook format matches the Trigv guide for that tool.
    2. Choose the events and the title. {agent} and {project} are filled in by the script when the tool provides a project path.
    3. Copy the settings snippet and download the script. Export TRIGV_API_KEY before you test.
    4. Follow the install steps under the output. Keys stay in the environment, not in the hook file.
      5.  
     
     
     
    About this tool
     
    Claude Code, OpenAI Codex CLI, and Cursor can run a command when an agent stops or when it needs input. That command is a hook. Trigv’s guides already use those hooks to post one event to your phone. This page fills in the same files with your channel, title, and level.
    Claude Code reads ~/.claude/settings.json. The Stop hook runs when a turn finishes. The Notification hook in the guide listens for permission_prompt and idle_prompt. Codex uses ~/.codex/config.toml with hooks enabled and a Stop hook. Cursor uses .cursor/hooks.json with version 1 and a stop command. Those shapes are the ones documented in the Trigv guides.
    The script posts to https://api.trigv.com/v1/events with the key from TRIGV_API_KEY. It does not print the key and it does not ask you to paste one here. On macOS and Linux the script is bash and uses jq. On Windows it is PowerShell. If the agent has no hook file, the Other option is a wrapper that runs your command and then notifies.
    Hook formats change. If a tool updates its settings file, follow the linked guide and the vendor’s docs. The request body stays the same: channel, title, and an optional level of info, success, warning, or error.
     
     
     
    Questions
     
     
     
      Which hook events are these? 
     
    Claude Code uses Stop and Notification as in the Trigv Claude Code guide. Cursor uses the stop hook in .cursor/hooks.json. Codex uses the Stop hook in config.toml.
     
     
      Why is the project name missing? 
     
    Turn on “Include project folder name.” The script reads the JSON the agent passes on stdin and uses the folder name. If you turn it off, the title is used as you typed it.
     
     
      Can I commit the hook? 
     
    You can commit the settings file and the script. Do not commit TRIGV_API_KEY. Each person exports their own key.
     
     
      What if my agent is not listed? 
     
    Choose Other. You get a wrapper that runs the command and then sends the Trigv event. That matches the pattern in the other-agents guide.
     
     
     
     
      
        Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.     Cron Expression Generator Build a schedule or paste one and read the next run times.     HTTP Status Codes Look up what a status code means and whether you should alert on it.