pub fn session_panes() -> HashMap<String, String>Expand description
The machine daemon pane each Codex conversation runs in, by session id. The pane the daemon names
in the environment it gives every pane (SUPERCODE_TEAMS_PANE), read from the codex process
that holds the conversation’s rollout, is only a candidate: a process inherits that variable
from whatever ran it, so a headless codex exec a Claude pane’s tool started carries the Claude
pane’s name, and its mail was typed into Claude’s composer (twins’ m-72bc65eb). A Codex holds a
pane only as that pane’s own program: the pane’s root process by the daemon’s record, or a
descendant of the root reached only through Codex launchers (npm’s codex.js runs the native
codex beneath it, and the daemon’s Codex pane host runs that beneath itself: yuerans-macbook-pro’s
node native-codex-pane.mjs → node codex.js → codex, 2026-10-03), when the root is itself a Codex
launcher or the daemon launched the pane as Codex. A root that is Claude does not lend its pane to the codex exec a
tool of it runs: the tool’s shell is no launcher, and the daemon launched that pane as Claude.
A conversation outside any daemon pane (or held only by the shared app-server) has none.