|
|
@@ -278,6 +278,29 @@ TASK SETTINGS
|
|
|
|
|
|
mode Starting mode (act/plan)
|
|
|
|
|
|
+ hooks_enabled
|
|
|
+ Enable or disable hooks for the task (true/false)
|
|
|
+
|
|
|
+HOOKS INTEGRATION
|
|
|
+ Hooks let you inject custom logic into Cline's workflow at key moments.
|
|
|
+ They can validate operations before they execute, monitor tool usage,
|
|
|
+ and shape AI decisions. This allows you to integrate hooks into
|
|
|
+ automated workflows, CI/CD pipelines, and headless task execution.
|
|
|
+
|
|
|
+ Enable hooks for a task:
|
|
|
+
|
|
|
+ cline "prompt" -s hooks_enabled=true
|
|
|
+
|
|
|
+ Configure hooks globally:
|
|
|
+
|
|
|
+ cline config set hooks-enabled=true
|
|
|
+ cline config get hooks-enabled
|
|
|
+
|
|
|
+ Note: Hooks in the CLI are only supported on macOS and Linux.
|
|
|
+
|
|
|
+ For complete hooks documentation, see:
|
|
|
+ <https://docs.cline.bot/features/hooks/index>
|
|
|
+
|
|
|
NOTES & EXAMPLES
|
|
|
The cline task send and cline task new commands support reading from
|
|
|
stdin, enabling powerful pipeline compositions:
|