<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cli on Danilo Falcão da Silva</title><link>https://falcao.org/tags/cli/</link><description>Recent content in Cli on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 26 May 2026 00:05:54 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Codex CLI From a DevOps Lens: Fast, Guardrailed, and Worth Piloting</title><link>https://falcao.org/posts/codex-cli-devops-opinionated-review/</link><pubDate>Tue, 26 May 2026 00:05:54 -0300</pubDate><guid>https://falcao.org/posts/codex-cli-devops-opinionated-review/</guid><description>&lt;p>I decided to test Codex CLI today because I have liked the quality I get from GPT-5.3-Codex enough to take it seriously in real work. I did not open it looking for a demo. I opened it with the same question I apply to any tool that can touch production-bound code: is this operationally trustworthy, or just impressive for fifteen minutes?&lt;/p>
&lt;p>My conclusion is clear: Codex CLI is already good enough to pilot seriously, but it is not my daily driver yet.&lt;/p></description></item></channel></rss>