Readiness before execution
Check runner type, workspace, allowed commands, network use, and artifact locations before work starts.
Home / Runners
Mac · CLI runners · Explicit approval
Treat existing tools as governed runners.
Naikaku does not rebuild the tools developers already trust. It connects authenticated local Coding CLIs behind scoped worktrees, explicit approval and reviewable evidence.
Logs and evidence
Record command, exit code, output summary, changed files, screenshots, and receipts for later review.
High-impact actions need approval
Production deploy, Git push, external send, purchase, and broad desktop control do not pass automatically.
Connect local Coding CLIs without handing credentials to the browser.
naikaku doctor checks Node.js, dependencies, the gateway and whether local codex, claude or qwen commands are available. It does not run a model. Real work uses fixed runner templates, a bounded worktree, execution logs, changed-file references and receipts in one reviewable flow.
naikaku doctor
Checks environment and CLI readiness without starting a model or desktop automation.
naikaku task
Prepares a reviewable task and evidence package by default instead of launching an external runner immediately.
Codex, Claude and Qwen
Uses fixed adapters and bounded scopes while keeping local login credentials out of the browser and leaving a receipt.
How runner candidates fit.
Codex CLI, Claude Code, Qwen Code, OpenHands, OpenClaw-style tools, Hammerspoon, Playwright, and similar tools can become runners when they follow Naikaku's receipt and artifact contract.
Download
Run steps, verification commands, and checksums.
API Gateway
Bring-your-own keys and future hosted gateway.
Runners
Boundaries for CLIs and Mac automation.
Use cases
Pick the entry point by intent.
Developers
Contributions, adapters, and verification.
License
Noncommercial source and commercial permission.