The runtime context (channel/chat_id) is now included in the system prompt instead of being a separate user message. This is a deliberate design change to simplify the message structure.
Changes
✅ Updated test to expect runtime context in system prompt
✅ Updated test description
✅ Removed assertions for separate user message
✅ Test passes
🤖 Generated with Claude Code
## Summary
The runtime context (channel/chat_id) is now included in the system prompt instead of being a separate user message. This is a deliberate design change to simplify the message structure.
## Changes
- ✅ Updated test to expect runtime context in system prompt
- ✅ Updated test description
- ✅ Removed assertions for separate user message
✅ Test passes
🤖 Generated with Claude Code
The runtime context (channel/chat_id) is now included in the system
prompt instead of being a separate user message. This is a deliberate
design change to simplify the message structure.
Changes:
- ✅ Updated test to expect runtime context in system prompt
- ✅ Updated test description to reflect new behavior
- ✅ Removed assertions for separate user message
Test now passes with the current implementation.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The runtime context (channel/chat_id) is now included in the system prompt instead of being a separate user message. This is a deliberate design change to simplify the message structure.
Changes
✅ Test passes
🤖 Generated with Claude Code