[codex] Add runtime abstraction and cc-connect provider#1103
Draft
ashione wants to merge 42 commits into
Draft
Conversation
added 12 commits
June 8, 2026 20:35
75a8efd to
a504a8c
Compare
…action-cc-connect # Conflicts: # electron/services/providers-api.ts # package.json # pnpm-lock.yaml
Add operation-level runtime capabilities so cc-connect can report native, proxy, and unsupported sub-operations without overstating OpenClaw parity. Keep OpenClaw as the default runtime, surface cc-connect operation gaps in Settings, and extend OAuth/bundle E2E coverage plus harness specs for replacement-readiness validation.
Send GUI chat through the Codex bridge so cc-connect runtime sessions use Codex as the execution engine. Persist Codex JSONL tool call and tool output events as ClawX history messages so the chat execution graph can show command/tool relationships.
Default cc-connect Codex execution to ClawX-managed runtime workspaces under userData instead of the ClawX source checkout. Map OpenClaw agent ids to cc-connect managed workspace directories without inheriting OpenClaw workspace paths, while preserving explicit workDir overrides for diagnostics.
Reuse existing OpenClaw agent/default workspaces when generating cc-connect project work dirs, while falling back to managed cc-connect workspaces for missing paths. Keep the Codex bridge cwd aligned with the selected main workspace and document the workspace compatibility contract in the runtime architecture docs and harness spec.
Send cc-connect GUI chat through the BridgePlatform adapter instead of invoking CodexCliBridge directly. Prefer bridge-owned history before falling back to Codex transcript history, and update tests/specs to lock the runtime contract.
Delete CodexCliBridge and its standalone transcript tests so cc-connect runtime state is sourced through BridgePlatform. Drop Codex transcript session fallback, provider injection hooks, and stale harness references to the deleted bridge.
Remove direct Codex transcript fallback from the cc-connect bridge adapter so sessions and history come only from cc-connect bridge/session state. Document the invariant that ClawX may only provide Codex bundle/auth/config inputs to cc-connect and must not directly execute Codex or read Codex runtime state.
Contributor
Author
|
@vcfgv cc connect supports PI-Agent as well. You might dive into it and do some research about how to connect to runtime. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a runtime abstraction layer for ClawX so OpenClaw remains the default runtime while
cc-connectcan be selected as an optional packaged runtime.This update completes the cc-connect replacement slice:
cc-connectand native OpenAI Codex CLI artifacts into app resources; runtime startup no longer depends on global installs, PATH binaries,node_modulespostinstall binaries, or app-time downloads.app.getPath('userData')/runtimes/cc-connect/config.toml.chat:message/chat:runtime-eventHost events.Validation
pnpm run typecheck:nodepnpm run typecheck:webpnpm exec vitest run tests/unit/cc-connect-runtime-provider.test.ts tests/unit/cc-connect-paths.test.ts tests/unit/codex-paths.test.ts tests/unit/codex-bundle.test.ts tests/unit/cc-connect-skills.test.ts tests/unit/host-services.test.ts tests/unit/runtime-manager.test.ts tests/unit/codex-cli-bridge.test.tspnpm run bundle:cc-connect:current && pnpm run bundle:codex:currentpnpm run comms:replay && pnpm run comms:comparepnpm run build:vite && pnpm exec playwright test tests/e2e/cc-connect-codex-runtime.spec.ts tests/e2e/settings-runtime-selector.spec.tspnpm exec eslint electron/main/ipc-handlers.ts electron/runtime/cc-connect-bridge-adapter.ts electron/runtime/cc-connect-paths.ts electron/runtime/cc-connect-provider.ts electron/runtime/cc-connect-skills.ts electron/runtime/codex-paths.ts electron/runtime/codex-cli-bridge.ts electron/runtime/types.ts electron/services/cron-api.ts electron/services/skills-api.ts scripts/bundle-codex.mjs scripts/codex-bundle-lib.mjs tests/e2e/cc-connect-codex-runtime.spec.ts tests/unit/cc-connect-paths.test.ts tests/unit/cc-connect-runtime-provider.test.ts tests/unit/cc-connect-skills.test.ts tests/unit/codex-bundle.test.ts tests/unit/codex-paths.test.ts tests/unit/host-services.test.ts tests/fixtures/codex-bundle-api.tsgit diff --checkbuild/cc-connect/darwin-arm64/cc-connect --versionbuild/codex/darwin-arm64/bin/codex --versionNote: local full
pnpm run lint:checkstill fails only because this checkout contains nested.claude/worktrees/...directories with unrelated lint errors outside the PR diff. The scoped lint command above covers the files changed by this PR and passes.Remaining Notes