← ClaudeAtlas

aweswitchlisted

Use when helping users manage aweswitch profiles — adding, editing, or switching Claude Code, Codex, and OpenCode API configurations, plus official-login accounts (Claude Code / Codex OAuth). 中文触发词:切换profile、添加profile、配置aweswitch、API切换、provider管理、官方帐号、多帐号切换、account管理。
Webioinfo01/aweswitch · ★ 28 · AI & Automation · score 74
Install: claude install-skill Webioinfo01/aweswitch
# aweswitch This skill covers **configuring** aweswitch profiles and applying them to settings. ## Do Not Launch **Never run `aweswitch <profile-name>` inside this agent.** It launches an interactive agent via `execvpe`, which would nest an agent inside an agent. If the user wants to launch a profile, tell them to run it in their own terminal. ## Two Modes aweswitch has two ways to switch profiles. This agent can only help with **Apply mode**; launches must be run by the user. ### Launch mode — `aweswitch <profile>` (user only, not for this agent) Launches a new session with isolated env. Each session is independent. User runs this themselves in a terminal. **Do not run or suggest running this inside the agent.** ### Apply mode — `aweswitch apply [profiles...]` (this agent can do this) Writes profiles into each agent's own config as the persistent default: - Claude → env in `~/.claude/settings.json` (undo with `aweswitch config restore`) - Codex → provider + model in `~/.codex/config.toml` (first apply creates a `.toml.bak` backup; the API key stays in the environment via `env_key`) - OpenCode → provider entry + full model list upserted into `~/.config/opencode/opencode.json` (overwritten if the provider exists, added if missing); `aweswitch apply --opencode` does every OpenCode profile. Managed provider keys are recorded in `.aweswitch-managed-providers.json`; after renaming/deleting a tracked profile, apply warns about its leftover provider entry (old sessions sta