Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Aside integration profiles silently go `off (stale)`, breaking sidecar sync (no auto-recovery, `client sync` no-ops)

Open
  • Is something wrong?
#6,757 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, tooling

Research direction

Start by tracing the integration client sync --client aside and integration client enable entry points, then inspect how stale profiles become disabled and which profiles sync considers eligible. Reproduce with the reported off (stale) Aside profile if possible. Done means sync or doctor provides a reliable recovery path and the integration remains usable after the restart cycle.

Written by the indexing model from the issue text.

Description

Summary

After an ocx sync / Codex app restart cycle, the managed Aside integration profiles end up off (stale) and the OpenCodex sidecar provider/login config is no longer injected into Aside. ocx integration client sync --client aside then no-ops because disabled profiles aren't eligible, so there's no obvious recovery path short of a manual integration client enable.

Observed on macOS (home Mac), OpenCodex.app standalone runtime (/Applications/OpenCodex.app/Contents/MacOS/ocx), Codex 0.160.1.

What I saw

ocx integration client status --client aside:

0  bitkyc07: off (stale) [current]
1  Local Account: off (stale)
2  Local Account: off (stale)

ocx integration client sync --client aside:

No eligible Aside profiles to synchronize. Check integration status and profile sync preferences.

ocx integration native shows claude/grok/codex/claude-desktop all current / on, so only the Aside client fell out of sync.

ocx status is otherwise healthy:

Proxy: running (PID ...), Health ... ok (live)
Runtime source: standalone
routing=opencodex-local, service=absent, shim=absent

(Also surfaces Restart safety: AT RISK ... run 'ocx service install' and Codex autostart shim is not installed — possibly related, since there's no viable background service to keep integrations fresh across restarts.)

Likely cause

  • Aside profiles were marked stale (owner/attestation drift) and then flipped off, but nothing re-enables them automatically.
  • integration client sync --client aside only refreshes already-enabled profiles, so once they're off it reports "No eligible Aside profiles" instead of offering to re-enable or pointing at integration client enable.
  • Compounding: the Aside cloud account ([email protected]) is signed out with device mismatch, which also makes aside exec (built-in models) fail with a 400, while aside repl (direct browser) still works. The ocx-side off (stale) and the Aside-side sign-out look correlated.

Expected

  • integration client sync --client aside (or ocx doctor) should detect off (stale) profiles and either re-apply them or clearly tell the user to run integration client enable --client aside --profile N.
  • Ideally, the sidecar integration should survive an ocx sync --restart-codex / app relaunch without silently going stale.

Workaround

Manual re-enable:

ocx integration client preview --client aside --operation apply --profile 0
ocx integration client enable  --client aside --profile 0

(preview fingerprint p2:15b1dbef33ed299ae3ff59b9767c76ad, change = replace providers.opencodex).

Environment

  • OpenCodex.app runtime: standalone (also npm @bitkyc08/[email protected] installed under nvm, not running)
  • Codex 0.160.1, macOS (Apple Silicon)
  • proxy port 10100
Dominant language
TypeScript
Stars
16.9k
Forks
1.3k
Avg merge
4h 58m
Merged PRs (30d)
616

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lidge-jun/opencodex

All issues in lidge-jun/opencodex

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.