A new Reddit explainer says Codex v0.117.0 plugin support is reaching users, and some Claude Code subscribers report trying Codex's $20 tier after repeated rate-limit friction elsewhere. Re-evaluate Codex if plugins or practical session headroom were the blockers last week.
Codex v0.117.0 now supports plugins. Here’s a simple visual explainer.
The concrete product change is plugin support. A Reddit post in r/OpenAICodex says "Codex v0.117.0 now supports plugins" and packages it as a "simple visual explainer," which suggests the feature is already reaching end users rather than sitting in a vague roadmap state plugin explainer. For engineers, that matters because plugins are a practical integration surface: they expand what the coding agent can call into without requiring every workflow to fit the stock toolset.
The evidence here is still early and lightweight. The post does not spell out plugin APIs, sandbox rules, or install mechanics, so the confirmed change is narrower: plugin support is present in v0.117.0, but implementation details are not yet documented in the evidence provided gallery post.
That's it. Just subscribed this morning to codex to try this it out. And this is all outside of the claude's new "peak hours"
The immediate driver looks less like model hype and more like headroom. In r/ClaudeCode, one user said they had "just subscribed this morning to codex" because Codex's $20 plan appeared to offer more usable capacity than Claude Code's $100 plan, adding that this was "all outside of Claude's new peak hours" usage comparison. In the same thread, another commenter argued "5.4 model is currently kinda better," framing the switch as a tradeoff between model preference and practical availability rather than a clean quality win for either side comparison thread.
I'm not even doing anything special - in fact I think I got my project pretty well organized, very small context usage per sub-agent, I don't use many sub-agents in the first place. My usage is a 5% only for the week! Yet I am constantly hitting that error as soon as Claude comes out of a web search or runs a review or anything slightly more complex than just editing a few files Like what the hell Edit: I found that asking claude to run the thing in a sub-agent bypasses the api error rate limit. Got no clue what's going on, it's been an on-going issue for me for a few days now
A second Reddit report adds the failure mode behind that shopping behavior. A Claude Code Max $200 user said they were using only "5% for the week" yet still repeatedly hit "API Error: Rate limit reached," especially after web search, code review, or anything "slightly more complex than just editing a few files" rate-limit report. The same user said routing work through "a sub-agent bypasses the api error rate limit," which reads as a workaround rather than a documented quota model rate-limit report. Together, these posts do not prove Codex is broadly better, but they do show why plugin support plus cheaper perceived session availability is enough to trigger new trials this week.
Practitioners describe Channels as MCP servers that can push messages into a live Claude Code session for folder watches, chat bridges, and response callbacks. Try it for lightweight automations, but plan for context growth, missing remote restarts, and weak daemon support.
workflowTwo local StatusLine tools now surface hidden 5h and 7d quotas from Claude Code telemetry, while Max subscribers still report rate-limit errors and confusing practical headroom. Install a tracker before long sessions so you can measure resets and separate outages from quota exhaustion.
breakingThe service says Starter now bundles credits, high-limit access to Claude, GPT, and Gemini families, and a new Web Apps v2 builder with automatic deployment. Treat it as an evaluation path until you verify official API routing, rate limits, and code quality on your own repos.
workflowUsers surfaced /insights reports, plan mode, editor handoff, and Anthropic training links as the fastest way to understand Claude Code before buying around unclear session caps. Learn these built-ins first so you can judge where the tool helps and where other agents are still needed.
workflowPractitioners describe Channels as MCP servers that can push messages into a live Claude Code session for folder watches, chat bridges, and response callbacks. Try it for lightweight automations, but plan for context growth, missing remote restarts, and weak daemon support.
