If you use both Claude Code and Codex CLI but want one bounded API budget, this guide shows the minimum configuration for each client, how to keep their credentials from colliding, and how to verify the setup before either agent reads a large repository.
AceDataCloud Coding Plan is currently a 30-day, Credit-metered multi-model API package. The entry tier, Coding Plus, has a ¥99 display anchor and a US price of $14.645677. It currently includes 500 Credits—400 base plus a 100-Credit bonus scheduled to end November 30, 2026 (UTC+8). This is not an official Claude or OpenAI consumer membership, and it is not unlimited. Usage deducts Credits based on items such as uncached input, output, cache writes, and cache reads.
Why separate the two client configurations?
Claude Code and Codex are both terminal coding agents, but they do not use interchangeable configuration:
- Claude Code expects the Claude Messages workflow and reads Anthropic-style environment variables.
- Codex CLI can use an OpenAI Responses-compatible provider defined in
~/.codex/config.toml. - A model appearing in a live catalog does not guarantee that every client and protocol can call it.
The safest design is one Coding Application token stored in an environment variable, with each client pointed at the endpoint and protocol it actually understands. Do not paste the token into a repository or commit a local settings file containing it.
Configure Claude Code
Install Claude Code using its current official installation method, then confirm the binary is available:
claude --version For macOS or Linux, add the following to your shell profile, replacing the placeholder with the token from your Coding Application:
export ANTHROPIC_BASE_URL="https://api.acedata.cloud" export ANTHROPIC_AUTH_TOKEN="YOUR_CODING_APPLICATION_TOKEN" unset ANTHROPIC_API_KEY Reload the shell:
source ~/.zshrc # or source ~/.bashrc The unset line matters. If an old ANTHROPIC_API_KEY remains in the environment, Claude Code may use the wrong credential or produce confusing authentication behavior. Do not set it to an empty string; remove it.
If you need project-local configuration, use .claude/settings.local.json and make sure it is ignored by Git:
{ "env": { "ANTHROPIC_BASE_URL": "https://api.acedata.cloud", "ANTHROPIC_AUTH_TOKEN": "YOUR_CODING_APPLICATION_TOKEN" } } Environment variables or an OS secret manager are preferable for a real token.
Configure Codex CLI
Install Codex and expose the same Coding Application token under a client-specific variable:
npm install -g @openai/codex export ACEDATACLOUD_API_KEY="YOUR_CODING_APPLICATION_TOKEN" Then add this provider to ~/.codex/config.toml:
model_provider = "acedatacloud" [model_providers.acedatacloud] name = "acedatacloud" base_url = "https://api.acedata.cloud/v1" [model_providers.acedatacloud.auth] command = "sh" args = ["-c", "echo $ACEDATACLOUD_API_KEY"] This keeps the secret out of the TOML file. On Windows, use the PowerShell command form from the dedicated Codex guide rather than the sh snippet.
You do not need to hard-code a model in this minimal configuration. Start Codex, run /model, and choose an exact model ID that is currently compatible with the provider and your credential.
Verify before opening a real repository
First check authentication and inspect the live directory:
export ACE_CODING_TOKEN="YOUR_CODING_APPLICATION_TOKEN" curl --fail-with-body https://api.acedata.cloud/v1/models \ -H "Authorization: Bearer $ACE_CODING_TOKEN" Use a returned id as a model name, but treat the directory as discovery—not proof that every model works through every protocol. The credential's API scope and the client's compatibility still apply.
Next, use a disposable repository with a tiny task:
mkdir coding-plan-smoke-test && cd coding-plan-smoke-test git init printf '# Smoke test\n' > README.md git add README.md && git commit -m "initial fixture" Run each client separately and ask it to read README.md and summarize it without modifying files. Then check:
git status --short A clean result verifies that the client launched, reached the provider, and completed a bounded read-only task. It is not a speed or quality benchmark.
For Codex, also run /model and confirm the provider is acedatacloud. For Claude Code, if you receive 401, inspect the effective environment:
printf '%s\n' "$ANTHROPIC_BASE_URL" test -n "$ANTHROPIC_AUTH_TOKEN" && echo "auth token is set" test -z "$ANTHROPIC_API_KEY" && echo "legacy key is unset" Never print the token itself.
Budget the first 30 days from observed tasks
Do not translate Credits into a fixed number of prompts. A one-line documentation edit and a repository-wide refactor can have very different context, output, caching, tool, and retry costs.
Instead, measure three workload classes during the first week:
| Class | Example | What to record |
|---|---|---|
| Small | Explain one function | Client, model, Credits used |
| Medium | Add tests for one module | Context size, retries, Credits |
| Large | Plan a cross-file refactor | Tools, cache behavior, total Credits |
Use the smaller tier to validate your actual pattern, then choose a larger allowance only if the measurements justify it. All current tiers have the same Coding model access scope; they primarily differ in included Credits.
Renewing before expiry carries remaining Credits forward and extends the term by 30 days. If the plan expires first, unused Credits expire. There is no automatic renewal and no automatic fallback to the general balance.
The practical takeaway
Sharing a budget does not mean sharing one generic configuration. Keep Claude Code on its Claude-native environment variables, give Codex its own provider block, remove conflicting legacy credentials, and test both against a disposable repository. That small separation makes authentication errors easier to diagnose and gives you clean usage data for choosing the next 30-day tier.
Current packages are listed on the AceDataCloud Coding Plan page. For client-specific updates, use the Coding Plan configuration center, the Claude Code CLI guide, and the Codex CLI guide. Plan boundaries and positioning are also documented in Ace Data Cloud's ¥99 plan explainer and multi-client overview.

