Install · OpenAI Codex CLI

Your Codex work becomes verified skill signal.

Axsept observes your sessions with Codex — what you ask, what you accept, what you push back on — and records the skills you demonstrated into your proof on axsept. It runs on the same open standard as the Claude Code plugin; nothing leaves your machine without being anonymized first.

Before you start

Codex CLI and Node.js 18+ installed (the integration uses npx).
A axsept account (or you'll be prompted to create one during the install flow — the 60-day trial applies).

Install in one command

1
Run the installer
In your terminal:
```
npx @axsept/codex init
```
This registers the axsept MCP server in ~/.codex/config.toml and adds the activity-tracking guidance to ~/.codex/AGENTS.md. Existing config is preserved — it only edits a clearly-marked axsept block.
2
Authorize in your browser
The installer opens https://app.axsept.com/connect?source=codex. Sign in, click Authorize Codex CLI, and copy the displayed sk_user_… key.
3
Paste the key
Paste it back at the terminal prompt. The installer writes it into your ~/.codex/config.toml (file mode 0600). Restart Codex or start a new session.
Done. As you work in Codex, it logs activities to your profile — sparingly, only on substantive moments.

Optional: automatic capture (experimental)

By default, Codex logs activities when its model judges a moment worth recording (the reliable rich path). You can also opt into lifecycle hooks that nudge it to log after substantial work, with:

npx @axsept/codex init --with-hooks

These hooks ship in dry-run by defaultand are still being calibrated against Codex's hook contract — they won't change your sessions yet. The rich path above is the supported way to capture today.

What gets captured

Skills Codex observed you demonstrate (e.g., system design, debugging, code review)
How you directed the work — whether you course-corrected, validated, or delegated
Short evidence snippets from your own prompts, post-anonymization
Tools and frameworks you mentioned

What doesn't

Raw conversation transcripts
API keys, tokens, SSH keys, JWTs (regex-stripped locally)
Email addresses, phone numbers, SSNs, credit card numbers
Project codenames or customer names you add to your local denylist

Local-first by design

The integration uses the same local @axsept/mcp-server that powers the Claude Code plugin — Codex itself observes and classifies; we don't do server-side LLM extraction. Before any data reaches axsept, it's passed through @axsept/anonymizer locally, which strips PII and secret patterns. Activities are tagged with their source (codex) so you always know which tool produced each signal. The full pattern set is open source — you can audit exactly what we redact.

What Codex can do once installed

log_activity

Records a discrete activity you demonstrated a skill on. Called sparingly (2–8 times per hour of focused work) — not on every message.

record_session_summary

At natural session boundaries, captures your directing / orchestration skill across the whole session.

get_profile_snapshot

Read-only. Lets Codex see your current proof on axsept to avoid re-logging what's already there and to personalize coaching when you ask.

Troubleshooting

Check what's installed

Run npx @axsept/codex status to see whether the MCP server, instructions, and (optional) hooks are wired up, plus your base URL and key.

Activities aren't appearing on my profile

Codex only logs on substantive moments. For quick questions, that's expected — try a longer working session. You can also nudge it explicitly: "Use the skillchain log_activity tool to record what we just did."

Revoke / rotate my key, or point at staging

Re-authorize anytime with npx @axsept/codex connect. Manage or revoke keys from Settings → API Keys (revoke is immediate).

For staging / self-hosted, pass --base-url https://staging.skillchain.tech to init or connect.

Removing the integration

npx @axsept/codex uninstall removes the axsept blocks from config.toml and AGENTS.md and deletes the hook scripts. Then revoke the key from Settings → API Keys for clean rotation.

Ready to connect?

Run npx @axsept/codex init, or open the Connect page directly to grab a key first.

Open Connect page Manage existing keys

The Codex wrapper is open source. Source: github.com/skillchain/integration-protocol. It reuses the same MCP server, event schema, and anonymizer as every axsept wrapper; only the Codex-specific install glue is new.