Agent providers
Configure Codex or Claude and understand the provider boundary.
Tasuku supports CODEX and CLAUDE. Select the provider, optional model, and default reasoning effort at instance scope or as a repository override.
Provider authentication
The chosen CLI must be installed in the selected agent runtime. In Settings → Agent, paste the provider's subscription credential while saving the agent configuration:
- For Codex, first enable Device code authorization for Codex in ChatGPT's security settings. Then select Connect ChatGPT, open the OpenAI authorization page, and enter the one-time device code. Tasuku encrypts the resulting credential without returning it to the browser. If device authorization is unavailable, expand Use auth.json instead and paste the complete
~/.codex/auth.json. - Claude expects an OAuth token.
Tasuku stores these as the encrypted CODEX_AUTH_JSON or CLAUDE_OAUTH_TOKEN secret and never returns plaintext. The bundled runtime images install both tools and inject only the selected credential while an agent runs. On a repository page, choose Reuse instance credential or Use repository credential; the latter creates a repository-scoped override.
Leaving the credential field blank preserves the existing secret. Credentials are not part of the configuration JSON returned by the API.
Subscription usage
After saving the provider and credential, the Review agent card shows the usage windows returned by that subscription. These commonly include a five-hour and weekly limit. Monthly spend, extra-usage, or model-specific limits appear only when the provider returns them.
Usage snapshots are cached for one minute and refreshed by the dashboard every five minutes. Use Refresh to request a current snapshot. Tasuku reads usage without refreshing or rewriting the saved OAuth credential; replace the credential if the panel reports an authentication failure.
Repository usage follows the same precedence as review runs: a repository credential overrides the instance credential, otherwise the instance credential is reused.
Codex usage follows the provider's current usage contract. Claude usage relies on the private machine-readable endpoint used by Claude Code, so a Claude CLI or service change may temporarily make the panel unavailable without affecting review runs.
Invocation context
Tasuku supplies the provider with:
- the primary repository at the workflow's exact commit;
- approved secondary repositories mounted read-only;
- workflow instructions and repository policy;
- custom instructions and enabled learnings;
- provider-specific skill packaging;
- configured HTTPS MCP servers.
The provider does not receive GitHub App credentials. It produces structured output or a bounded workspace artifact for the worker to validate.
Model selection
An empty model value leaves model selection to the installed provider's default. A non-empty value is passed as provider configuration. Confirm it is supported by the CLI version in your runtime image.
Tasuku includes gpt-5.6-sol in the Codex model suggestions. The reasoning selector exposes the levels supported by the selected provider CLI:
low,medium,high,xhigh, andmaxfor current Codex 5.6 models and current Claude Code;low,medium,high, andxhighfor Codex models that do not supportmax.
medium is the default for ordinary work. Research workflows use Codex gpt-5.6-sol with high reasoning, while requests the conversation router classifies as deep research use xhigh. These workflow overrides apply regardless of the saved provider, model, or reasoning default and do not change that saved default. ultra is not exposed because it is a Codex subagent mode, not a reasoning-effort level.
Behavior and instructions
The Instructions tab controls the agent's communication and working style. DEFAULT is neutral and concise; FRIENDLY, PRAGMATIC, and NERDY apply Tasuku's built-in guidance. CUSTOM requires up to 4,000 characters of custom behavior guidance. Additional instructions are appended after the selected behavior.
Behavior and additional instructions inherit together as the repository's instructions category. They influence presentation and approach, but do not weaken diff validation, path exclusions, permissions, publication limits, or approval gates.
Overrides
Use a repository override when one codebase needs a different provider, model, or reasoning default. Keep the override disabled when it should track instance changes. See Inheritance and overrides.