claude-code - 💡(How to fix) Fix Add displayContext hook field for human-visible, agent-hidden output [1 comments, 2 participants]

TL;DR

To address the issue of hooks not being able to display output to humans without adding it to the agent's context, introduce a displayContext field that allows hooks to render output in the terminal without including it in the agent's context.

Guidance

• Introduce a new field displayContext in the hook output to separate output intended for human visibility from that intended for the agent's context.
• Update the rendering logic to display displayContext in the terminal while excluding it from the agent's context.
• Modify existing hooks, such as the PostToolUse hook, to utilize displayContext for surfacing summaries or results to humans, as shown in the proposed example.
• Ensure that the agent's context only includes additionalContext and not displayContext to avoid unnecessary data inclusion.

Example

The provided Bash script example demonstrates how a PostToolUse hook can use displayContext to surface a test summary to the human:

jq -n --arg ctx "$SUMMARY" '{"displayContext": $ctx}'

This example assumes that the SUMMARY variable contains the desired output to be displayed to the human.

Notes

The introduction of displayContext requires updates to both the hook logic and the rendering of output in the terminal. This solution assumes that the underlying infrastructure supports the differentiation between additionalContext and displayContext.

Recommendation

Apply the workaround by introducing the displayContext field and updating hooks to utilize it, as this directly addresses the issue of separating human-visible output from the agent's context.