Raw CLI vs RexCLI Layer¶
RexCLI 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 RexCLI¶
| Workflow Need | Raw CLI Only | With RexCLI 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 RexCLI When¶
- You switch between
codex,claude,gemini, oropencodein 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/rex-cli.git
cd rex-cli
scripts/setup-all.sh --components all --mode opt-in
source ~/.zshrc
codex
Then verify persistent artifacts exist:
ls memory/context-db
Expected: sessions/, index/, exports/.