Skip to main content
OpenAI Euphony visualization tool interface, displaying Harmony chat and Codex log data with interactive graphs.

Editorial illustration for OpenAI releases Euphony, a tool to visualize Harmony chats and Codex logs

OpenAI Launches Euphony: Chat Log Visualization Tool

OpenAI releases Euphony, a tool to visualize Harmony chats and Codex logs

Updated: 3 min read

The raw logs of an AI conversation are a mess. Not illegible, exactly, but dense, noisy, and full of structural noise that buries the signal. OpenAI’s answer is Euphony: a browser-based tool that transforms those tangled Harmony JSON and Codex session files into clean, browseable timelines.

No custom parsers. No command-line gymnastics. Just drag in a file, and the structure emerges, role, recipient, content type, timestamps, all laid out for inspection.

Euphony auto-detects four common data shapes, from conversation lists to nested fields to arbitrary JSON fallbacks. It ships with JMESPath filtering, focus modes, metadata inspection, grid view, even an in-browser JSONL editor. You can run it as a static frontend or with a local FastAPI backend for remote loading, though OpenAI warns against exposing that backend to the internet (SSRF risk is real).

And because it’s built as reusable Web Components, you can drop into React, Svelte, Vue, or plain HTML, customize the look with CSS variables, and keep everything under Apache 2.0. Euphony doesn’t just make logs readable. It makes them useful.

OpenAI team is taking a direct swing at that problem with the release of Euphony, a new open-source browser-based visualization tool designed to turn structured chat data and Codex session logs into readable, interactive conversation views.

Euphony doesn’t just solve a debugging problem , it rewrites the terms of engagement with AI data. By handing developers a browser-ready, embeddable, fully inspectable lens into Harmony and Codex internals, OpenAI signals a shift toward operational transparency. No more blind trust in black-box outputs.

No more glue code for log parsing. The tool’s design , from its auto-detection modes to its Web Component architecture , makes deep inspection a casual act, not a week-long project. This matters because as language models weave themselves into production pipelines, the ability to trace, filter, and validate every turn of a conversation becomes a non-negotiable practice.

Euphony is the bones of that practice, open-sourced and ready to drop into any stack. The question is no longer whether you can see what the model is doing, but how quickly you can act on what you see.

Common Questions Answered

What problem does OpenAI's Euphony tool solve for developers working with Harmony and Codex logs?

Euphony addresses the challenge of parsing complex JSON and JSONL files from AI conversations and code generation sessions by providing a browser-based visualization tool. Instead of manually writing custom log parsers, developers can now easily browse structured conversation timelines and understand the context of AI interactions.

How many auto-detection modes does Euphony support for processing different log formats?

Euphony supports four auto-detection modes that can recognize various log structures, including lists of Harmony conversations, Codex session files, conversations nested under top-level fields, and a fallback mode for rendering arbitrary data as raw JSON objects. This flexibility allows the tool to handle diverse log formats without requiring manual configuration.

Why is visualizing AI agent interactions more challenging compared to traditional debugging?

Unlike traditional software debugging with clear stack traces, AI agent interactions involve complex, multi-step processes that generate hundreds of lines of raw JSON. Developers often struggle to piece together the model's reasoning and decision-making at each step, which is why tools like Euphony are crucial for understanding AI conversation flows.

LIVE06:13Gemini 3.6 Flash Boosts Coding and Token Efficiency