check-remove-stored-credentials

Inspect and delete stored OAuth tokens and API keys for provider authentication.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill check-remove-stored-credentials-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-remove-stored-credentials
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/check-remove-stored-credentials
Command: npx skills add https://github.com/catalystctl/catcode --skill check-remove-stored-credentials-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging authentication issues, switching provider accounts, or forcing a re-login, stale OAuth tokens, API keys, and cached model lists can mask changes and cause confusing behavior. This Skill locates exactly where the Catalyst Code harness stores credentials and removes them safely. ## Core Features & Use Cases - Credential Discovery: Lists stored OAuth token files under ~/.config/catalyst-code/oauth/ and shows a masked view of the providers block in config.json without leaking raw secrets. - Targeted Removal: Deletes OAuth token files per provider (Codex, Gemini, Claude/Anthropic, others), removes legacy ~/.gemini/oauth_creds.json, and clears the models cache so stale data does not mask changes. - Use Case: A user switched API keys but the harness still uses the old provider. The Skill removes the stale OAuth file, clears models-cache.json, and instructs a core restart so /login re-runs cleanly. ## Quick Start Check which provider credentials are stored on this machine and remove the Gemini OAuth token so I can log in again.

Frequently Asked Questions about check-remove-stored-credentials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove a stored API key or OAuth token in Catalyst Code?

Delete the provider's OAuth file under ~/.config/catalyst-code/oauth/ (e.g. openai.json, gemini.json, anthropic.json) and remove the api_key or providers entry from config.json. Clear models-cache.json and restart the core, then run /login again.

Where does Catalyst Code store provider credentials?

OAuth tokens live in ~/.config/catalyst-code/oauth/<provider>.json, and pasted API keys plus provider configuration live in ~/.config/catalyst-code/config.json. The harness does not read third-party CLI stores like ~/.codex/auth.json or ~/.claude/.credentials.json.

Why is my new API key not taking effect after changing credentials?

A stale models-cache.json (8-hour TTL) or the running core's in-memory provider cache can mask the change. Delete ~/.config/catalyst-code/models-cache.json and restart the core so discovery and authentication re-run.

Does Catalyst Code read credentials from Claude CLI or Codex CLI?

No. The harness intentionally ignores third-party CLI credential files such as ~/.claude/.credentials.json and ~/.codex/auth.json. Only a legacy ~/.gemini/oauth_creds.json is read once for migration to the new store.

How do I check stored credentials without exposing secrets?

List the oauth directory and use jq to print a masked view of config.json showing provider names, kinds, base URLs, and whether an api_key exists. Never print raw token or key values when inspecting.