Codex Commit Safe
English | 简体中文
A VS Code extension that generates a locally validated Conventional Commit message from staged Git changes only, while the developer keeps full control of Git.
Start here
Use this product after staging changes and, optionally, after running Codex Review Safe. It writes only the SCM commit-message input; it never runs git commit, pushes, or edits source files.
Requirements:
- VS Code 1.90.0+
- Git
- OpenAI Codex CLI installed and authenticated in the same environment where the workspace Extension Host runs
- a trusted Git workspace
For Remote SSH, Dev Containers, Codespaces or WSL, install/authenticate Codex in the remote environment and configure safeCodexCommit.codexPath there.
First successful commit message
- Stage the files you intend to commit.
- Run Codex Commit Safe: Check Codex Environment once.
- Run Codex Commit Safe: Generate Commit Message from Source Control.
- Review or regenerate the proposed message.
- Commit manually with normal Git/VS Code controls.
See Getting Started for installation, configuration and troubleshooting.
What it guarantees
- staged snapshot only;
- deterministic scope inference before model execution;
- recent commit style is summarized locally instead of sending raw history;
- Safe Core Semantic Context Budget handles source/generated/binary files predictably;
- Structured Output is schema/semantics validated before entering the SCM input;
- HEAD/index changes invalidate stale results;
- matching Review Receipt v5 can be incorporated into Commit provenance;
- pending Commit Receipt v4 binds HEAD, index, full diff, final message, policy and review evidence;
- later Change evidence is accepted only after recomputing the real first-parent commit fingerprints;
- Safe Contract v2 runs Codex ephemeral/read-only/no-approval with shell/web/apps/multi-agent/plugins/hooks/goals/memories/dependency installation disabled;
- no source edit, commit or push side effect.
Shared safety/runtime and repository-policy validation come only from the exact commit-pinned Codex Safe Core 4.14.4 submodule at 25467922eeebffa93b7c820f2ffa7590c1625381.
Repository policy
The only repository policy is committed .codex-safe.json with schemaVersion: 4. Safe Core owns the closed commit, review, change, and reviewService sections; Commit Safe consumes only Commit policy while Change Safe owns delivery interpretation.
{
"$schema": "https://raw.githubusercontent.com/jiying2007/codex-safe-core/25467922eeebffa93b7c820f2ffa7590c1625381/codex-safe.schema.json",
"schemaVersion": 4,
"commit": {
"language": "en",
"maxDiffBytes": 262144,
"subjectMaxLength": 72,
"maxBodyChars": 2000,
"scopes": ["bsp", "driver", "wifi", "audio", "motor", "imu", "ota", "mcu", "nand", "power", "camera", "system"],
"scopePolicy": "flexible",
"autoInferScope": true,
"styleHistoryLimit": 12,
"timeoutSeconds": 90
},
"change": {}
}
Only policy committed in HEAD is effective. maxDiffBytes is the model semantic-context budget, not the raw staged-diff rejection threshold.
Family workflow
staged changes
↓
Codex Review Safe → Review Receipt v5
↓
Codex Commit Safe → Commit Receipt v4
↓
manual git commit / push
↓
Codex Change Safe → Change Receipt v1
↓
GitHub PR / GitLab MR
Commit Safe works independently; using Review Safe first adds stronger provenance. Codex PR Safe is retired as the former model-generated PR-description product; Codex Change Safe is the deterministic successor delivery stage and does not restore that narrative generator.
Install, upgrade and verify
Install from the VS Code Marketplace or an immutable GitHub Release VSIX. After upgrading, run Check Codex Environment before generating the first message.
Release artifacts are built once, checksummed and attested. See VERIFY_RELEASE.md and PUBLISHING.md.
Development
git submodule update --init --recursive
npm ci --ignore-scripts --no-audit --no-fund
npm run ci
Support and security
Identity
- Publisher:
jiying2007
- Extension ID:
jiying2007.codex-commit-safe
- Settings:
safeCodexCommit.*
License
MIT
Codex provider runtime
Codex Commit Safe defaults to Runtime Contract v3 Auto discovery. It may reuse machine Family Runtime (~/.codex-safe/runtime.json) or machine Codex configuration (${CODEX_HOME}/config.toml / ~/.codex/config.toml) in the Extension Host; VS Code provider settings remain machine-scoped advanced overrides. Environment Check performs a real structured round-trip.
Relay credentials and private-network HTTP
For openai-compatible providers, Codex Commit Safe 4.5.3 consumes Core Provider Contract v3. providerCredentialSource=auto first uses providerApiKeyEnv, then falls back to ${CODEX_HOME}/auth.json or ~/.codex/auth.json; auth-json requires auth_mode=apikey and OPENAI_API_KEY. Non-loopback http:// endpoints are rejected unless providerAllowInsecureHttp=true is explicitly set in user/application settings. Repository policy cannot provide credentials or enable insecure transport.
Runtime Contract v3 — zero-config
Commit defaults to Auto runtime discovery. If codex already works in the current VS Code Extension Host, Commit reuses machine Family Runtime (~/.codex-safe/runtime.json) or machine Codex configuration (${CODEX_HOME}/config.toml / ~/.codex/config.toml) without re-entering the relay URL. In Remote SSH the workspace extension runs remotely, so the config and auth.json are read from the remote Linux account. Literal private-IP HTTP relays are inherited with a plaintext warning; public/non-IP HTTP remains fail-closed. VS Code provider settings are machine-scoped advanced overrides.
