Give Codex a memory your whole product can use.
XandaCross is a private brain for teams building with AI agents. Connect Codex through MCP, run Zen Pulse Codex from npm, and turn every useful development session into searchable knowledge, project history, and publishable product moments.
Zen Brain
A private knowledge base for documents, memories, decisions, and project context.
XandaCross MCP
OAuth-scoped access for Codex and other MCP clients, connected to the brain the user selects.
Zen Pulse Codex
A developer workflow wrapper that captures Codex sessions, turns them into searchable knowledge, and feeds Project Pulse.
Project Pulse
A product intelligence view that turns real development activity into launch notes and marketing opportunities.
Zen Pulse Codex
Connect the brain first. Then run Codex through Zen Pulse.
MCP gives Codex authorized access to the selected XandaCross brain. The npm package gives developers a local command that captures completed Codex sessions and syncs them into that same brain.
Connect MCP first
Authorize Codex to the XandaCross MCP server so it can read and write to the selected brain.
codex mcp add xandacross --url https://xandacross.himeshbhowmik.com/mcpInstall Zen Pulse
Install the public CLI from npm. This gives every developer the same local capture workflow.
npm install -g zen-pulse@latestConnect the CLI
Choose the brain where development history should be stored.
zen-pulse connectInitialize a project
Give the repository a stable project identity so future sessions attach to the same project.
zen-pulse init --name "Your Project Name"Run Codex through Zen Pulse
When the session ends, Zen Pulse captures the useful summary, evidence, and project timeline.
zen-pulse codexSync queued work
If a session was offline or authentication was refreshed, flush the queue.
zen-pulse flushWhy it matters
Your AI work becomes product memory.
Zen Pulse is not only logging activity. It stores clean notes, project events, milestones, and marketing-ready opportunities so future answers and future content can reference what actually happened.
Remember what changed
Codex sessions become durable project knowledge instead of disappearing in terminal history.
Answer from real evidence
Zen can retrieve indexed pages, chunks, and source context from the brain selected by the user.
Create from actual progress
Project Pulse can recommend product updates and marketing posts from real development milestones.
Documentation
The path is explicit.
A normal developer should know exactly what to do: connect MCP, install the npm package, connect Zen Pulse, initialize the project, run Codex, then flush if needed.
# 1. Connect Codex to the XandaCross MCP server
codex mcp add xandacross --url https://xandacross.himeshbhowmik.com/mcp
codex mcp list
# 2. Install Zen Pulse from npm
npm install -g zen-pulse@latest
# 3. Connect the CLI to your selected brain
zen-pulse connect
# 4. Give this repo a stable project identity
zen-pulse init --name "Your Project Name"
# 5. Run Codex through Zen Pulse
zen-pulse codex
# 6. Sync any queued events
zen-pulse flush
zen-pulse status