Codex

Codex has two Treeship paths today. The skill teaches Codex how to use Treeship and how to work safely in this repo. The MCP bridge captures MCP-routed tool calls into a Treeship session.

Method 1: Install the skill

npx skills add zerkerlabs/treeship --skill treeship --agent codex -g -y

npx skills add zerkerlabs/treeship --skill treeship-dev --agent codex -g -y

Use treeship-dev. Read AGENTS.md first, then update the Codex integration docs.

Method 2: Attach the MCP bridge

From a project with treeship init already run:

curl -fsSL treeship.dev/install | sh
treeship init
treeship add codex

This appends a [mcp_servers.treeship] block to ~/.codex/config.toml, creating the file and parent directories if needed.

Manual config:

[mcp_servers.treeship]
command = "npx"
args = ["-y", "@treeship/mcp"]

[mcp_servers.treeship.env]
TREESHIP_ACTOR = "agent://codex"
TREESHIP_HUB_ENDPOINT = "https://api.treeship.dev"

Restart Codex after changing MCP config.

Method 3: Codex plugin candidate

The repo includes a candidate Codex plugin package at:

plugins/treeship-dev/

It bundles the treeship-dev skill and a .codex-plugin/plugin.json manifest for local testing and future plugin submission. Until the plugin is accepted into an official marketplace, the direct skill install above is the stable path for users.

For maintainers preparing submission:

1. Keep plugins/treeship-dev/skills/treeship-dev/SKILL.md in sync with skills/treeship-dev/SKILL.md.
2. Review plugins/treeship-dev/.codex-plugin/plugin.json for current version, URLs, policy links, and screenshots/assets if the marketplace requires them.
3. Test in a fresh Codex session against a clean Treeship checkout.
4. Submit the plugin package from plugins/treeship-dev/ using the current Codex plugin submission process.

What Gets Captured

The skill itself is just instructions. It does not capture anything. The MCP bridge captures MCP callTool activity while a Treeship session is active:

• signed intent attestation before the call
• signed result receipt after the call
• session timeline event for the Codex actor

Codex built-in shell and file tools do not currently route through this MCP bridge. Use treeship wrap -- <command> for commands that need explicit receipts until Codex exposes hook coverage similar to the Claude Code plugin.

Coverage

See Also

• skills/treeship/SKILL.md
• skills/treeship-dev/SKILL.md
• integrations/codex/
• Agent Skills
• MCP bridge