Roo Code Hooks

[wheelo]

I would like to propose a Roo Code Hooks system similar to Cline Hooks. This feature would allow developers to use custom scripts to observe, control, and extend the agent loop. Hooks can run before or after specific stages in the agent lifecycle, enabling actions like:

• Running code formatters after edits
• Adding analytics or event tracking
• Scanning for PII or sensitive information
• Limiting high-risk operations (e.g., SQL writes)

---

Motivation

Hooks provide developers with a flexible mechanism to intercept, observe, and modify agent behavior. This is especially useful for:

• Enforcing project-specific coding standards
• Integrating with external tools (linters, CI/CD, notifications)
• Security and compliance checks
• Contextual learning and guidance for the agent

By implementing hooks, Roo Code can become more extensible and customizable for both individual developers and teams.

---

How to Use

1. Hooks Directory:

   mkdir -p .roo/hooks
   cd .roo/hooks

2. Example: TaskStart Hook

   cat > TaskStart << 'EOF'
   #!/usr/bin/env bash
   
   # Read JSON input
   input=$(cat)
   
   # Extract task metadata
   task_id=$(echo "$input" | jq -r '.taskId')
   initial_task=$(echo "$input" | jq -r '.taskStart.taskMetadata.initialTask')
   
   # Log for demonstration
   echo "[$(date)] Task Started: $task_id" >> ~/roo-hooks.log
   echo "Initial request: $initial_task" >> ~/roo-hooks.log
   
   # Return success (non-blocking)
   echo '{
     "cancel": false,
     "contextModification": ""
   }'
   EOF
   
   chmod +x TaskStart

3. Testing Hook

   echo '{"taskId":"test-123","taskStart":{"taskMetadata":{"initialTask":"Create a hello world app"}}}' | ./TaskStart

4. Execution Model: Hooks should accept JSON input via stdin and return JSON via stdout. This allows Roo Code to:

   • Block operations ("cancel": true)
   • Inject or modify context ("contextModification": "...")
   • Log or observe events without blocking

5. Hook Types (similar to Cline Hooks)

   • TaskStart — Initialize tasks
   • PreToolUse — Validate or block operations
   • PostToolUse — Learn or modify context after execution
   • TaskCancel — Cleanup

This setup provides a flexible and modular hook system. For advanced scenarios, hooks can run external scripts or connect to APIs, allowing Roo Code to integrate with CI/CD pipelines, security audits, or analytics systems.

References

• Cline Hooks Implementation

[cybairfly]

Related:
#8665