Skip to content

feat(coding-agents): carry the Codex plugin's endpoint over too - #3203

Open
nicoloboschi wants to merge 1 commit into
mainfrom
feat/legacy-endpoint-codex
Open

feat(coding-agents): carry the Codex plugin's endpoint over too#3203
nicoloboschi wants to merge 1 commit into
mainfrom
feat/legacy-endpoint-codex

Conversation

@nicoloboschi

Copy link
Copy Markdown
Collaborator

Follow-up to #3193. The endpoint carry-over only read ~/.hindsight/claude-code.json, so someone migrating off the Codex plugin silently landed on Cloud despite having a server configured.

Codex uses identical key names in ~/.hindsight/codex.json, so one reader serves both. The agent being installed is checked first — wiring Codex takes Codex's server even when a stale claude-code.json is still lying around — then falls back to any known legacy config, since one server shared by both is the common case.

Verified with both files present and conflicting URLs: install codex picks http://codex-server:8888.

These two are the only superseded plugins that shipped a user config; Cursor CLI, Copilot CLI, opencode and Cline have no endpoint to carry.

317 tests pass, lint clean.

The endpoint carry-over only read ~/.hindsight/claude-code.json, so someone
migrating off the Codex plugin silently landed on Cloud despite having a server
configured. Codex uses the same key names in ~/.hindsight/codex.json, so one
reader serves both.

The agent being installed is checked first: wiring Codex must take Codex's
server even when a stale claude-code.json is still present. It then falls back
to any known legacy config, since one server shared by both is the common case.

These two are the only superseded plugins that shipped a user config —
Cursor CLI, Copilot CLI, opencode and Cline have no endpoint to carry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant