Reference gpt sol claudex remote control blocked

Confirmed directly from Claude Code error text: "Remote Control is only available when using Claude via api.anthropic.com." This is an absolute gate, not a bug. claudex (the CLIProxyAPI-based alias that runs Claude Code driven by GPT-5.6 Sol on Justin's ChatGPT subscription) works fine as a local session but can never register with claude.ai/code. That means none of /spawn, the warm pool, /rebridge, or the Telegram remote-bridge bot can ever be built on top of claudex — they all depend on Remote Control, which requires Anthropic auth.

Why: This closes off an entire class of future ideas ("let's make Sol drive spawned workers", "bridge Sol sessions to Telegram") before time is spent prototyping them.

How to apply: If Justin or a future session proposes extending claudex to mobile/remote surfaces, cite this constraint immediately rather than re-investigating. /codex:* plugin commands (shell out to local codex CLI, don't replace Claude's model) remain the correct way to get Sol's help from within a Remote Control session. Full detail: memory/general/reference_gpt_sol_in_claude_code.md.

[auto-memory session b3dd3bff-68c5-48fb-a063-4866759a10f8, confidence 0.85, mode direct]

Auto-memory addendum 2026-07-13T01:19:27.633560¶

Confirmed directly from Claude Code: "Remote Control is only available when using Claude via api.anthropic.com." This is a hard client-side gate, not a bug or oversight. Setting ANTHROPIC_AUTH_TOKEN/custom base URL (as claudex does to route through CLIProxyAPI to GPT-5.6 Sol) disables Remote Control entirely.

Why: Remote Control registers the session with claude.ai and streams tool traffic through Anthropic's infrastructure; it authenticates the transport, not just the model. There is no legitimate way to make it carry a non-Anthropic model without patching the Claude Code binary or spoofing auth, which was explicitly rejected as an approach (circumvents a technical control on Anthropic's product).

How to apply: Do not propose or attempt bridging claudex/Sol sessions to claude.ai/code, /spawn, the warm pool, or the Telegram remote-bridge bot. claudex is confirmed terminal-only (Console shell only). For mobile-first Sol access, the legitimate paths are: (1) Telegram bridge shelling out to codex exec/codex resume, (2) Codex's own hosted web surface, or (3) a custom tmux-based control panel behind Cloudflare Access. Regular claude (Opus, Anthropic auth) remains the only path with full Remote Control.

[auto-memory session b3dd3bff-68c5-48fb-a063-4866759a10f8, confidence 0.85]