feat: hook receiver as a configurable automation bus #65
Labels
No labels
backend
bug
chore
duplication
effort:complex
effort:medium
effort:trivial
enhancement
frontend
fullstack
priority:high
ready-for-agent
refactor
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
dries/ocman#65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From spec/multi-agent-support/agent-feature-survey.md — finding #13.
What it is
Pre/post tool hooks, session lifecycle hooks (
SubagentStart,SubagentStop,Stop, etc.) that fire shell scripts with a JSON payload on stdin.Seen in
Claude Code; Codex; OpenCode itself.
ocman angle
ocman already has a hook receiver endpoint that OpenCode (and any future platform) can POST to. Today it's a sink. We could turn it into an automation pipeline: per-project rules ("on session end, send a webhook"; "on file edited in
prod/, post to Slack"; "on tool error, capture a trace"). A small rule engine in the backend, a rule editor in the UI.Effort
M.