Codex Central Memory Setup

Summary

Each Codex host should use Closed Akashic MCP directly as its shared memory. Do not clone or depend on local agent-knowledge for normal work.

Host Setup

1. Configure Closed Akashic authentication at the machine level, outside any project repository.
2. Add the closed-akashic MCP server to ~/.codex/config.toml.
3. Put the host-level memory rules in ~/.codex/AGENTS.md.
4. Start a new Codex session so the MCP registration and AGENTS instructions are loaded.
5. Smoke-test with search_notes, read_note, and a small safe write-back.

Required MCP Endpoint

[mcp_servers.closed-akashic]
url = "https://knowledge.openakashic.com/mcp/"

Preferred Auth for Shared Local Agent Setups

Prefer a static Authorization header in the machine-local Codex config when the host is shared by local agents and GUI/session environment propagation is unreliable:

[mcp_servers.closed-akashic]
url = "https://knowledge.openakashic.com/mcp/"
http_headers = { Authorization = "Bearer <redacted>" }

Do not store or document the real token value in repositories or project notes.

Env Var Fallback

Use bearer_token_env_var only when the token must not be stored in ~/.codex/config.toml:

[mcp_servers.closed-akashic]
url = "https://knowledge.openakashic.com/mcp/"
bearer_token_env_var = "CLOSED_AKASHIC_TOKEN"

For shell-based hosts, keep the token in a host-local profile or service environment:

export CLOSED_AKASHIC_TOKEN="set-your-master-token-here"

Already-running GUI apps or agent processes can keep stale env state, so restart the Codex session after changing auth config.

Required AGENTS File

Use [[Codex AGENTS Template]] as the canonical text for ~/.codex/AGENTS.md.

For a single deployable instruction file, use [[Codex MCP Deployment]].

For token-specific setup details, use [[Closed Akashic Shared Agent Token Setup]].

Copy-Paste Setup

Run this on each Codex host after configuring authentication outside any project repository.