Skip to content

Blog / News

Stay in Codex. Ship real integrations.

Tray Headless for Codex brings the full Tray AI Orchestration Platform natively into Codex — real engineered components, not a markdown file. Built on the same headless-first foundation as Tray Headless for Claude Code.

Simon Cole avatar

Simon Cole

For a decade, enterprise iPaaS vendors built their products around one assumption: developers would come to the platform.

That assumption hasn’t aged well.

Developers have already left. They live in AI IDEs now — Claude Code, Cursor, Codex, Windsurf — and that’s where they build. By Stack Overflow’s 2025 survey, 84% use or plan to use AI tools. By various estimates, AI now writes roughly 41% of new code. The migration already happened. Now enterprise tooling is in a race to catch up.

84%
of developers use or plan to use AI tools
~41%
of new code is now AI-generated

Sources: Stack Overflow 2025 Developer Survey; industry estimates; developer tooling surveys, 2026.

The challenge

Tools change. Requirements don't.

OpenAI’s Codex went from 600K to 5M weekly developers in the first half of 2026, adding roughly a million a month. Claude Code’s primary-tool share overtook Cursor’s for the first time in recent surveys. Most developers don’t commit to one tool — they run two or three, and the leaderboard reshuffles every quarter.

2–3
AI tools in the average
developer's stack

For an enterprise iPaaS, that means one thing: extend a first-class experience to each AI IDE, and keep pace as they change. Most platforms can’t. Support arrives late and shallow, the tooling underneath lags the IDE your team actually builds in, and developers work around the gaps.

The problem with most headless offerings

How to fake a headless iPaaS offering

Every iPaaS vendor is rushing to claim headless support. Here’s how most of them do it: pile everything into markdown. Stuff a giant instructions file into each IDE and call it support.

It looks fast for a release or two. But then you get the bill. It comes as bloated context, brittle prompts, nothing typed or testable, instructions drifting out of sync with the platform beneath them. You can simulate velocity that way but you can’t sustain it.

The product

Introducing Tray Headless for Codex

Tray Headless for Codex brings the full Tray AI Orchestration Platform natively into Codex — integrations, automations, MCP services, and agent tools, right where developers already code. It’s built on the same headless-first foundation as Tray Headless for Claude Code: the same typed components, the same governance, the same architecture underneath. That foundation is what makes extending to a new IDE fast and the support genuine.

Claude

Purpose-built plugin

Tray Headless
for Claude Code

The deepest AI IDE experience for Claude

Codex

Purpose-built plugin

Tray Headless
for Codex

The deepest AI IDE experience for Codex

Cursor Windsurf Gemini GitHub Copilot

Any MCP-compatible AI IDE

Other AI IDEs

Cursor · Windsurf · Gemini · and more

Platform-neutral

Tray Headless MCP

The full Tray platform as MCP services — built for developers to unlock its complete power from any AI IDE

Build Connect Validate Configure

The unified platform underneath

Tray AI Orchestration Platform

Integration Automation MCP services Governance 700+ connectors

Under the hood

What's inside the plugin

Tray Headless for Codex is built from engineered components, not a markdown file:

01

Config files

Pre-configured setup connecting Codex to Tray, with sensible defaults and workspace configuration.

02

Tool definitions

Typed definitions that give Codex precise access to the full Tray MCP tool surface.

03

Response formatters

Translate Tray responses into the shape Codex expects, reducing hallucination and improving output quality.

04

Validation hooks

Pre- and post-tool checks that enforce conventions and audit structure before workflows deploy.

05

Connector agent

A specialist agent that turns a natural-language description into prescriptive, validated step configurations.

06

Codex extension

Tray-specific primitives and patterns wired directly into the Codex development model.

Plus six packaged skills — build-workflow, tray-connectors, tray-patterns, tray-gotchas, research-connector, and set-workspace — so Codex knows how Tray thinks.

Velocity you bolt on with markdown is debt. Velocity you architect is a moat.

Why it matters

What it means for you

Velocity without the debt

Real, typed, validated components scale. Markdown doesn't. Each new IDE Tray supports reuses the same foundation, so the support is genuine and the cadence holds. Platforms built on older architectures that retrofit headless onto what already exists can't replicate that.

No bet required

You don't have to predict which IDE wins. Developers run multi-tool stacks. The leaderboard reshuffles every quarter. Tray Headless covers Claude Code and Codex — Anthropic and OpenAI — so your team builds where they want to build.

No lock-in

Today's pick won't be forever. When the landscape shifts, developers move between IDEs without rebuilding. Integrations, automations, and governance stay on Tray while the tool on top changes.

Tray Headless

Build where you want. We bring all of Tray.

The full Tray AI Orchestration Platform, native to your AI IDE — Claude Code, Codex, or any MCP-compatible IDE.

Explore Tray Headless →