Raw CLI vs Harness CLI Layer¶

Quick Answer: Use a raw codex, claude, gemini, or opencode CLI for a focused one-off task. Add Harness CLI when the work needs cross-session memory, workflow routing, multi-client handoff, browser safety, or verification evidence. Harness CLI is a local workflow layer; it does not replace the coding client.

Decision at a glance¶

Need	Recommended path
One short task with no durable state	Raw CLI
Shared project memory and searchable context	Harness CLI + ContextDB
Multiple clients or agents with ownership boundaries	Harness CLI + Agent Team
A change that needs safety and completion evidence	Harness CLI + edit and verification gates

Harness CLI is not a replacement for Codex, Claude, or Gemini CLI. It is a reliability layer on top of them.

Star on GitHub Quick Start Case Library

What Changes With Harness CLI¶

Workflow Need	Raw CLI Only	With Harness CLI Layer
Cross-session memory	Manual copy/paste context	Project ContextDB resume by default
Cross-agent handoff	Ad hoc and fragile	Shared session/checkpoint artifacts
Browser automation	Tool-by-tool setup drift	Unified MCP install + doctor scripts
Safety for sensitive config reads	Easy to leak secrets into prompts	Privacy Guard redaction path
Operational recovery	Manual troubleshooting	Doctor scripts + reproducible runbooks

Use Raw CLI Only When¶

You need a one-off short task with no handoff.
You do not need session persistence or workflow traceability.
You are experimenting in a throwaway environment.

Add Harness CLI When¶

You switch between codex, claude, gemini, opencode, hermes, or grok (Grok Build) in one project.
You want restart-safe context and auditable checkpoints.
You need browser automation and auth-wall handling with explicit human handoff.
You must reduce accidental secret exposure during config reads.

Fast Proof (5 Minutes)¶

git clone https://github.com/rexleimo/harness-cli.git
cd harness-cli
scripts/setup-all.sh --components all --mode opt-in
source ~/.zshrc
codex

Then verify persistent artifacts exist:

ls .aios/context-db

Expected: sessions/, index/, exports/.

Deep-Dive Cases¶

Next Action¶

Star on GitHub

FAQ¶

Does Harness CLI replace my coding agent?¶

No. It adds a local workflow, memory, and verification layer around supported clients.

Is the raw CLI ever the better choice?¶

Yes. Keep the raw path for small, stateless, low-risk tasks where extra state would not improve the result.

Canonical Docs¶

Read Workflow Policy, ContextDB, and Getting Started for the current behavior.