Track Codex cloud tasks and Claude Code cloud sessions next to your local chats

The problem

Both Anthropic and OpenAI can run coding agents on their own servers: Claude Code sessions in Anthropic's cloud, and Codex cloud tasks. That's useful for long jobs you don't want tying up your laptop, but it adds two more places to check. Local work is in the desktop apps; cloud work is in a web page or a separate list, and it's easy to forget a cloud task that finished an hour ago and is waiting for you to apply it.

How Pairbar solves it

1. Load Claude's cloud sessions once
   Open Code in the Claude app so it loads its Code sessions list. Pairbar reads the app's own cached copy of that list (read-only), and the rows appear within a few seconds.
2. Make sure `codex` is logged in
   Codex cloud tasks come from codex cloud list, run with your own codex and its login. If codex cloud list lists your tasks in a terminal, Pairbar can too.
3. Group by project
   Cloud chats join the local chats of the same repo, so one group shows everything happening in, say, acme-api. Cloud chats without a repo go under Cloud.
4. Open or organise them
   Click a row to open it. The cloud menu offers Open in Claude (Claude sessions, with the Claude app installed), Open in browser, Pin, Mark as unread / read, Rename… (in Pairbar only), Copy link, Labels, Select and Hide. Read markers and selection are kept in Pairbar.

Where each comes from

Limits

• There's no transcript on your Mac, so cloud chats have no question text, current action, conversation search, subagents, handoff, fork, follow-up or check-in, and no alert when one needs you.
• A Claude cloud session is only as current as the Claude app's copy, and shows only after the app has loaded its Code sessions list at least once. Sessions archived in Claude are left out.
• If the app's cache can't be read (a newer format, a file mid-write), cloud sessions are simply left out; local chats are unaffected.
• Sessions you run through Remote Control are your Mac's own chats and are listed once, as local chats.
• Renaming a cloud chat changes its name in Pairbar only; the title on claude.ai or chatgpt.com stays.

Starting a cloud chat from Pairbar

In the composer, switch the Local chip to Cloud. For Codex, with an environment id saved for the repo (its environment chip), the task is sent straight to Codex Cloud with codex cloud exec and its page opens. Claude can't be started in the cloud from outside, so Claude's new chat opens with your text and folder filled in and you pick a cloud environment there.

Without Pairbar

Each service has its own view of cloud work:

• Claude Code cloud sessions: the Claude app's Code section and Claude Code on the web at claude.ai list them with their status.
• Codex cloud tasks: the Codex page on chatgpt.com, and codex cloud in the terminal.
• Both are the source of truth and show more than Pairbar can (the full transcript and diff). What they don't do is put the two services and your local chats in one list.