UNQUOTE

Read Codex and Claude Code session logs

Unquote turns recognized Codex rollout and Claude Code transcript JSONL files into readable Agent and Trajectory views. Follow messages, tool calls, results, and session activity alongside the original JSON records. Import a local log to investigate a run without uploading its contents.

Open the free viewer

Open a session log

  1. Choose or drop a local JSONL session file into Unquote.
  2. Let Auto detect the format, or select JSONL to parse the file line by line.
  3. Use Agent for the conversation and Trajectory for activity over time.
  4. Select an event and inspect its linked source record when you need the raw details.

You can start with the built-in Codex rollout sample to explore the views without finding a file first. Session detection depends on recognized record structures; naming a file after an agent does not make an unrelated log compatible.

Choose the view that answers your question

Agent: what did the assistant do?
Read the conversation and inspect tool calls and their results. The view groups supported session events so you can follow the work without reading each JSONL line.
Trajectory: when did the work happen?
Follow timed activity, narrow the range, and filter by event kind, status, or failures. Long idle gaps are compressed in the overview so active periods remain readable.
JSON: what did the log actually contain?
Inspect the original record structure, search nested fields, and check source lines. Use this view when a summary needs context or a record format is not recognized.

Investigate a failed tool call

Find a failure in the Trajectory view, inspect the call and result, then open the linked record. Check the arguments, result, and surrounding conversation before attributing the failure to the agent. A missing result may mean the log is incomplete rather than that the tool never finished.

Unquote surfaces integrity warnings where the log provides incomplete or inconsistent evidence. Invalid JSONL lines remain parse warnings and do not automatically disable an otherwise recognized session. Token usage and other metadata are shown only where the supported records provide them.

Supported logs and privacy

Agent detection supports recognized Codex rollout and Claude Code transcript records in JSONL. Other JSON and JSONL files can still be inspected in the general viewer. A new agent log format may need an updated adapter before a session view becomes available.

Session logs can contain prompts, code, paths, and tool output. File contents stay in your browser. If you need to share a debugging excerpt, use the report tools to select source lines and redact specific paths, then review the exported result.