Bring your team's graph into Codex CLI.

Install the Oynix CLI

Everything Oynix does runs from one small command-line tool on your own machine — there's nothing to deploy or host. Open your terminal (Terminal on Mac, PowerShell on Windows) and paste this in to install it:

• Don't have a terminal open? On Mac press ⌘+Space, type "Terminal", hit Enter.
• Paste the line, press Enter, and wait for it to finish — that's it.
• Check it installed: run oynix --version (it should print a version number).

Sign in

Tell Oynix who you are. This opens your browser to sign in with GitHub and links this computer to your workspace — it's how your edits, decisions and presence get attributed to you.

• Run the command; your browser opens automatically.
• Approve the sign-in with GitHub, then return to the terminal.
• If your team uses a workspace key, paste it when asked (a teammate with the master key issues it).

Generate the config

Run setup for Codex CLI. Oynix prints a small config snippet (already filled in for you) and tells you exactly where it goes — your secret stays a reference, never written into the file.

• Run the command in your terminal.
• Copy the snippet it prints out (it includes the copy button here too).

Paste it into the config

Open ~/.codex/config.toml and paste the snippet, then save.

• Where: ~/.codex/config.toml.
• If the file already lists other MCP servers, add ours alongside them (don't delete theirs).
• If the file doesn't exist yet, create it and paste the snippet in.

Restart & connect

Fully quit and re-open Codex CLI so it loads the new server. That's it — it now answers from your team's real graph.

Check it works

Open Codex CLI and ask it something about your codebase — for example, "how does login work?". If it answers using your actual code and decisions, you're connected.

• Make sure Codex CLI was fully restarted after you pasted the config.
• Not answering from your code? Re-open the config file and confirm the snippet is there and saved.