Skip to content

CodexBot v0.1.0-beta.1 — CLI onboarding

Pre-release
Pre-release

Choose a tag to compare

@AppSolves AppSolves released this 15 Nov 12:15
Immutable release. Only release title and notes can be modified.
067be58

CodexBot v0.1.0-beta.1 uses CLI-based initial ChatGPT provisioning. Reviews and merges then run unattended on repository-owned GitHub Actions; a permanently running CLI or VM is unnecessary.

Supported modes:

  • Native COMMENT, APPROVE and REQUEST_CHANGES with exact-commit inline findings.
  • Automatic reviews with explicit administrator consent for a repository-owned credential assignment; contributors never implicitly share accounts.
  • Fully Autonomous merging with zero CodexBot-required human approvals, or Human-in-the-Loop with 1–6 independent human approvals.
  • Repository opt-in, separate merge authorization, required CI, App-bound guards, current-head verification and all applicable GitHub protections. No protection bypass.

Live evidence:

  • Complete APPROVE and protected autonomous merge without a human: disposable acceptance PR #3, workflow 43669491863.
  • A substantial authorization regression: REQUEST_CHANGES on the changed security line, PR #4, workflow 43669871592; never merged.
  • Pending required CI: native auto-merge queued by CodexBot while the App guard and required CI remained pending on PR #9.
  • Complete advisory COMMENT and inline findings verified separately.
  • Final immutable runner pin and environment-only/OIDC credential diagnostic: f008673, workflow 43679274620.

Browser ChatGPT OAuth is deferred. WEB_ENABLED=false and OPENAI_HOSTED_INFERENCE_AUTHORIZED=false. The approved CLI ChatGPT deployment remains enabled. No API-key fallback is used.

Beta limitations: AI review can miss defects; incompatible merge queues or unverifiable protection/check evidence fail closed. Trusted repository administrators/workflow writers remain inside the credential trust boundary. Credentials, local state and generated build directories are excluded from release archives.

Validation: 198 tests, typecheck, lint, build, clean-checkout, real workerd/D1 tests, synthetic browser onboarding, pinned Codex Docker isolation, Actionlint, dependency audit, runtime image security scan and Wrangler dry-run passed in CI. Synthetic provider tests are not represented as real provider acceptance. Migration 0006 is additive; existing production migrations are current.
Production verification:

  • Release implementation: #35, merged commit 067be58; CI run 43679312787 passed.
  • Final immutable runner source: f008673. Worker, backend expectation, TopkAPI caller and disposable caller agree.
  • Worker version bd6e416f-4596-4db2-8ca8-793bc700dbb8; deployment 5248884b-5b9a-4d97-955f-e92a13743ee3 at 100%.
  • Production https://codexbot.appsolves.workers.dev/health reports 0.1.0-beta.1. CLI installation landing, canonical redirects, disabled browser authentication and cross-origin rejection were verified.
  • CHATGPT_DEPLOYMENT_AUTHORIZED=true; MERGE_DEPLOYMENT_AUTHORIZED=true; WEB_ENABLED=false; OPENAI_HOSTED_INFERENCE_AUTHORIZED=false. Temporary acceptance scope and operator quota overrides are cleared.
  • Owner-consented automatic review for an unconnected github-actions[bot] contributor: complete native APPROVE, https://github.com/AppSolves/codexbot-acceptance-20261115/pull/10, workflow 43679528359. No provider session belongs to the contributor.
  • Human-in-the-Loop: PR #10 was held while only the Bot approved. After a genuine independent human approval, fresh complete inference (workflow 43712378653), native APPROVE and both required checks, CodexBot merged it natively at 2026-11-15T12:13:07Z as 895dd8e9f52b8add5855013fa9b2aa53f3ef383c. GitHub protection required one approval, the human had write access, and the bypass actor list was empty. The merged tree exactly matches the reviewed head.

Merged implementation and source-pin PRs:

PR Actual merge SHA
23 929ff2a
24 86f54dd
25 b15163e
26 29c6254
27 01aba17
28 4cc32b8
29 757c28e
30 59b00dd
32 f008673
33 e20f3bd
34 8dd88f6
35 067be58

Caller coordination: Worker trust, backend expectations and both verified caller repositories pin f008673. Existing Environment guards and named secret references are preserved.

Acceptance failures were not hidden: the original waiting merge intent expired and was cancelled. Two fresh attempts returned incomplete analysis, failed their review jobs and produced a non-approving COMMENT. A corrected snapshot-path context then produced the fresh complete review above. No incomplete result or stale request authorized a merge. Merge intents expire after one hour; expiry requires a fresh authorized review. Browser OAuth and a real paid API-key acceptance run remain outside this CLI/ChatGPT beta acceptance.