CommandCodeAI / CommandCodeAI/command-code

Feature: Just 3 Hooks are there Please expand the hooks system to match Claude Code / Codex parity

Đang mở
#463 3 bình luận 0 reaction 1 người được giao Xem trên GitHub

@vipulgupta2048 đang làm issue này rồi.

Từ ngày 30/6/2026.

Ngôn ngữ chính
Không có dữ liệu ngôn ngữ
Star
4k
Fork
350
Chỉ số merge pull request
Không có pull request nào được merge trong 30 ngày

Mô tả

Feature Description

Command Code currently supports only 3 hook events:

  • PreToolUse
  • PostToolUse
  • Stop

This is severely limited compared to Codex and Claude Code, which both expose a much richer hook lifecycle. The gaps prevent meaningful observability, automation, and integration with orchestration tools like herdr, tmux, and cmux.

Missing events (present in Codex):

  • PermissionRequest — intercept before a permission dialog
  • PostCompact / PreCompact — hook around context compaction
  • SessionStart — fire on session begin/resume
  • SubagentStart / SubagentStop — detect when subagents spawn/finish
  • UserPromptSubmit — intercept before Claude processes the prompt

Missing events (present in Claude Code, not even in Codex):

  • Setup — one-time prep on init
  • UserPromptExpansion — before slash command expands to a prompt
  • PermissionDenied — when auto-mode classifier denies a tool call
  • PostToolUseFailure — after a tool call fails (currently only success is hooked)
  • PostToolBatch — after a full parallel tool batch resolves
  • Notification — when the assistant sends a notification
  • MessageDisplay — while assistant message text is being displayed
  • TaskCreated — when a task is created via TaskCreate

Missing tool matcher support:
Command Code's supported tools table (shell, read, write, edit) also lacks matcher support for MCP tools, which both Codex and Claude Code support via mcp__* patterns.

Use Case

Without these hooks, Command Code cannot be properly integrated into multi-agent orchestration setups.

Concrete pain points today:

  1. herdr cannot recognize cmd agents in tmux/cmux sessions because there is no SessionStart or SubagentStart event to listen on — the hooks to signal "an agent started" simply don't exist
  2. No failure visibilityPostToolUseFailure is missing, so failed tool calls are silent
  3. No notification hooks — the Notification event missing means tools like cmux cannot trigger alerts when Command Code finishes a task
  4. No permission interceptionPermissionRequest / PermissionDenied missing means no way to auto-approve or audit permission dialogs programmatically
  5. No subagent lifecycleSubagentStart / SubagentStop missing breaks any workflow that needs to track spawned agents

Codex and Claude Code already solved these. Command Code needs hook parity to be usable in the same workflows.

Additional Context

Reference implementations for all listed events:

Priority order for missing events (highest impact first):

  1. SessionStart — needed for herdr/cmux agent detection
  2. SubagentStart / SubagentStop — needed for multi-agent orchestration
  3. Notification — needed for cmux notification triggers
  4. PostToolUseFailure — needed for error observability
  5. PermissionRequest / PermissionDenied — needed for auto-approval workflows
  6. UserPromptSubmit — needed for prompt interception
  7. PostToolBatch, MessageDisplay, TaskCreated, UserPromptExpansion, Setup — parity completion
Image Image
How important is this to you?

Very important

Hướng dẫn đóng góp

Chưa lập chỉ mục được hướng dẫn đóng góp cho kho mã nguồn này

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Đánh giá

Issue này chưa được đánh giá.

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.