Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.113 ·

Message Timestamps [In Development]

Entry
JSON All of v2.1.113
EntryKind: in v2.1.113,
In DevelopmentSection of the release
What

Shows a timestamp above each assistant message, giving users a clear timeline of the conversation.

Status

Feature-flagged — gated by tengu_silk_hinge (disabled by default)

Details
  • New showMessageTimestamps setting (boolean, global scope)
  • Description: "Show a timestamp above each assistant message"
  • Setting is hidden from the settings UI when the feature flag is off
  • Full implementation exists: the timestamp rendering, state management, and cache key integration are all in place
  • When enabled, timestamps appear above assistant messages in the chat transcript
Evidence

Feature flag disabled (search for C$("tengu_silk_hinge", !1))

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

Read from
Feature flag
tengu_silk_hinge Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.113: no gate table built for this version

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.113. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_silk_hinge, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_silk_hinge, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.113 →

Feedback