Skip to main content
Nasiko treats Codex as a coding harness. Discovery and session reporting use Codex hooks. Model routing adds a Nasiko provider to Codex’s config.toml. No wrapper, no SDK in your code.

​
Discover and report

Install writes Nasiko command hooks into Codex’s hooks config and a launcher under the Codex config directory. Existing hooks stay.
Open Codex, run /hooks, and trust the new Nasiko command hooks. Codex will not fire them until you do.
Codex turns arrive across several hook events. Nasiko assembles them under ~/.nasiko/integrations/events/ and queues a turn once it is complete. See Session reporting.

​
Route models

connect codex edits {CODEX_HOME}/config.toml:
  • model_provider = "nasiko"
  • [model_providers.nasiko] with wire_api = "responses" and base_url = {cluster}/v1
  • Command-based auth that runs nasiko __coding-agent-token codex
Codex talks OpenAI Responses (POST /v1/responses). Nasiko translates and routes to the provider in your config. Codex refreshes the JWT on a timer rather than minting one per request. Connection state is stored in ~/.nasiko/integrations/codex-router.json.

​
Disconnect and uninstall

The two are independent.

​
Identity in Nasiko

Registration creates a coding-agent identity named <username>-codex, labelled Codex (<your email>) in the dashboard.

​
Troubleshooting

More: Troubleshooting and Route models.