codex-multi-subscription-auth-fallbacks_skill

This skill enables seamless multi-provider Codex authentication with automatic failover, profile management, and optional cron-based model switching for
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill codex-multi-subscription-auth-fallbacks

  • _meta.json333 B
  • SKILL.md5.9 KB

Overview

This skill sets up multi-provider authentication for OpenClaw with OpenAI Codex OAuth fallback profiles and automatic model switching. It helps import multiple Codex OAuth sessions via device-flow, configure provider failover order, and optionally deploy a cron job that auto-switches models when a provider is on cooldown. Use it to achieve seamless rate-limit failover across multiple OpenAI Codex accounts.

How this skill works

The supplied scripts perform a safe device-flow login for each OpenAI account, extract access and refresh tokens from the Codex CLI auth file, and write timestamped backups before updating OpenClaw's auth-profiles.json. OpenClaw is then configured with profile order and model fallbacks so it will retry other profiles when one hits a rate limit. An optional cron job polls model cooldown state and updates the active model automatically when needed.

When to use it

  • You run multiple OpenAI Codex accounts and want automatic failover when one hits rate limits.
  • You need to add new Codex OAuth profiles reliably using device-flow (browser-based) login.
  • You want OpenClaw to prefer one model/provider but transparently switch when it hits cooldown.
  • You plan to run a scheduled job that monitors cooldowns and flips models without manual intervention.
  • You want local-only token handling with safe backups during profile import.

Best practices

  • Back up ~/.codex/auth.json and OpenClaw config files manually before the first run, even though the script creates timestamped backups.
  • Test the add-profile script with a non-production account first to verify the flow and restores.
  • Give short, clear profile names (e.g., usernames) so fallback order and logs remain readable.
  • Verify openclaw models status manually before enabling the cron job to confirm profiles are working.
  • Limit cron auto-switching to environments where automatic model changes are acceptable, and monitor its logs for unexpected switches.

Example use cases

  • Import three OpenAI Codex accounts to provide continuous capacity for a high-throughput agent and let OpenClaw fail over across them.
  • Add a newly provisioned Codex OAuth profile via device-flow when an account is rotated or newly purchased.
  • Deploy a 10-minute cron job that monitors cooldowns and promotes the best available model to minimize latency interruptions.
  • Set provider priority so Anthropic or a preferred Codex session is tried first, then fall back to other Codex profiles when needed.
  • Maintain local-only token handling while consolidating multiple provider sessions into OpenClaw's auth-profiles structure.

FAQ

No. Tokens are read from your local Codex CLI auth file and written only to your local OpenClaw auth-profiles.json. The script never transmits tokens to external endpoints.

Will the script destroy my existing Codex CLI tokens?

No. The script creates timestamped backups and restores the original Codex auth file if the flow is interrupted. It prompts for confirmation before clearing the CLI auth file.

Is the automatic model switching mandatory?

No. The cron-based auto-switch is optional. OpenClaw's built-in failover works without it; the cron job only automates proactive model selection based on cooldown state.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational