SkillFoxx

Nasiko CLI

The Nasiko CLI finds installed Claude Code, Codex, OpenCode and Cursor, tracks their spend and routes calls to models you pick.

  • 11,957 ★ on the repository
  • Last commit
CLI

Broad access

Why this level

  • Connecting edits global Claude Code and Codex settings and changes where model calls go.
  • Hooks send session progress, including prompt text, to the control plane, which also stores provider keys.
All reasons and checks

nasiko-labs/nasikoAuthor:Nasiko-Labs

Install

Manual install

git clone https://github.com/Nasiko-Labs/nasiko.git && cd nasiko && cargo install --path cli/ --force

Rust is required. First run: `nasiko agents discover`.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Connecting edits global Claude Code and Codex settings and changes where model calls go.
  • Hooks send session progress, including prompt text, to the control plane, which also stores provider keys.

This is third-party code. Review the repository files before installing.

What it does

Nasiko, an agent runtime written in Rust, has a `nasiko` command line. `nasiko agents discover` only reads the machine: it shows which harnesses (Claude Code, Codex, OpenCode, Cursor CLI) are found, their versions and config paths. It changes no settings, needs no account and sends nothing off the machine. Two independent opt-ins follow. Session reporting installs through harness hooks with `nasiko agents install <agent>`, and `--no-content` drops prompt and response text. Routing is set up with `nasiko llm-config create` and `nasiko connect claude --config <name>`: Claude Code then goes to the chosen provider, for example OpenAI. `nasiko disconnect <agent>` reverses the settings.

Who it is for. Teams and solo developers who run several coding agents and want spend broken out by harness and model.

Good fit when

  • Claude Code, Codex and OpenCode are installed and it is unclear which are connected.
  • A monthly bill needs a split by agent and model.
  • Claude Code calls should go to an OpenAI key without leaving the familiar harness.
  • Agent session progress should be recorded on your own control plane.

Not a fit when

  • One agent and its vendor bill are enough.
  • Prompt text may not leave the machine even for your own server: enable reports only with `--no-content`.
  • A control plane cannot be run: reporting and routing do not work without it.

Example request

Run nasiko agents discover and show which coding agents are found on this machine and whether they are connected to the control plane.

Limitations

Four harnesses are supported; routing exists for Claude Code, Codex and OpenCode but not for Cursor CLI yet. The CLI builds through `cargo install`, so Rust is required. Reporting and routing need a running control plane (Docker) and a login. Connecting edits global files such as `~/.claude/settings.json` and affects every process of the user, not one project. The README states Apache-2.0, while GitHub metadata shows no license value.

How to disable. Run `nasiko disconnect <agent>` and `nasiko agents uninstall <agent>`, then delete the binary. The event queue lives in `~/.nasiko/integrations/`.

FAQ

What does nasiko agents discover do?

It only reads the machine and prints a table of harnesses with versions and config paths. Nothing changes, no account is needed and no data leaves.

How do I send Claude Code to another provider?

Create a config with `nasiko llm-config create` and run `nasiko connect claude --config <name>`. The CLI sets `apiKeyHelper` and `ANTHROPIC_BASE_URL`.

How do I undo the connection?

`nasiko disconnect <agent>` restores the routing settings. A running harness may need stopping or disconnecting with `--force`.

Which harnesses does Nasiko support?

Claude Code, Codex, OpenCode and Cursor CLI. Routing works for the first three and is not available for Cursor CLI yet.

Where are session events kept before delivery?

Completed turns are queued under `~/.nasiko/integrations/queue/`. Permanently rejected deliveries land in `~/.nasiko/integrations/rejected/` and are safe to delete.

Discussion

No questions or reviews yet.

CLI tools

A transparent wrapper for Claude Code and Codex: a local gateway records run events and trajectories without changing the agent.

CLIExtended access245

Tokscale

tokscale

A CLI with an interactive TUI that tracks token usage and cost across AI coding agents: Claude Code, Codex, Copilot, Cursor and more

CLIExtended access5.8K

ANOLISA is a system stack for AI agents: output compression, memory, workspace snapshots, command checks and token accounting

CLIBroad access663

OpenTelemetry-based CLI tracing for Claude Code, Cursor and Codex sessions, showing what the agent actually did and what it cost

CLIExtended access3.1K

A native Bash-compatible shell written in Rust for Windows, Linux and macOS, running agent commands exactly as written.

CLIBroad access268

README in short

The README opens with the safe `nasiko agents discover` check, then separates session reporting from routing and gives a Docker quick start for the control plane.

README badge

Report a problem