Skip to content

Feature request: support viewing Claude Code session logs #7

@ddhjy

Description

@ddhjy

Summary

Euphony currently supports Harmony conversations and Codex session JSONL files, but it does not appear to support Claude Code session logs yet.

From the current codebase and README:

  • The README advertises Harmony and Codex session viewing.
  • Session detection is wired through a Codex-specific parser.
  • The parser recognizes Codex event shapes such as session_meta, response_item, event_msg, and turn_context.

Because of that, Claude Code session files seem likely to fall back to raw JSON rendering instead of the structured session timeline that Codex logs get.

Request

Please consider adding support for Claude Code session display, ideally with the same kind of structured timeline / conversation view that Codex sessions already have.

Why this would help

  • Many people compare or debug workflows across multiple coding agents, not just Codex.
  • Euphony already has a nice session-viewing UX, so extending that to Claude Code would make it more broadly useful.
  • Even a basic first pass (messages, tool calls, tool outputs, timestamps) would already be very valuable.

Possible implementation direction

  • Add a Claude Code session detector alongside the existing Codex detector.
  • Normalize Claude Code events into the same internal conversation/message model used by the existing viewer.
  • If possible, keep the session adapter layer generic so future agent/session formats can plug in more easily.

If helpful, I can also provide a sample Claude Code session file format for testing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions