Providers Reference

Registry

AgentStack currently registers four providers:

• codex
• claude
• opencode
• gemini

Two different layers

Understand providers through two separate layers:

1. hub runtime — profile activate
2. provider materialization — apply

apply writes native config files and local package skills for all supported providers. It also materializes project-root instruction files for claude and gemini when you pass --target-root. It does not yet promise universal instruction-file materialization such as automatically generating every AGENTS.md / other provider surface.

Current truth table

Provider	Native config file	apply local skills	MCP support in adapter	Hub runtime mapping
codex	~/.codex/config.toml	~/.agents/skills/<id>/SKILL.md	Yes	Yes
claude	~/.claude/settings.json	~/.claude/skills/<id>/SKILL.md + <target-root>/CLAUDE.md	Yes	Yes
opencode	~/.config/opencode/opencode.json	~/.opencode/skills/<id>/SKILL.md	Yes	Yes
gemini	~/.gemini/settings.json	~/.gemini/skills/<id>/SKILL.md + <target-root>/GEMINI.md	Yes	Yes

Codex

• native config: ~/.codex/config.toml
• apply also materializes local package skills into ~/.agents/skills/
• MCP servers are translated into Codex TOML sections
• provider-specific extras can be preserved via overrides/settings

Claude Code

• native config: ~/.claude/settings.json
• apply also materializes local package skills into ~/.claude/skills/
• with --target-root, apply can also copy instructions.provider_files.claude into <target-root>/CLAUDE.md
• MCP servers are translated into mcpServers
• settings-based instruction translation still exists, but explicit repo-root CLAUDE.md materialization is now supported in apply

OpenCode

• native config: ~/.config/opencode/opencode.json
• apply also materializes local package skills into ~/.opencode/skills/
• MCP servers are translated into OpenCode config entries

Gemini

• native config: ~/.gemini/settings.json
• apply also materializes local package skills into ~/.gemini/skills/
• with --target-root, apply can also copy instructions.provider_files.gemini into <target-root>/GEMINI.md
• MCP servers and Gemini-specific settings are supported in adapter output

Important boundary

Caution

Instruction-file parity is still partial. Today apply supports explicit repo-root materialization only for claude and gemini; do not assume the same for codex, opencode, or every other provider surface.