Full sync not working

[sk2andy]

Component

Mobile App

Problem

When I continue a session on my main codex app ccpocket stops following the updates. It only gets its own initiated Outputs from the model. A refresh button or anything would help big time because I hope between devices quite a lot

Proposed solution

When having a session open that is not running, check for updates every 5s or so and reattach in case of changes to the live update algorithm you already have

Alternatives considered

No response

Additional context

sk2andy#1

I made a pr on a fork. Maybe have a look. I hope that can gelp

[K9i-0]

Thanks for the detailed write-up and the fork PR — really appreciate the effort!

Sharing active Mac sessions with CC Pocket is an appealing idea. That said, I want to be deliberate about how we approach it, both architecturally and from a UX perspective, so I'd like to take some time before committing to a specific implementation.

For context, CC Pocket is designed around the concept of starting and completing development sessions entirely from your phone (see the README for more on this). Syncing sessions that were started elsewhere is a nice-to-have, but it's not a blocker for the core workflow.

I'd like to gauge community interest before raising the priority on this. If you find this feature valuable, please leave a 👍 on this issue — that'll help me prioritize accordingly.

[tlk3]

Not being able to resume from desktop in the Codex app is a real pain.

[K9i-0]

@tlk3 Thanks for bringing this up! Just to clarify — CC Pocket sessions are fully shared with the Codex CLI since they use the same session storage (~/.codex/sessions/). You can resume any CC Pocket session from the CLI and vice versa.

The issue of sessions not appearing in the Codex Desktop App is actually a known upstream limitation. The Desktop App doesn't fully sync with CLI/app-server session history. There are several open issues tracking this on the Codex repo:

• openai/codex#14722 — Sync CLI and app-server sessions
• openai/codex#14751 — Desktop app sidebar only shows loaded recent subset

If this is impacting your workflow, I'd recommend upvoting those upstream issues to help raise visibility. Once Codex resolves the CLI↔App sync, CC Pocket sessions should automatically appear in the Desktop App as well.

[K9i-0]

@tlk3 Heads up — the latest Codex App seems to show CLI/app-server session history now. CC Pocket sessions showed up in my environment. The upstream issues are still open, but try updating your Codex App.

[tlk3]

@K9i-0 Appreciate the heads up! Will give it a whirl.

[K9i-0]

Quick update on this.

I've been investigating whether this can be solved using Codex's official app-server / remote mechanism instead of adding a separate sync layer in CC Pocket. The current findings are documented here:

• docs/design/shared-app-server.md

Short version: it is not reliable enough for a user-facing feature yet. The WebSocket transport is still experimental / unsupported, thread/resume still has practical limitations around persisted history, and the current protocol does not expose enough per-client / per-turn ownership information to cleanly distinguish messages from CC Pocket vs another joined client.

Separately, as mentioned in this PR comment, the core cross-device workflow is possible today in a different way: on macOS, using the desktop version together with the mobile app can provide the synced experience without introducing a separate CLI / PTY / sidecar routing architecture.

So I'd like to keep this issue open as the tracking issue for broader Codex session sync, but the current direction is:

• macOS desktop app + mobile app is the practical path for now
• Codex official app-server / remote based sharing remains shelved until the upstream protocol becomes stable enough
• Codex session stops syncing to iOS after opening the session in CC Pocket #81 is a more specific report of the same underlying limitation, so I'll close it as a duplicate of this issue

[tonyho]

Hoping this issue can be resolved, even though it seems that it depends on the upstream.
Also anyone have tips to resume the session that was started or resumed in the CCpocket in the Codex CLI?

[K9i-0]

@tonyho Thanks! The broader sync/live-join behavior is still under investigation.

For resuming a CC Pocket Codex session from the Codex CLI, there are a few options:

1. Run codex resume and pick the session from the history list.
2. Run codex resume <session-id> to resume a specific session directly. In CC Pocket, long-press a history item to copy this command.
3. Start codex normally, then use the /resume command inside the TUI to open the history list.

If you want a synced CC Pocket experience today, using the macOS version together with the mobile app is also a good option:
https://github.com/K9i-0/ccpocket/releases?q=macos

[K9i-0]

Quick update: this is not fully solved yet, so I’ll keep the issue open as the broader tracking issue for Codex session sync / live co-presence.

CC Pocket 1.97.0 and Bridge 1.58.0 now include an experimental first step: sessions started from CC Pocket can expose a session-specific codex resume ... --remote ... command, which can be copied from the session screen and used from Codex CLI to join that session.

This work was based on the shared app-server / co-presence contribution from @jerryfane in #90:
#90

This does not yet cover reliably following sessions that were originally started from the official Codex App or another external client. That still depends on upstream Codex app-server / history behavior becoming stable enough.

Setup details are in the Bridge README:
https://github.com/K9i-0/ccpocket/tree/main/packages/bridge

[Snailflyer]

This is the exact split I keep running into too: phone-started sessions are useful, but a lot of real use is: I already have the CLI/tmux session running on the host, now let me steer it from the phone.

For that narrower shape I am building Faryo (Snailflyer/faryo): keep the host tmux session as the source of truth, and let phone/browser handle compact output, short input, approve/interrupt, and handoff. Not a CC Pocket fix; just a related route for the existing-live-session side of the problem.

[runsisi]

I find litter¹ did a very good job here, it can sync perfectly.

I kind of think the direction @Snailflyer pointed out is correct. Recently I tried herdr² on iPhone over SSH, it works like a charm.

Footnotes

1. https://github.com/dnakov/litter ↩

2. https://github.com/ogulcancelik/herdr ↩

[Snailflyer]

Yeah, litter/herdr are pointing at the same broader need: session continuity is less about chat history existing somewhere and more about which process is the live owner.

Since my earlier comment, I added a redacted Faryo walkthrough for the host-tmux route: https://github.com/Snailflyer/faryo/releases/download/v1.0.7/faryo-public-redacted-same-session-handoff-walkthrough-20260528-0120.gif

The narrow proof is: phone/browser input and handoff content land back in the same live tmux session, rather than becoming a separate mobile-owned run.