claude-code - 💡(How to fix) Fix Feature request: Include parent sub-agent context in hook stdin [1 comments, 2 participants]

TL;DR

Modify the PreToolUse hook to include the parent sub-agent's context, such as tool_call_id, to attribute tool calls from background sub-agents to their parent.

Guidance

• Identify the source of the tool_call_id or equivalent identifier for the parent sub-agent and ensure it is accessible when the PreToolUse hook is fired.
• Update the hook stdin to include the parent_tool_call_id field, as shown in the requested behavior example.
• Verify that the updated hook correctly attributes tool calls to the parent sub-agent by testing with multiple concurrent background sub-agents.
• Consider extending this attribution to the PostToolUse hook for comprehensive tracking of sub-agent activity.

Example

No explicit code changes are implied in the issue, but the modification might involve updating the hook stdin construction to include the parent_tool_call_id field, similar to the requested behavior example:

{
  "tool_name": "Grep",
  "tool_input": { "pattern": "..." },
  "parent_tool_call_id": "toolu_01G4DRTnHw4vqwHcSddaHn4u"
}

Notes

The exact implementation details depend on the internal workings of the Agent tool and the hook system, which are not fully described in the issue.

Recommendation

Apply a workaround by modifying the PreToolUse hook to include the parent sub-agent's context, as this directly addresses the requested behavior and provides a clear path to attributing tool calls to their parent sub-agents.