Official coverage map
Map the local Codex collection to upstream documentation and define maintenance scope.
This page records the scope of the Codex documentation collection. The upstream reference is the Codex manual. These guides aggregate installation, configuration, permissions, extensions, automation, governance and Passion8 boundaries rather than translating every official page verbatim.
| Item | Count | Location |
|---|---|---|
| Upstream Source blocks in the historical snapshot | 91 | Recount after refreshing the manual; not a live coverage claim |
| Local Codex articles per language | 27 | content/docs/codex and content/docs/en/codex |
| Main connection guides | 2 | Install, Configure |
| Audit/troubleshooting entry points | 2 | This page and Troubleshooting |
#Coverage areas
| Area | Local guides | Upstream topics |
|---|---|---|
| Setup and configuration | Install, Configure, Reference | Quickstart, authentication, configuration, models |
| CLI and daily work | Commands, Terminal, Workflow, Git, Review | CLI, slash commands, best practices, reviews |
| App, IDE and entry points | App, IDE, Availability, Platforms, Browser | Desktop, IDE, web, browser, computer tools, remote connections, Sites |
| Permissions and network | Permissions, Security, Troubleshooting | Approvals, sandbox, permissions, review and internet access |
| Customization | MCP, Skills, Hooks, Memory | Tools, skills, plugins, instructions, hooks, rules, memories and imports |
| Parallel work | Subagents, Git | Subagents, worktrees and background tasks |
| Automation and SDKs | Automation, CI/SDK, Reviews | Environments, exec, Actions, SDK and app-server |
| Enterprise | Governance, Availability, Platforms | Administration, managed configuration, tokens, Windows and provider policy |
#Passion8 conventions
| Client | Base URL | Reason |
|---|---|---|
| Codex | https://passion8.cc/v1 | OpenAI / Responses-compatible prefix |
| Claude Code | https://passion8.cc | Anthropic Messages-compatible prefix |
Supported local clients read their runtime's Codex configuration. Hosted tasks and integrations do not automatically inherit your local Passion8 provider.
#When to add a page
Create a separate guide when:
- A capability has its own workflow, such as hooks, CI or managed configuration.
- It materially changes execution/data boundaries.
- Provider, hosted-service and local behavior need separate explanation.
- An existing guide has too many responsibilities to navigate clearly.
Extend an existing guide when:
- The change is one command, setting or diagnostic entry.
- It fits an existing section, such as a new slash command.
- A new navigation entry would not help readers.
#Maintenance commands
After refreshing the manual, count source blocks:
rg -n '^Source: ' /tmp/openai-docs-cache/codex-manual.md | wc -lCount local articles:
find content/docs/codex -maxdepth 1 -type f -name '*.mdx' | wc -l
find content/docs/en/codex -maxdepth 1 -type f -name '*.mdx' | wc -lThe original navigation check for Chinese source routes:
node - <<'NODE'
const fs = require('fs');
const path = require('path');
const root = 'content/docs';
function walk(dir) {
return fs.readdirSync(dir, { withFileTypes: true }).flatMap((d) => {
const p = path.join(dir, d.name);
return d.isDirectory() ? walk(p) : p;
});
}
const pages = new Set(walk(root).filter((f) => f.endsWith('.mdx')).map((f) => {
const rel = path.relative(root, f).replace(/\.mdx$/, '');
if (rel === 'index') return '/docs';
return `/docs/${rel.replace(/\/index$/, '')}`;
}));
const nav = fs.readFileSync('src/lib/docs-nav.ts', 'utf8');
const links = [...nav.matchAll(/href: "([^"]+)"/g)].map((m) => m[1]).filter((href) => href.startsWith('/docs'));
const missing = links.filter((href) => !pages.has(href));
console.log({ pages: pages.size, links: links.length, missing });
NODEFor generated bilingual navigation, use the actual navigation functions and renderer rather than assuming literal href strings cover every entry. Verify translated slugs and anchors as well as page counts.
#Official references
Support
Need help?
For setup, billing, or model issues, email us. Check the status page for uptime.
WeChat / QQ support is available at the bottom right.

