Probe × cc/cx native integration
Plan for making Claude Code (cc) and Codex (cx) first-class in Probe — titles and working state (shipped 2026-11-04), then agent identity via hooks, native launch/resume, and Cyberdeck/T3 ownership.

Probe × cc/cx native integration

2026-11-04, cc@yacht. Builds on Deck docs/AGENT-COMMUNICATION.md (cx@starlight, 2026-11-03), whose rule this plan keeps: every conversation has exactly one owner. Probe owns a cc/cx conversation when the CLI runs in a Probe PTY; T3, Deck's runner and Seed keep theirs. Probe shows the others and never becomes a second writer.

Phase 0 — tabs follow session titles (shipped 2026-11-04)

Both CLIs already set the window title over OSC 0. Claude Code sends ✳ <topic> when idle and ◐◑◒◓ <topic> while working. Codex sends a braille spinner plus [tui].terminal_title items. Its default is the project name only, so the Macs now set terminal_title = ["spinner", "thread-name", "project-name"]. thread-title would show the thread UUID until Codex names the thread.

    GUI (Renderer.m, Shell.swift, Organization.swift): a program's SET_TITLE becomes a live title for its tab. Live titles are kept per window and never go into the synced organization document. A name given with Rename still wins. A leading status mark becomes a small "working" spinner on the sidebar row and the top chip. This works with the daemons already running, because every open terminal tab keeps a live Ghostty surface.

    Daemon (probe.py): tracks the last OSC 0/2 title per session and adds terminalTitle and busy to the catalog. It replays the title at the front of attach snapshots, so a reopened GUI or a CLI attach gets the name before any new output. This only takes effect when the daemon next restarts, because restarting it now would end every shell.

    Tests: Tests/test_integration.py (split OSC with an ST terminator, busy/idle, snapshot replay), Tests/NativeWorkspace (parser, precedence, not synced), Tests/gui_organization.py (a real printf OSC title renames the tab in the app).

Phase 1 — agent identity and attention via hooks

The goal is for Probe to know that a session is cc or cx, which native session it runs, in which checkout, and whether it is working, waiting for Eric, or idle.

    The daemon exports PROBE_SESSION_ID=<uuid> (and the socket path) to each PTY, next to the existing PROBE_SESSION=1.

    New probe agent-event CLI. It reads a hook payload on stdin and sends {op:"agent", session, provider, nativeSessionId, cwd, state, message} to the daemon. It does nothing outside Probe, so the same hook config works in cmux, iTerm or SSH.

    Claude Code hooks in ~/.claude/settings.json: SessionStart (sessionid, cwd, transcriptpath), UserPromptSubmit (working), Notification (permission prompt or idle: needs you), Stop (idle, with the last assistant line), SessionEnd.

    Codex 0.166 has the same hook family behind the codex_hooks feature: SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, Stop. One handler covers both providers. The existing notify entry (Codex Computer Use) stays as it is.

    The UI gets a "needs you" badge on the tab and its group, a macOS notification when the tab isn't visible, and optional fleet-notify to Telegram for long waits. Busy state from hooks takes over from the title heuristic when present.

Phase 2 — launch and resume natively

    The New Tab dropdown gets cc here / cx here, with a project picker from ~/.config/cyberdeck/projects.json on the chosen host. Worktree creation is optional.

    Resume: Home lists recent cc/cx sessions from the Deck session index (deck sessions --json, all hosts). Opening one runs claude --resume <id> or codex resume <id> in that session's checkout on that host. If Phase 1 shows the native session already running in some Probe PTY, Probe focuses that tab instead (one owner).

    Session records survive a GUI relaunch with their agent identity. After a reboot, Probe offers to resume them rather than showing dead tabs.

Phase 3 — Cyberdeck and T3 see Probe-owned agents

    The Probe catalog (already reachable fleet-wide over probe --host fleet-<id>) becomes Cyberdeck's source for "agents running in terminals" with owner probe, replacing PTY/tmux byte scraping for state.

    A fleet Agents view in Probe Home shows every cc/cx on every host, with its state, checkout and waiting question. T3-owned threads are listed with a "open in T3" action, not a second writer.

Phase 4 — structured messages (later, per AGENT-COMMUNICATION.md)

    Claude Channels for sending a message to an open cc without injecting keystrokes. It is a research preview and needs the interactive dev opt-in.

    Codex App Server for Cyberdeck-owned cx conversations, with turn steer/interrupt and approvals as UI events.

    Neither is a prerequisite for Phases 1–3.

Open questions for Eric

    Should Phase 1 hooks be installed fleet-wide (Deck-managed settings), or only on the laptops and Clipper?

    Should "needs you" also go to Telegram after a delay, and if so, after how long?

    Should Resume adopt sessions that T3 started (open in a terminal with --resume), or always hand off to T3?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Connections0
Probe × cc/cx native integrationProbe × cc/cx native inte…
Citations 0Children & links 0

Loading child documents…

Connections show where other documents or comments link to this document.

Related documents

Loading connections…