Connect Codex.

One-time setup

Before you start

• Node.js 22.13 or later and Codex on the same computer. Check node --version in Terminal or PowerShell.
• This guide configures a local Codex host. The app, CLI and IDE extension can share that host’s MCP configuration; a cloud task or another computer needs its own setup.
• The beta has been exercised with real Codex conversations on macOS. Windows installation, permissions, recovery and host recall still need native Windows verification.

Compare the outer ZIP with the downloadable SHA-256 checksum. After extracting it, compare ubimemo-connect-0.3.0-beta.1-standalone.tar.gz with its entry in the included SHA256SUMS before running it. The archive includes JavaScript dependencies; Node is installed separately.

01 / PROJECT

Choose your setup

Without an account: Quickstart creates a private Lite project named My memories and a key restricted to that project. No email, browser signup or manual API key entry is needed. You can register later and keep the same project.

With an account: Sign in or register, then choose a Lite project using the account setup steps. If you already have a guest project, register that project instead of replacing it.

A valid existing connection is reused. Connecting does not enroll local memory sources or upload conversations. Keep the existing private state if setup is interrupted; retry the same command.

02 / INSTALL

Install the package

Start in the extracted download folder. Run one command at a time and stop on any error. Check the hash before extracting the standalone archive.

shasum -a 256 ubimemo-connect-0.3.0-beta.1-standalone.tar.gz
# Compare with SHA256SUMS. Stop if the hash differs.
# Only after it matches:
tar -xzf ubimemo-connect-0.3.0-beta.1-standalone.tar.gz
cd ubimemo-connect-0.3.0-beta.1-standalone
node install.mjs
node install.mjs verify

Get-FileHash .\ubimemo-connect-0.3.0-beta.1-standalone.tar.gz -Algorithm SHA256
# Compare with SHA256SUMS. Stop if the hash differs.
# Only after it matches:
tar -xf .\ubimemo-connect-0.3.0-beta.1-standalone.tar.gz
Set-Location .\ubimemo-connect-0.3.0-beta.1-standalone
node .\install.mjs
node .\install.mjs verify

The installer prints the installed release path. Change into that directory before running any node server.mjs commands below. Default locations:

• macOS~/.local/share/ubimemo-connect/releases/0.3.0-beta.1
• Windows%LOCALAPPDATA%\UbimemoConnect\releases\0.3.0-beta.1

Keep that directory in place: Codex will launch the installed server by its absolute path. The package also includes a WorkBuddy connector and skill; Codex uses the managed installer in the next step. A printed workbuddy_registration: required message does not require a WorkBuddy setup.

03 / CONNECT

Connect Codex and add its instructions

Start without an account

From the installed release directory, run:

node server.mjs quickstart --client codex

The helper creates or reuses your connection, saves and reads back a synthetic setup memory, and adds the Codex connector and its standing instructions. If the service reports guest setup is unavailable, keep the saved request and retry when it is enabled, or deliberately choose account setup.

Start a fresh Codex chat and complete the host’s tool approvals. Default installation preserves your permission policy and native memory settings. In the Codex CLI, /mcp shows active servers; codex mcp list checks configured servers. See the official Codex MCP documentation.

Connect with an account

1. Sign in or create an account and complete email verification.
2. In Account → API keys, create a key for this connection. Account-wide keys can access your account’s projects; keep them private.
3. Install the package, then open your own interactive terminal in the installed release directory. Run node server.mjs setup. Enter the API key at the hidden prompt and select an existing Lite project, or enter a name to create one. Setup uploads no files.
4. Run node server.mjs install to add the Codex connector and managed instructions. Start a fresh chat and complete the host’s tool approvals.

node server.mjs setup
node server.mjs install

Run these commands one at a time. API keys go only into the hidden terminal prompt, never into chat, command arguments or a repository. If the terminal is not interactive, open Terminal or PowerShell yourself. Reuse an existing connection; use registration to keep an existing guest project and its memories.

04 / VERIFY

Check recall in a fresh chat

Confirm Codex has sync_memories, search_memories, read_memory and save_memory. Guest quickstart already saves and reads a synthetic setup memory. For account setup, ask Codex:

Save this synthetic setup memory in Ubimemo once: “Ubimemo setup check: the synthetic Cedar notebook is teal.” Then read it back and verify the exact text.

For a retry, reuse the same operation ID and exact text. Then start another fresh Codex chat and ask without supplying the answer:

What color is the synthetic Cedar notebook from our setup check?

1. Finds and reads the memoryCodex searches the selected project, then reads the returned document with its revision ID and hash.
2. Answers accuratelyIt answers “teal” using the saved memory, without you pasting the answer or asking it to read local files.
3. Shows its sourceIt cites the hosted memory so you can check the original.

Installed tools, an accepted save, an exact read, search readiness and demonstrated fresh-chat recall are separate checks. If search is still processing, retry later; a successful save alone does not prove recall.

Optional

Bring selected native memories with you

Saving and recall work without native-memory sync. If you want to sync existing Codex memories, first review the actual memory folder on this computer and explicitly choose it. Replace the example path below with that reviewed absolute path.

node server.mjs enroll-codex --memory-root "/absolute/path/to/reviewed/codex-memory-root"

Enrollment uploads nothing. The supported folder contains rollout_summaries/ and/or extensions/ad_hoc/notes/. Only Markdown files in those selected sources are eligible. Aggregate memory_summary.md, raw session transcripts, symlinks and other files are excluded. A rollout summary remains a summary; it is not the full conversation.

After reviewing the sources, you can run one initial bounded sync:

node server.mjs sync --force
node server.mjs status

During substantive work, the managed instructions ask Codex for one quiet due check. By default, a sync handles up to 10 changed files within a 45-second budget; the due interval is 15 minutes. Pending files wait for a later pass. This runs during active chats, with no background watcher. Files generated later can be collected in a subsequent chat.

Native Codex memory continues separately. If no new summaries appear, review Codex’s generation and use settings, including tool-assisted chats and the chat’s /memories choices. Generation depends on Codex eligibility and timing. See Codex memories.

Sync keeps revisions of changed originals. Removing a local file does not delete its hosted memory. Remote edits that conflict with the expected revision stop that file’s update for review.

Register later and keep your memories

1. From the installed release directory, run node server.mjs register start and open its short-lived link.
2. Register or sign in, then choose the destination account in the browser.
3. Run node server.mjs register status. Check the verified email and project and explicitly confirm that exact destination.
4. Only then run node server.mjs register confirm --account-id ID --confirmation-id ID, using the exact values from status. If the destination changes, check and confirm again.

Creating an account alone does not attach the guest project. Registration preserves the project, memories, valid keys and pending imports. Links expire after 30 minutes; an interrupted or expired registration leaves guest access intact. Run register start again to resume.

Guests can retain 1,000 memories and 25 MiB, including retained versions and pending uploads. At capacity, reads continue while new intake pauses until registration. Guest data is not automatically deleted. Register before connecting another computer.

After setup

Keep working. Let context follow.

Ask Codex about earlier decisions, preferences or project context in ordinary language. Its instructions guide it to search selectively, read the relevant original, and cite what it used. Saved notes, imports and other connected tools can contribute to the same Ubimemo project.

To keep a new decision, ask “Save this decision in Ubimemo.” Explicit saves need no native source enrollment. Successful routine sync checks stay quiet; actionable failures should let ordinary work continue.

If something needs attention

Troubleshooting

node server.mjs doctor
node server.mjs status

Download mismatch or server will not start

Stop on a checksum mismatch and download a fresh copy. Check Node 22.13+, verify the installed package with install.mjs verify from the extracted archive, and keep the installed server path in place.

Tools are missing or a call is denied

Start a fresh chat and check the active MCP server and host approvals. A host can allow search/read while denying sync/save. Complete the relevant permission step; do not weaken the host’s general policy or report a denied call as successful.

No recall or no_sources

No enrolled sources is expected after setup; explicit save and recall still work. Confirm the selected project, check search readiness, and make sure the managed instructions are present. Read the search result’s exact revision before answering.

Guest setup unavailable or a destination conflict

Preserve the saved request and configuration. Retry when guest provisioning is enabled, or deliberately choose account setup. Resolve an ambiguous destination before continuing; do not reset state or create another profile to bypass it.

Key expired or revoked

Guest integration keys expire after 90 days. Before registration, explicitly run node server.mjs quickstart --client codex --replace-expired to replace an expired key. Revoked keys are not silently recreated. After registration, replace that integration key in Account settings and enter it with node server.mjs reconnect --client codex in a private interactive terminal.

Busy, pending or temporarily rate limited

Keep private state, honor Retry-After and retry later. Another call may own the lock, a file may still be changing, or the bounded call may have ended. Do not delete locks or run catch-up loops in ordinary chats.

Remote revision conflict

Keep the receipt and compare the local file with the hosted history. Do not reset source identities or force an overwrite. Resolve the intended content deliberately before resuming that source.

Disconnect Codex

From the installed release directory, run node server.mjs uninstall. It removes its owned MCP and instruction additions while preserving unrelated settings, native memories, hosted data and private connection state. Edited managed blocks cause a refusal so your changes can be reviewed. Revoke the API key separately if you want to end service access.