LlamaTreeClaude Code and Codex
A session's command decides what it runs: claude for Claude Code, codex for the Codex CLI (each with any options you add), or anything else, such as a shell or a dev server. They can sit side by side, in the same project or even the same folder.
What each gets
| Claude Code | Codex | Any other command | |
|---|---|---|---|
| Tiles, tabs, projects, shortcuts | ✓ | ✓ | ✓ |
| Working, waiting, idle dots | ✓ | ✓ | ✓ |
| Needs your answer dot | ✓ | ✓ | with OSC 7501 |
| A conversation of its own, reopened after restarts | ✓ | ✓ | – |
Follows /clear, /resume, /new | ✓ | ✓ | – |
| Resume picker | ✓ | ✓ | – |
| Conversation rail and tab | ✓ | ✓ | – |
| Panels and messages | ✓ | ✓ | – |
| Started in matching light or dark colours | ✓ | not yet | – |
| Git panel, diffs, Project view | ✓ | ✓ | ✓ |
| Suggest commit messages | ✓ Claude Code | ✓ Codex | ✓ Claude Code, if installed |
Claude Code
Each Claude session is started with:
--session-idor--resume, so it keeps its own conversation;--mcp-configpointing at LlamaTree's MCP server for panels and messages (your own MCP servers still load; a command that passes its own--mcp-configis left alone);--settingswith the app's light or dark theme, since Claude can't detect the terminal's colours on Windows (left alone if you pass your own).
The conversation rail and tab read Claude's saved transcript, so they work in Claude's full-screen mode too.
Codex
- Its own conversation. Codex can't be told which id to use, so a new session learns its conversation once Codex has saved it, then reopens it with
codex resume <id>. - Following you. After
/newthe session moves to the new conversation. After/resumeit moves once you send a prompt there. - Saved conversations are read from
~/.codex/sessions, orCODEX_HOME. - Panels and messages: the MCP server is added on Codex's command line, with the session's token in an environment variable rather than on the command line.
codex resume …,codex fork …and Codex's other subcommands run as they are.
Other agents: the needs your answer dot
Any program can report that it's blocked on you by writing an OSC 7501 sequence with state=blocked to the terminal, which is how Codex does it. LlamaTree shows the pink dot for it, without reading the screen.