Brings Claude Code to parity with the Codex CLI integration.
- `omniroute launch` is now remote-aware: --remote <url>, --profile <name>,
--api-key. Resolves base URL + auth from the active context (so
`omniroute connect <vps>` then `omniroute launch` just works), accepts a bare
port OR a full base URL, health-checks the (possibly remote) server, and sets
CLAUDE_CONFIG_DIR for the chosen profile.
- `omniroute setup-claude` (new): fetches the live /v1/models catalog and writes
~/.claude/profiles/<name>/settings.json per model. Claude Code has no native
profile files, so CLAUDE_CONFIG_DIR is the idiomatic mechanism. Reuses the SAME
profile names as setup-codex (glm52, kimi-k27, …) via the shared categoriseModel
(now exported). The auth token is NEVER written to disk — launch injects it.
- Docs: docs/guides/CLAUDE-CODE-CONFIGURATION.md + README index. i18n (en + pt-BR).
- Tests: setup-claude profile generation (incl. "no token on disk"), buildClaudeEnv
(port + URL + CLAUDE_CONFIG_DIR), resolveLaunchTarget.
check:cli-i18n + check-docs-sync green; 13 unit tests pass.
* feat(cli): Codex CLI launcher + setup commands
Two new CLI subcommands mirroring the `launch`/`configure` pattern, for driving the
OpenAI Codex CLI against OmniRoute:
- `omniroute launch-codex` — boots OmniRoute (if needed) and launches Codex CLI
pointed at it (local or remote VPS), with no manual env/config editing.
- `omniroute setup-codex` — generates ~/.codex profile files from OmniRoute's live
model catalog.
Registered in the command registry; en.json + pt-BR.json locale sections added
(keeps the cli-i18n-catalog top-level parity gate green). CODEX-CLI-CONFIGURATION.md
refreshed. Consolidated from work-in-progress that was uncommitted on the shared
checkout; reconstructed on release/v3.8.30.
* chore(vscode): reduce git repo-detection overhead for nested worktrees
Disable VS Code's git auto-repository-detection / submodule scan / autofetch so the
Source Control view stops indexing the ~44 nested repos (worktrees + _references/*
+ _mono_repo/*), which caused constant "validating" churn. Only the root repo is
tracked. Editor-only settings; no runtime impact.
