[codex] park side packages, expand native api, and hide /agent#12
Merged
[codex] park side packages, expand native api, and hide /agent#12
Conversation
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.
What changed
codex-gatewayandmission-controlin the docs and clarified thatcodex-native-apiis the only retained future package pathcodex-native-apitoward a more standalone npm package with package-local CLI, daemon management, default provider bootstrap, and broader responses/web-search handling/agentcommand from user-facing help and aliases, blocked direct invocation by default, and disabled related background scheduling and notifications unless explicitly re-enabledWhy it changed
codex-native-apineeded a stronger standalone surface before any future packaging decision/agentis not ready for end users yet, so it should stop showing up in discovery paths or leaking through nearby command flowsImpact
/agentin normal bridge sessions/agentavailable by default through the test runner flag so existing agent coverage remains intactRoot cause
/agentwas still wired into the live help catalog, alias map, and background runtime even though the command is not production-readyValidation
git diff --checknode ./scripts/test.mjs --test-name-pattern="/helps lists all supported slash commands and help entrypoints|/helps renders English help text when locale is set to en|/agent stays hidden and unavailable when the command flag is disabled|/review natural language can reject execution requests and avoids starting review" test/core/bridge_coordinator.test.tsnode ./scripts/test.mjs --test-name-pattern="WeixinBridgeRuntime prefers supervision-backed agent scheduling and does not double-dispatch the same mission|WeixinBridgeRuntime skips agent supervision when the command is disabled" test/runtime/weixin_bridge_runtime.test.tsNotes
node ./scripts/test.mjs test/core/bridge_coordinator.test.ts test/runtime/weixin_bridge_runtime.test.tssuite still has three pre-existing/asassertions that assumeUTCoutput instead of the currentAfrica/Abidjanlocale