docs(hooks): document plugin hook names and clarify naming#12819
docs(hooks): document plugin hook names and clarify naming#12819JBrady wants to merge 1 commit intoopenclaw:mainfrom
Conversation
|
Greptile encountered an error while reviewing this PR. Please reach out to [email protected] for assistance. |
|
Thanks for the review. It looks like this PR is currently blocked by an unrelated Windows test failure in CI, not by the docs changes in this branch. Failing job: The failures in that job are in I’m happy to re-run checks and keep this updated, and I can also rebase once the Windows test issue is resolved upstream. |
a05ff9d to
658ec07
Compare
|
Quick follow-up: I refreshed this branch onto the latest Current run is now on the docs-only path ( |
bfc1ccb to
f92900f
Compare
|
This pull request has been automatically marked as stale due to inactivity. |
|
This pull request has been automatically marked as stale due to inactivity. |
|
Closing due to inactivity. |
Summary
Documents currently implemented plugin hook names and clarifies internal-hook vs plugin-hook naming to prevent confusion.
What changed
Updated
docs/tools/plugin.md(Plugin hookssection):before_agent_start,agent_endmessage_received,message_sending,message_sentbefore_tool_call,after_tool_callsession_start,session_endmessage_received, notmessage:received).Updated
docs/automation/hooks.md:Future EventstoFuture Events (internal hooks)type:actionnames belong to internal hooks/tools/plugin#plugin-hooksWhy
Issue #12436 reports confusion where plugin hooks appeared undocumented and
message:receivedlooked like a future-only event. The actual confusion is between two hook systems with different naming conventions (internaltype:actionvs plugin underscore names). This PR documents the available plugin hooks and disambiguates naming.Closes #12436
Contributing checklist
openai-codex/gpt-5.3-codex)