Providers
ShioriCode supports multiple AI providers. Each provider runs as an independent session that streams events back to your workspace.
How Providers Work
When you start a turn, ShioriCode launches a provider session for your thread. All activity is persisted and pushed to your browser in real time.
You can switch providers between turns - each thread tracks which provider was used for each turn.
Billing & Subscriptions
ShioriCode does not bill you for model usage itself - each provider uses your own subscription with that vendor:
- Codex runs against your ChatGPT / OpenAI subscription via the locally authenticated Codex CLI. Usage counts toward that plan.
- Claude runs against your Claude / Anthropic subscription via the locally authenticated Claude CLI. Usage counts toward that plan.
- Gemini runs against your Google account or Google Cloud project via the locally authenticated Gemini CLI. Usage counts toward that plan.
- Cursor runs against your Cursor subscription via the locally authenticated Cursor agent CLI. Usage counts toward that plan.
- Kimi Code runs against your Moonshot / Kimi account via the locally authenticated Kimi CLI. Usage counts toward that plan.
- Shiori runs against your paid Shiori subscription. Usage counts toward your Shiori plan limits.
Access to ShioriCode itself requires an active paid Shiori subscription, regardless of which provider you use.
Codex
OpenAI's Codex is the default provider. ShioriCode manages Codex sessions automatically.
Billing: Codex uses your own ChatGPT / OpenAI subscription - ShioriCode simply drives the locally authenticated CLI. All usage counts toward your OpenAI plan, not your Shiori plan.
Setup
- Install the Codex CLI globally and ensure it's on your PATH
- Run
codex loginto authenticate - ShioriCode auto-detects the binary - no further configuration needed
Settings
| Setting | Description |
|---|---|
enabled | Enable or disable the Codex provider |
binaryPath | Custom path to the Codex binary (auto-detected by default) |
homePath | Custom Codex home directory |
customModels | Additional model IDs to make available |
Claude
Anthropic's Claude provides conversational coding assistance with tool use capabilities.
Billing: Claude uses your own Claude / Anthropic subscription - ShioriCode simply drives the locally authenticated CLI. All usage counts toward your Anthropic plan, not your Shiori plan.
Setup
- Install the Claude CLI and ensure it's on your PATH
- Authenticate with your Anthropic credentials
Settings
| Setting | Description |
|---|---|
enabled | Enable or disable the Claude provider |
binaryPath | Custom path to the Claude binary |
customModels | Additional model IDs to make available |
Gemini
Google's Gemini coding agent runs through the locally installed Gemini CLI. ShioriCode launches sessions against your authenticated CLI.
Billing: Gemini uses your own Google account or Google Cloud project - ShioriCode simply drives the locally authenticated CLI. All usage counts toward that plan, not your Shiori plan.
Setup
- Install the Gemini CLI and ensure it's on your PATH
- Authenticate with your Google account (or supply a Google Cloud project)
- ShioriCode auto-detects the binary - no further configuration needed
Settings
| Setting | Description |
|---|---|
enabled | Enable or disable the Gemini provider |
binaryPath | Custom path to the Gemini CLI binary (defaults to gemini) |
googleCloudProject | Optional Google Cloud project to bill usage against |
acpFlag | Override flag used when launching the CLI in agent-control mode |
customModels | Additional model IDs to make available |
Cursor
Cursor's background coding agent (Composer) runs through the locally installed Cursor agent CLI. ShioriCode launches sessions against your authenticated CLI.
Billing: Cursor uses your own Cursor subscription - ShioriCode simply drives the locally authenticated CLI. All usage counts toward your Cursor plan, not your Shiori plan.
Setup
- Install the Cursor agent CLI and ensure it's on your PATH (the binary is named
agentby default) - Sign in to Cursor through the CLI so the credentials are cached locally
- ShioriCode auto-detects the binary - no further configuration needed
Settings
| Setting | Description |
|---|---|
enabled | Enable or disable the Cursor provider |
binaryPath | Custom path to the Cursor agent binary (defaults to agent) |
apiEndpoint | Override API endpoint (advanced; leave empty to use the default) |
customModels | Additional model IDs to make available (for example, composer or composer-2) |
Kimi Code
Moonshot's Kimi coding agent runs through the locally installed Kimi CLI. ShioriCode launches sessions against your authenticated CLI.
Billing: Kimi Code uses your own Moonshot / Kimi account - ShioriCode simply drives the locally authenticated CLI. All usage counts toward that plan, not your Shiori plan.
Setup
- Install the Kimi CLI and ensure it's on your PATH (the binary is named
kimiby default) - Authenticate with your Moonshot / Kimi credentials
- ShioriCode auto-detects the binary - no further configuration needed
Settings
| Setting | Description |
|---|---|
enabled | Enable or disable the Kimi Code provider |
binaryPath | Custom path to the Kimi CLI binary (defaults to kimi) |
shareDir | Optional shared directory the CLI uses for cached state and session artifacts |
customModels | Additional model IDs to make available |
Shiori
The Shiori provider is managed by your Shiori account. It requires no local binary, but access currently requires an active paid Shiori subscription.
Billing: The Shiori provider uses your paid Shiori subscription. Usage counts toward your Shiori plan limits - no separate vendor account needed.
Setup
- Sign in with your Shiori account from the ShioriCode settings
- Make sure your account has an active paid Shiori subscription
- The model catalog is fetched automatically
Settings
| Setting | Description |
|---|---|
enabled | Enable or disable the Shiori provider |
apiBaseUrl | Custom API base URL (for self-hosted deployments) |
Runtime Modes
Regardless of provider, you can choose a runtime mode for each session:
- Full access - The agent executes commands without asking for approval. Best for trusted workflows.
- Supervised - The agent requests approval before executing commands.
Toggle the runtime mode from the chat toolbar before starting a turn.
MCP Servers
ShioriCode supports the Model Context Protocol for extending provider capabilities with external tools. Configure MCP servers in the server settings to make them available to all providers.