Nori CLI: One Terminal Interface for Claude, Gemini, and Codex
Referenced in catalog
Summary
Nori CLI is an open-source, Rust-built terminal interface that lets developers switch between Anthropic Claude, Google Gemini, and OpenAI Codex from a single interactive TUI — eliminating the need to maintain separate CLIs for each AI provider. With 121 GitHub stars as of April 2026 and releases shipping multiple times per week, it is the most active “multi-provider coding agent shell” in the open-source space. The project builds on OpenAI’s Codex CLI codebase and integrates Zed Industries’ Agent Client Protocol (ACP) to orchestrate agents across providers.
What This Source Covers
The source is the GitHub repository for nori-cli. It provides: README documentation, release notes across 17+ versions, and source code written primarily in Rust (97.7%). The review is based on the README, recent release changelogs (0.14.x–0.17.0), and the tool’s positioning.
Critical Assessment
Credibility
Medium. Nori is a new, small-team open-source project — the GitHub org tilework-tech is not an established vendor. 121 stars is a modest signal. The release cadence (multiple releases per week) demonstrates active development but also suggests instability and churn. The project does not have documentation outside the README, and no production case studies exist. The ACP integration is novel but the underlying protocol from Zed Industries is itself pre-stable.
Technical Approach
Nori takes an unconventional approach: rather than building its own agent engine or calling provider APIs directly, it wraps the CLIs of other providers (Claude Code, Gemini CLI, Codex CLI) through ACP — the Agent Client Protocol. Authentication is delegated to those upstream CLIs. This means Nori is effectively an orchestration shell, not a standalone agent. The TUI is built in Ratatui (a Rust terminal UI framework) with double-buffered scrollback.
This architecture is a double-edged sword: it gets the full capabilities of each underlying agent without re-implementing them, but it also means Nori is tightly coupled to the stability and interfaces of three separate tools simultaneously. Breaking changes in any upstream tool can break Nori.
Planned vs. Shipped Features
Several features in the README are flagged as planned/coming:
- OS-level sandboxed command execution — not yet shipped
- MCP server connection — partially implemented (MCP OAuth in 0.16.0, but tooling depth unclear)
- Session persistence (
nori resume) — not yet shipped - Multi-agent orchestration — not yet shipped
The release notes show substantive ACP improvements and bug fixes, but the headline multi-agent and sandboxing features remain aspirational.
Comparison with Alternatives
| Tool | Provider Support | Architecture | Stars (Apr 2026) |
|---|---|---|---|
| Nori CLI | Claude, Gemini, Codex | ACP wrapper over 3 CLIs | 121 |
| OpenCode | 40+ providers via LiteLLM | Direct API calls | High |
| Goose | Multi-provider, MCP-native | Agent framework | High |
| Codex CLI | OpenAI only | Native agent | 73k+ |
OpenCode and Goose offer broader provider support and more mature multi-provider architectures. Nori’s differentiator is its ACP-based orchestration and its Ratatui TUI quality.
Strengths
- Rust performance: Fast startup, efficient rendering, no JVM or Python runtime dependency.
- ACP integration: The only publicly visible consumer of Zed’s Agent Client Protocol, which has long-term potential as an agent interoperability standard.
- Rapid iteration: Multiple releases per week with substantive changelogs.
- No credential duplication: Reuses authentication tokens from upstream CLI tools already installed on the system.
Weaknesses
- Tight coupling to three upstream CLIs: Stability depends on Claude Code, Gemini CLI, and Codex CLI simultaneously. Each upstream breaking change propagates.
- Single developer / small org risk: No indication of team size;
tilework-techhas no organizational presence beyond this repo. - Incomplete feature set: Major differentiating features (sandboxing, multi-agent) are not yet shipped.
- No documentation beyond README: No architectural docs, API references, or troubleshooting guides.
- Authentication complexity: Users must separately install and authenticate each upstream CLI before Nori can manage it.
Entities Referenced
- Nori CLI — the subject tool; multi-provider AI coding agent TUI
- Codex CLI — OpenAI’s CLI; Nori is described as “built on the great work within OpenAI Codex CLI”
- Claude Code — Anthropic’s coding agent CLI; supported as a first-class provider
- Gemini CLI — Google’s coding agent CLI; supported as a first-class provider
Recommended Radar Position
Assess. Nori CLI is technically interesting as the first concrete ACP consumer, and its Rust TUI is high quality. However, it is early-stage, underdocumented, and the core multi-provider orchestration model is architecturally fragile. Engineers who already use multiple AI coding agents and are tired of context-switching between terminals should experiment with it. Organizations should not adopt it as a team standard until it ships sandboxing and session persistence, and the ACP integration matures.