Skip to content

[codex] add QoderWork CN bridge tweak#1

Open
jupiternaut wants to merge 1 commit into
mainfrom
codex/qoderworkcn-bridge
Open

[codex] add QoderWork CN bridge tweak#1
jupiternaut wants to merge 1 commit into
mainfrom
codex/qoderworkcn-bridge

Conversation

@jupiternaut

Copy link
Copy Markdown
Owner

Summary

Adds a bundled Codex++ tweak for QoderWork CN that exposes a local OpenAI Responses-compatible bridge model (qoderworkcn-codex) backed by the QoderWork CN CLI qmodel lane.

What changed

  • Add tweaks/qoderworkcn-bridge with main-process bridge startup and renderer settings UI.
  • Add a local Responses API server with /v1/responses, /v1/models, /health, /usage, and /codexbar/cost.
  • Add structured tool-call bridging for Codex app tools and explicit Subagent A/B/... startup planning via create_thread.
  • Add CodexBar-style JSONL usage ledger and a settings-page usage visualization.
  • Add isolated profile/config handling so the tweak can avoid mutating the user's normal ~/.codex profile.
  • Add docs and focused Node tests.

Installation / usage note

Installing Codex++ alone does not automatically switch Codex to QoderWork. The bridge works when this bundled tweak is linked/enabled, for example with:

codexplusplus dev tweaks/qoderworkcn-bridge --replace --no-watch

The machine must also have QoderWork CN CLI available at the configured QODER_CLI path. The tweak then starts a local Responses-compatible endpoint and writes managed Codex provider config into its isolated profile unless QODERWORKCN_CODEX_HOME or CODEX_HOME is set explicitly.

Validation

  • node --import tsx packages/installer/src/cli.ts validate-tweak tweaks/qoderworkcn-bridge
  • npm test --prefix tweaks/qoderworkcn-bridge
  • npm test --prefix tweaks/qoderworkcn-bridge/bridge
  • staged diff scan for local usernames, API keys, and usage JSONL files

Recreated from closed upstream PR: b-nnett#606

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