Improve Message Filtering and Avatar DisplayPublic

Short answer: no, not currently.

• In the merged message-rendering work, agent-context detection in frontend/lib/message-transforms.ts only recognizes patterns like <command-*>, <teammate-messages>, <environment_context>, <skill_content>, and <available_skills>.
• Tags like <local-command-caveat> and <local-command-stdout> do not match those patterns, so frontend/lib/message-utils.ts falls back to user_message.
• The Claude adapter also passes user text through as-is in cli/src/adapters/claude-code/v1.ts, so those blocks make it to the frontend unchanged.

If you want, I can patch this so <local-command-*> gets treated as agent_context (and hidden from Highlights like other context messages).

Done — local command wrappers are now treated as agent context, so those caveat/stdout payloads won’t be shown as normal user prompts in Highlights.

• Updated command-context detection in frontend/lib/message-transforms.ts:31 and frontend/lib/message-transforms.ts:37 to recognize both <command-*> and <local-command-*> prefixes.
• Updated command tag parsing in frontend/lib/message-transforms.ts:41 and frontend/lib/message-transforms.ts:130 so <local-command-caveat> / <local-command-stdout> are parsed by the same command-context path.
• Committed and pushed directly to main as requested: ef3f457 (fix(frontend): classify local command caveats as context).

I also attempted to run frontend lint, but bun is not available in this environment (command not found: bun).

Found it 😄

• bun is at /Users/tarunsachdeva/.bun/bin/bun (version 1.3.8)
• bunx is at /Users/tarunsachdeva/.bun/bin/bunx
• The earlier failure happened because this shell didn’t have ~/.bun/bin in PATH.

I also reran lint with the explicit binary:

• "$HOME/.bun/bin/bun" run lint in frontend/
• Result: 0 errors, 4 warnings (unrelated existing warnings)

I’ve also set PATH in this shell session now, so subsequent commands here can use bun directly.