# codex

OpenAI wedged a $100/month plan between its $20 Plus and $200 Pro tiers, promising higher Codex limits and explicitly targeting Anthropic’s Claude. But its honeymoon limits expire May 31, so the plan may feel less generous afterward.

Every two hours, Codex drafts email replies for review. The drafts are good — he edits them anyway. Those edits are context too, and most automations throw them away. The fix: an inner loop brings context to the work; an outer loop recovers context from the review diff.

Dimillian (an iOS dev now at OpenAI) wrote a field guide for Codex Mobile. The part worth keeping is a mental model that holds across tools: your phone is not a shrunken terminal, it is the control center that keeps you making decisions while the agent does the work.

Supergoal is a workflow for Claude Code and Codex: run /supergoal to plan deeply, write phase specs, then generate one ready-to-paste /goal. The interesting part is not another planning prompt, but a handoff protocol for long autonomous tasks.

When learning a new tool with Codex, the worst move is asking it to give you a lecture. A better pattern is to ask it for an entry point, a rough map, a tiny exercise, a teach-back check, and breadcrumbs for next time.

Vaibhav Srivastav's Codex prompt is interesting because it describes an agent maintenance loop: look back at recent work, find repeated workflows, and package only high-confidence patterns into Skills, automations, or subagents. It is agent dreaming: turning busy work into capability.

Codex is no longer only editing code. Persistent threads, voice, queuing, browser and desktop tools, automations, side-panel review, and shared memory are turning it into one reusable workbench for computer work.

OpenAI's Cookbook frames Codex Goals as a thread-scoped completion contract: the objective persists, but completion must be checked against evidence. This post fills in the official spec angle around GP-192, GP-197, and GP-207.

OpenAI and Anthropic both pushed /goal-like ideas into coding agents. A goal helps, but production agents also need strategy, constraints, health metrics, autonomy boundaries, and stop rules.

OpenClaw and Hermes are both handing low-level coding-agent execution to Codex app server. This is not just a model switch. It is the agent product stack separating model, execution engine, and chat surface.

Mem0 breaks down Codex CLI memory: not a vector database, but local Markdown, background summaries, credential scrubbing, and grep search. This post looks at when local notes are enough, and when a semantic memory layer makes sense.

Codex `/goal` is not a wish machine. Chris Hayduk's real point is engineering discipline: give the agent a measurable finish line, a fast feedback loop, and Markdown files that work as long-term memory.

Jarrod Watts looked inside Codex Goals and found that it solves early stopping, not long-run drift. The real long-running agent stack needs upfront clarification, multi-agent review, and memory outside the context window.

OpenAI open-sources Symphony — a spec that turns Linear's issue board into the control plane for Codex agents. Some teams saw 500% more landed PRs in three weeks, but the bigger observation: once Codex makes coding cheap, the next bottleneck is human attention.

OpenAI DevX's Dominik Kundel says Chronicle means he no longer packages context for AI: one line can sync docs, edit markdown, open a PR, and DM Slack. Nice, but Chronicle's costs are real: screen recording, unencrypted local memories, and prompt-injection risk.

OpenAI quietly open-sourced Euphony — a browser-based viewer for Harmony chats and Codex session logs (Apache 2.0). Four telling details buried in the source: a 2-line AGENTS.md, gpt-tokenizer as a runtime dep, translation needing the user's own API key, and a self-written SSRF warning.

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.

Berryxia uses Dense vs MoE to explain why Codex shines at bug fixes, refactors, and long-running engineering while Claude wins vibe coders. The real split is broader: training philosophy, product design, and precise delegation versus interactive creation.

Many teams treat Claude Code and Codex as interchangeable tools, only to waste hours on misconfiguration. This article breaks down the fundamental differences in their control planes and trust models, with a practical day-one setup guide.

@daniel_mac8 shares an open-source Elixir implementation: create a Linear issue and move it to 'in progress,' and Symphony picks it up in a dedicated Codex workspace. Codex even writes status updates back. The author argues this is software development moving up an abstraction layer.