claude-code - 💡(How to fix) Fix [FEATURE] Allow additionalContext to specify a /context category [1 participants]

TL;DR

Adding an optional category field to additionalContext entries may help distinguish hook-injected context from actual conversation in the /context display.

Guidance

• Introduce a new field, additionalContextCategory, to categorize additionalContext entries, allowing for separate display in /context.
• Ensure message normalization preserves the category field when flattening hook attachments into plain user messages.
• Update the /context display logic to show categorized additionalContext entries separately from the "Messages" bucket.
• Consider the potential impact on existing conversation handling and context management systems.

Example

{
  "additionalContext": ["...policy text..."],
  "additionalContextCategory": "Hook: coding-policy"
}

Notes

This solution assumes that the proposed category field can be successfully integrated into the existing message normalization and /context display logic.

Recommendation

Apply workaround: Introduce the additionalContextCategory field to provide a clear distinction between hook-injected context and actual conversation, as this is a narrower and more targeted solution compared to a full context management system.