OpenAI Codex Feature Expansion: Appshots, Goal Mode, Plugin Sharing, and Advanced Annotation

The headline-friendly framing of Appshots — press Command-Command, send your window to Codex — undersells what's actually shipped. The capture uses a hybrid of macOS ScreenCaptureKit for the visual and the Accessibility APIs for structured text extraction, so Codex receives both the pixels of the frontmost window and the underlying accessible text tree, including content scrolled off-screen ^[1][2]. That detail matters: a Figma board, a long Slack thread, or a Jira ticket below the fold all arrive in the thread without the user having to scroll-and-stitch. Two more constraints reveal intent. Appshots default to opening a new thread, but if the user touched Codex within the last 60 seconds the capture is appended to that recent thread — supporting consecutive captures during an iteration loop without polluting history ^[1]. And the feature is Mac-only and explicitly unavailable from the CLI, requiring Screen Recording and Accessibility permissions ^[1].

Curtis Pyke at Kingy AI reads this as a deliberate human-AI handoff pattern: 'not just screenshot to chat,' but a least-friction primitive for visual context that the user fires on demand rather than streams ambiently ^[2]. The contrast with always-on recall products is the point — OpenAI is betting developers want a discrete capture key, not surveillance.

The official pitch for Goal Mode going GA is straightforward — define a completion condition, a success-check method, and constraints, then let /goal run for hours or days with pause, resume, and clear controls ^[3][4]. What the announcement doesn't quantify is the cost. Reddit's r/codex community surfaced specific power-user numbers: one developer ran a 210-task backlog overnight in 28 hours, holding context over 7.8 million tokens through 31+ compactions — and burned 70% of their weekly quota on a $100 plan to do it. The same thread converges on a working heuristic of roughly 1% of weekly quota per hour on the xhigh tier.

Multi-hour autonomy is real, but it isn't free, and the pricing curve means that the canonical 'leave it running overnight' demo is a once-or-twice-a-week move on the lower-tier plans, not a daily workflow. The community's working consensus on what actually fits /goal is unusually clean: vulnerability identification and resolution across large codebases, framework or language migrations, and telemetry-driven refactors with crisp 'done' criteria. The bad fit is gameplay or feel-based work that needs human-in-loop review — exactly the kind of subjective task where the autonomy-versus-cost tradeoff inverts. Goal Mode GA, in other words, isn't a green light for every team; it's a green light for the engineering tasks that have a verifiable stopping condition.

Two friction stories from launch day tell you more about OpenAI's roadmap than the feature list does. First, an OpenAI developer-experience engineer had to publicly walk users through manually enabling Goal Mode — codex features enable goals, then restart the app — and that workaround tweet attracted more engagement than the official launch announcement. Reddit corroborated the experience, with users noting /goal 'just started working without fanfare' for some and not at all for others until the manual flag was flipped. The pre-built Codex CLI v0.133.0 makes goals enabled by default, but the desktop app didn't ship that way.

Second, Windows-WSL users reported the update bricking their desktop app entirely; an OpenAI employee responded in-thread that Windows parity ships next week. Mac mobile relay — the remote computer use feature that lets Codex keep operating apps after lock and via Codex Mobile — was also flaky in field testing. The cumulative read is that Codex now has a clear platform tier hierarchy: Mac desktop is the reference target, CLI is the fast-moving substrate (v0.128/0.129 added persisted goals, codex update, Vim editing, allowlists, Hooks, and Programmatic Access Tokens), Codex for Chrome is the new browser surface, and Windows is the still-catching-up tail. For teams standardizing on Codex, this matters more than any individual feature: the same release rolls out to different audiences at different times.

The flashy features get the headlines, but plugin sharing is the move with the deepest commercial logic. Codex's plugin marketplace launched in March 2026 with 20+ integrations including Slack, Figma, and Notion and JSON-policy-based governance controls ^[5]. The May update lets ChatGPT Business workspaces distribute reusable bundles — skills, app connections, and MCP servers — to teammates, gated by an admin-level plugin_sharing = false policy in Codex cloud's Policies & Configurations, with Enterprise on early access and full rollout 'coming soon' ^[6][7].

This is the textbook network-effect playbook: once a team's internal AI tools are codified as plugin bundles and circulating inside one workspace, the switching cost compounds with every new plugin authored against the bundle. The Business-first/Enterprise-later stagger is calculated — it lets OpenAI demonstrate adoption and admin tooling at the SMB tier before promising the same to procurement-heavy enterprise buyers. The competitive frame matters too: The New Stack's hands-on review says Codex now matches Claude Code on breadth while Anthropic retains a quality edge, and Codex reports 1M+ active developers and 20x usage growth against Claude Code's reported $1B ARR ^[8][9]. Plugin sharing is how Codex turns breadth into stickiness — a feature Anthropic does not yet match at the workspace tier. The risk OpenAI's own docs flag is plugin sprawl and policy drift; the deliberate plugin_sharing switch and approval settings exist precisely because shadow tooling inside workspaces will follow.