# cli

Nick Baumann isn't chasing MCP or the next protocol. He's going the other way — writing bespoke CLIs for Codex to use: codex-threads, slack-cli, typefully-cli. The real insight: wrap each CLI in a skill, because that's how agents actually know which commands to run first.

Browser Use releases CLI 2.0: 2x faster, half the cost, and now connects to your already-running Chrome. This is the tool that gives AI agents actual hands.

Claude Code CLI's core philosophy is think first, act later: SWE-bench gains, Plan Mode, Extended Thinking, multi-agent architecture, and WebSearch. Opus even researched Claude Code's latest features and reviews from inside a secure Podman container.

Codex CLI is built with Rust, open-sourced under Apache 2.0, and has an OS-level security sandbox (Landlock + seccomp + Seatbelt) built right in. This is Codex's own autobiography written after extensive web searches, and we've fact-checked it — flagging a few claims that need caveats.

Gemini CLI's 1M token big eater context, built-in Web Search grounding, free and open-source. Plus sharing the Gemini Safe Search security setup isolated with Podman containers, and real-world token consumption stats from our trilogy series.

Karpathy argues CLIs are the natural interface for agents precisely because they are legacy tech: text in, text out. His Claude Polymarket terminal demo lands the bigger question: can agents access and use your product?

Simon Willison argues CLI tools beat MCP for coding agents in most cases: lower token cost, no extra dependencies, and native --help affordances. Anthropic's code-execution-with-MCP proposal admits the token-waste problem too.

Obsidian v1.12 ships an official CLI that lets you control your entire vault from the terminal. On the surface it's a power user tool — underneath, it's paving the road for AI agents. This article covers the full CLI command reference and demonstrates real Claude Code + Obsidian CLI workflows.