Getting started
Set up your AI coding tools
Connect Codex, Claude Code, Claude Desktop and OpenCode with the XEDOC setup assistant on Windows, macOS or Linux.
Before you run it
#- Node.js 20 or newer. Download the current LTS from nodejs.org.
- An API key from your XEDOC workspace.
- A current version of each client you want to connect. Codex command authentication is verified with Codex CLI 0.153.4.
- Desktop clients must be closed while their configuration changes. If one is running, the assistant offers to close it for you.
Install and start
#This downloads the newest XEDOC package, installs the xedoc command for your user and starts the assistant. The link always points to the current version. On Windows, npx.cmd also works when PowerShell blocks npx.ps1.
npx.cmd --yes https://xedoc.top/downloads/xedoc-setup-latest.tgznpx --yes https://xedoc.top/downloads/xedoc-setup-latest.tgznpx --yes https://xedoc.top/downloads/xedoc-setup-latest.tgzEnter your XEDOC key
Paste the key when asked. Input is hidden. Press Enter after pasting. If a key is already saved, press Enter to keep it or C to change it.
Choose your clients
Select one or more clients, or press A for all. The assistant fetches the current model catalog and prepares the appropriate configuration for each.
Review and apply
Review the destination files. Existing configurations are backed up before changes are applied.
Reopen your client
Choose the XEDOC provider or a model, then start a new conversation.
Start it again with xedoc
#After the first run, type xedoc in a new terminal. Each start checks for a newer version and updates itself, shows your status, adds new models to connected clients when automatic model updates are on, and then opens the menu. Without a connection it continues with the installed version after a few seconds.
xedocxedocxedocIf a selected client is running, the assistant asks whether to close it so the new configuration takes effect, and asks once whether to always do this. It also asks once whether new models should be added automatically on each start.
Select clients directly with --clients, for example xedoc --clients codex-app, or use --clients all.
xedoc not found?
xedoc.cmd in the npm folder on your PATH, or in %LOCALAPPDATA%\xedoc\bin, which setup adds to your user PATH. On macOS and Linux it is placed in ~/.local/bin or another user folder on your PATH. The npx command above always works as well.Change settings with xedoc set
#xedoc setxedoc setxedoc setChange your API key, automatic closing of running apps, automatic model updates, automatic self-updates and your default clients. A new key is checked before it is saved, and every change is saved immediately.
For scripts, use --auto-close, --no-auto-close, --auto-models and --no-auto-models. With --yes, the assistant never asks and only closes running apps when automatic closing is on.
What the assistant configures
#| Client | Connection | Selection |
|---|---|---|
| Codex CLI | A separate XEDOC profile and model catalog | Start with codex --profile xedoc |
| Codex App | The shared Codex configuration, XEDOC catalog and private credential helper | Restart the app and choose a model |
| Claude Code | XEDOC environment settings and model aliases | Use /model |
| Claude Desktop | A named XEDOC inference configuration | Restart and open the Code tab |
| OpenCode | An XEDOC provider with the current model list | Use /models |
The assistant preserves unrelated settings. It never replaces Codex auth.json. Private credential files and backups stay on your computer; setup does not send them to XEDOC. Only the supplied key is sent to the XEDOC API to validate access and retrieve models.
Change a key or refresh models
#Run xedoc set to replace your key, or xedoc to refresh client model lists. Use the same selected clients. A repeated setup keeps the existing XEDOC connection instead of creating duplicate providers.
If a client configuration is invalid or changes while setup is running, setup stops rather than overwriting it. Backups are saved in the XEDOC configuration directory shown by the assistant. Linked configuration files require manual setup. Windows and WSL use separate homes; run setup in the environment where your client runs.
Prefer to configure things yourself?
#Each integration guide also includes its connection settings and configuration format. Start with the guide for the client you use.