Codex Web Attachments & Composer @ Search, codexapp CLI/Termux Hardening, Playwright-on-Android Notes, and Oracle A1/Incus Check

Daily Tech Digest — March 6, 2026

Over the last 24 hours, work centered on Codex Web parity with the desktop app, notably around attachment handling and composer UX. At the same time, the CLI packaging story moved forward (including codexapp naming and Termux hardening), while Android automation constraints and an Oracle A1/Incus health check were documented.

Codex Web Parity: Attachments That Actually Render

Codex Web gained a full end-to-end path for non-image attachments: a backend upload endpoint persists blobs, returns absolute paths, and passes them back as structured mention items so the model can see them. On the frontend, transcript normalization now renders file attachments in chat history, not just in model payloads. A fallback parser converts text-only responses (e.g., “Attached file paths: …”) into structured attachments so chips still render reliably. These changes were validated with Playwright screenshots across desktop, mobile, and tablet to confirm that “what attachments do you have?” responses match the actual attachment state.

Composer UX: Multiline Input and @ File Search

The composer was converted from single-line input to a textarea with Codex-style behavior: Enter sends, Shift+Enter adds a newline. The @ file search feature was implemented with keyboard navigation and cwd-scoped searching, and suggestion rows now include file icons/badges to align with desktop styling. These UX changes were also exercised via Playwright to keep parity tight.

Dictation Flow Improvements

Microphone dictation now unblocks properly after transcription, and repeated dictation segments append on new lines. This matches the expected “dictate in chunks” workflow without getting stuck.

CLI Packaging, Naming, and Termux Reliability

The CLI side pushed forward with better defaults and more resilient bootstrapping. codexui now launches codex app-server using approval_policy=never and sandbox_mode=danger-full-access by default. Non-Termux environments auto-install the official @openai/codex package and trigger login if it’s missing. Termux stability improved with a hardened SPA fallback when dist/index.html is missing and guidance to avoid npx temp cache paths.

Command naming evolved as well: codexapp was added as an alias (while keeping codexui), and an attempted unscoped rename to codexui ran into npm naming policy constraints. A path toward @friuns/codexapp is underway with versioning and publish checks, noting npm propagation quirks.

Android Automation + Infra Notes

A quick pass on Playwright-on-Android clarified that andClaw relies on bundled assets and a proot Linux environment; direct Termux without proot is not reliable. Proot-to-Termux API access is possible only through host bridging.

An Oracle A1 + Incus health check showed the instance is reachable via SSH with no forced reset required, and Incus port 8080 is responsive with recent successful UI/API access. Any intermittent “frozen” reports likely stem from SSH connection throttling rather than the service itself.

What’s Next

• Finalize @friuns/codexapp versioning and public visibility.
• Add additional attachment telemetry to reduce “no attachments” responses when APIs return text-only blocks.
• Expand Playwright regression coverage for attachment rendering and composer behaviors.