Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Codex is now an official Termux package

Written November 13, 2026

The codex-termux fork has ended because Codex now ships as an official Termux package. What the fork's final release says, and what changed.

What changed

For a while, running Codex inside Termux on Android meant using a community fork. The codex-termux repository tracked upstream Codex milestones and shipped them as the npm package @mmmbuto/codex-cli-termux. That route is now closed. The repository's README opens with an end-of-life notice: "Codex is finally an official Termux package. 0.163.0-termux.3 is the final release of @mmmbuto/codex-cli-termux: from now on, Codex for Termux stays on the official package."

The official package is real in the place you would expect to find it. Termux's own package tree carries a packages/codex directory in termux-packages, with its build script and Android patches. Codex on Termux is no longer a side build maintained by one fork. It sits in the same package collection as the other tools Termux users install with pkg, and it updates through that collection too.

The fork's maintainer frames the ending as the point of the project, not a failure of it. The README thanks the people who installed the package, ran it on real phones and reported issues, in these terms: "You kept Codex alive on Android until it had an official home." Anyone still on the fork does not need to hunt for a replacement project. The replacement is the official package, and the final fork release is built to hand you over to it.

The switch is automatic

If you are already on the final fork release, the move largely happens for you. The README says that once you are on that release, the first interactive launch installs the official codex package and starts it. The old npm package stays installed and inert: it is not removed for you. Your ~/.codex directory — config, login and sessions — is reused as it is, so the sign-in and history you already have carry over to the official build.

There is a fallback for a rough first launch. If anything in that automatic install fails, the fork prints the manual steps and uses its bundled binary for that run, so a failed switch does not leave you without a working Codex in the session where it happened. From the next launch onward, the official package is the one that matters, and the fork's binary is only the bridge that got you there.

Switching by hand

The README also gives a manual route, for people already on the official package or cleaning up after the automatic switch:

The reinstall step is not optional, and the README says why: npm can remove the codex command together with its package, so uninstalling the fork can take the command with it even when the official package is present. The old codex-exec command belongs to the npm package and disappears with it. If you have not moved yet at all, the entry point is simpler: pkg install codex. If that reports the package as already installed but codex still runs the old launcher, use pkg install --reinstall codex. From then on, updates come through the package manager: pkg upgrade codex.

Downstream apps moved too

The change reaches past people who install Codex in Termux directly. Shelly, an Android terminal app that bundles a Codex binary, describes its current arrangement in its README this way: release builds bundle "the Android-native codex from Termux's official package, pinned in .ci-versions/ after CI checks Termux's signed apt index", and runtime updates install the same shape. In other words, an app that once had reason to consume the fork's build now takes the official package as its source, with the version pinned and the package index's signature part of its build process.

The extras are a separate package

One thing the official package does not try to be is the fork author's extended build. The README is plain about the split: "The official package is plain Codex." The extra commands the same author maintains — /loop, /goal, /vivling, /vl and /remote-control — live in a separate npm package, @mmmbuto/codex-vl, installed with npm install -g @mmmbuto/codex-vl. It runs as codex-vl, side by side with the official codex, with no PATH conflict, on Termux, Linux and macOS. Wanting the extras is no longer a reason to stay on the ended fork.

What to do

Related playbooks

Sources

Back to: Coding tasks playbooks hub · Also: Codex 0.167: run parallel sessions in one place