Built with Astro, hosted on Cloudflare. Domain registered in 2026.
claudelogs.com is built with Astro, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| 7.0.7 | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 9 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 9 Nov 2026 | |
| Accessibility1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
dave.ns.cloudflare.comtori.ns.cloudflare.comv=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;User-agent: * Allow: / User-agent: GPTBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: Google-Extended Allow: / User-agent: PerplexityBot Allow: / User-agent: ClaudeBot Allow: / User-agent: anthropic-ai Allow: / User-agent: Applebot-Extended Allow: / # Structured facts for language models (https://llmstxt.org) Allow: /llms.txt Allow: /llms-full.txt Sitemap: https://claudelogs.com/sitemap.xml
# Claude Logs > To review what Claude Code did, read the session JSONL under ~/.claude/projects/ in order: tool results are evidence, assistant text is a claim. The Black Box is a labeled synthetic specimen for forensic session review, not a Claude Code terminal tutorial (see claudeshipscode.com). Claude Logs is an independent educational publication and is not affiliated with Anthropic. Current as of 2026-09-20. Generally available models recorded in transcripts: Claude Fable 5.1 (claude-fable-5-1), Claude Opus 5 (claude-opus-5), Claude Sonnet 5 (claude-sonnet-5), Claude Haiku 4.5 (claude-haiku-4-5). Legacy Fable 5, Opus 4.x, and Sonnet 4.x identifiers still appear in older transcripts. How do I review what Claude Code did in a session? Read the session JSONL transcript under ~/.claude/projects/ in order, and sort every record into one of two kinds. Tool results, exit codes, and durations are evidence of what happened. Assistant text and thinking blocks are claims about what happened. Test every sentence that describes the environment, such as an offline sandbox, against a logged tool call. Scan tool inputs for credentials, because anything passed to a tool is written into the transcript. Then reconcile the final message with git diff, test counts, and CI output. Where the summary and the tool result disagree, the tool result wins. ## Signature - https://claudelogs.com/black-box/ - The Black Box: a labeled synthetic Claude Code JSONL session played record by record, with a redaction overlay, a containment readout, five recovered findings, and a downloadable specimen. Synthetic and authored by Claude Logs; no real transcript is published. Forensic review of what already ran, not a Claude Code terminal or CI tutorial. Primary pages: - https://claudelogs.com/tools - Free browser-only tools for Claude Code transcripts, token usage, and run audits. - https://claudelogs.com/tools/log-viewer - Local JSONL transcript viewer for readable timelines, tool calls, and usage fields. - https://claudelogs.com/tools/token-analyzer - Local token usage and cost estimator with a dated Claude pricing table. - https://claudelogs.com/tools/audit-checklist - Agent run audit checklist with exportable Markdown review notes. - https://claudelogs.com/session-logs - What Claude session logs are, what they contain, and what they do not prove. - https://claudelogs.com/transcript-anatomy - How to read JSONL transcripts, hook transcript paths, subagent paths, and stream-json output. - https://claudelogs.com/observability - Claude Code and Agent SDK observability with OpenTelemetry. - https://claudelogs.com/hook-audit-trails - Hook lifecycle events as audit capture points. - https://claudelogs.com/session-storage-retention - Local JSONL storage, SessionStore mirroring, retention, and deletion boundaries. - https://claudelogs.com/privacy-redaction - Redaction guidance before sharing transcripts, telemetry, hook logs, screenshots, or summaries. - https://claudelogs.com/incident-review-playbook - Review path for failed, stalled, expensive, surprising, or security-sensitive agent sessions. - https://claudelogs.com/containment-evidence - Why agent containment must be proven from logs, and what evidence a sandbox boundary should produce. - https://claudelogs.com/dashboards - Dashboard and alert ideas for Claude agent work. - https://claudelogs.com/updates - Weekly-extensible freshness register for Claude logging and observability changes. - https://claudelogs.com/token-usage - How to interpret Claude Code transcript token fields and estimate costs safely. - https://claudelogs.com/sources - Annotated primary-source bibliography. Source policy: product-behavior claims cite Anthropic documentation or the official Claude Code changelog. General log-management claims cite OpenTelemetry, NIST, or OWASP guidance. Full crawler file: https://claudelogs.com/llms-full.txt