Claude Code and Codex

Which worktree an agent is working in, what it is doing, and how to get to its session from the sidebar.

Claude Code and Codex each work in worktrees of their own: Claude Code in .claude/worktrees inside the repository, Codex in a folder of its own, on a detached HEAD. Innesta lists them with the rest, and puts the agent’s avatar on the row — see the figure in Worktrees.

It recognises them from what the agents leave behind, without running anything: a Claude Code worktree by its folder and its worktree-‹name› branch, a Codex one by the conversation Codex records for it. No plugin is needed in either.

Where an avatar takes you

Click the avatar for the agent’s session in that worktree. The button names where it goes, and goes exactly there:

  • Claude Code in Terminal, iTerm or Ghostty 1.4 — its tab, window or split.
  • Claude Code in Claude or Visual Studio Code — the session in that app.
  • A Claude Code session that has stopped — resumed in a terminal, or in Claude.
  • A Codex conversation — in ChatGPT, or resumed in a terminal.

When a place cannot be selected, the menu says why and offers Copy Resume Command.

The row’s menu has an Agents submenu: Open in Claude Code and Open in Codex start a new session in that worktree, Show Codex Thread opens the conversation Codex associated with it, and Copy Claude Code Resume Command and Copy Codex Resume Command copy the command to continue in a terminal of your own.

The agent’s app or a terminal

With both installed, opening an agent asks each time whether to use its app or a terminal, until you tell the alert not to ask again. Innesta ▸ Settings… (⌘,) → AI → Coding Agents changes the answer and chooses which terminal Innesta uses.

Live status

Show live agent status, in the same settings, shows on each avatar whether its session is working, waiting for you or idle. It is off until you switch it on, in the Direct build only. It reads the agents’ own local session metadata — folder, name and state — and sends nothing, starts nothing, and reads no conversation. Innesta reads it only while the Worktrees section or a worktree’s review is in use.

An agent seen working or waiting keeps its worktree from being updated from its base, finished, cleaned up or removed, and the reason says so. It is also what lets Send to Agent… list the sessions that can take your notes.

A worktree inside the repository

Claude Code’s worktrees are inside the repository, where Git would otherwise list each one as an untracked folder, and git add -A would record it as an embedded repository. Innesta leaves them out of the Working Copy and out of staging, and a row that Git does not ignore is marked, with Add to .git/info/exclude in its menu to ignore the whole .claude/worktrees folder in every worktree, without touching a tracked file.