DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to print a session's agent tree without opening the TUI with Zoetrope

Dump the session tree to the terminal headlessly for logs, notes or scripts.

Who it is forAn engineer who wants a plain-text record of which agents a session spawned, to paste into a ticket or check in a script.

The problemOpening an interactive graph is awkward when you only need the structure of a session and want to capture it as text.

The outcomeA printed session tree that shows the main session and its nested agents, with no interactive interface needed.

What you need first

  • Claude Code or Codex sessions already recorded on the machine (files under ~/.claude/projects/ or ~/.codex/sessions/)
  • Homebrew, a Rust toolchain for cargo install, or a prebuilt binary from the releases page
  • A terminal for the zoe TUI, or a browser for the hosted app

Steps

  1. Install Zoetrope with cargo install zoetrope (needs a Rust toolchain) or brew install furkankly/tap/zoetrope.
  2. Run zoe inspect followed by the path to the session file.
  3. Redirect the output to a file, for example with > in your shell, to keep the record.
  4. Check that the printed tree lists the subagents you expect.

Prompt for your agent

In the zoetrope repo (furkankly/zoetrope), run `zoe inspect` on the session file at <session-file-path> and save the output to <output-file>. Expected output: a printed session tree with the main session and its subagents, written without starting the TUI. Verify that the output file is not empty and lists at least the main session before reporting success.

Caveat. zoe inspect only prints the session tree, so per-tool timings and the detail panel are available only in the interactive TUI or the browser app.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page