{"name":"clientRequestId","slug":"clientrequestid","family":"setting","title":"Settings keys","noun":"settings key","description":"API success telemetry now records time-to-first-content, a client request id, and the user message's UUID","description_source":"entry","described_by":{"version":"2.1.268","anchor":"tengu-api-success-gains-firstcontentms-clientrequestid-use"},"presence":{"first_seen":null,"removed_in":null,"in_current_build":false,"newest_mined":"2.1.322","builds":0,"mined_builds":161,"first_cited":{"version":"2.1.113","released_at":"2026-04-17 19:09:22","spans":2}},"aliases":[],"entries":[{"version":"2.1.268","anchor":"tengu-api-success-gains-firstcontentms-clientrequestid-use","heading":"tengu_api_success gains firstContentMs, clientRequestId, user_message_uuid","line":"API success telemetry now records time-to-first-content, a client request id, and the user message's UUID","released_at":"2026-09-10 18:41:11","reason":"found in this entry's text"},{"version":"2.1.268","anchor":"api-dispatch-requests-now-carry-a-per-attempt-client-request","heading":"API dispatch requests now carry a per-attempt client request ID and richer retry telemetry","line":"API requests now carry a per-attempt request ID and log more detail about retries","released_at":"2026-09-10 18:41:11","reason":"found in this entry's text"},{"version":"2.1.113","anchor":"telemetry-request-id-tracking","heading":"Telemetry Request ID Tracking","line":null,"released_at":"2026-04-17 19:09:22","reason":"found in this entry's text"}],"entries_total":3,"docs":[],"docs_total":0,"gates":[],"related":[],"url":"https:\/\/changelogs.core-directive.com\/reference\/setting\/clientrequestid","family_url":"https:\/\/changelogs.core-directive.com\/reference\/setting.json"}