Text-only replies had a bare <sub> footer while tool-using runs had a <details> dropdown. Now every comment gets the same collapsed dropdown: summary 🔧 N tool calls · in X · out Y · cost, body = tool list (or a no-tools note) + full token breakdown.
Text-only replies had a bare `<sub>` footer while tool-using runs had a `<details>` dropdown. Now every comment gets the same collapsed dropdown: summary `🔧 N tool calls · in X · out Y · cost`, body = tool list (or a no-tools note) + full token breakdown.
Comments looked different depending on the run: tool-using agents got a
collapsed <details> report while text-only replies got a bare one-line <sub>
footer. Every comment now gets the SAME dropdown — summary '🔧 N tool calls ·
in X · out Y · <cost>', body = the tool list (or '(no tool calls)') plus the
full token/cost breakdown.
Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Text-only replies had a bare
<sub>footer while tool-using runs had a<details>dropdown. Now every comment gets the same collapsed dropdown: summary🔧 N tool calls · in X · out Y · cost, body = tool list (or a no-tools note) + full token breakdown.