Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.235 Home All releases ←olderv2.1.234 v2.1.236newer→
Claude Code v2.1.235

MCP tool permission prompts show parameters as a readable table

You'll notice
Useful4 Signal1
MCP

MCP permission prompts now show parameters as a readable table with links and real dates.

What

When an MCP tool asks for permission, its parameters are now laid out as key/value entries rather than raw JSON, with syntax-highlighted code, clickable http(s) links and epoch timestamps rendered as readable dates.

Details
  • A code parameter is highlighted when a sibling language parameter is a short string. Highlighting is skipped for values over 50000 characters.
  • Timestamps are annotated when the tool's JSON Schema declares format: date-time, or for Slack-style ts / thread_ts epoch strings.
  • Rendering is bounded: 80 columns for the inline layout, 200000 code units per key or value, and 64 levels of nesting before the value is reported as exceeding the display depth bound. Larger structures fall back to a bordered block.
Evidence

value exceeds the display depth bound

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.235 →