Forge by ShipToday for Codex
Free, AI-powered product development lifecycle automation for Codex.
What it does
Ask Forge by name — include forge or @forge in your message — and it routes
the request through a structured PDLC workflow backed by the hosted Forge MCP
server.
Examples:
forge, implement user authentication with OAuth
@forge fix the checkout page crash on mobile
forge, break down the notifications feature into stories
forge, estimate story points for PROJ-123
@forge check status of my feature
Forge runs only when you ask for it. If your message only mentions Forge in
passing, Codex asks whether you meant Forge before starting anything. A
message that doesn't name Forge gets a normal response, even when it's about
planning or shipping work or mentions a ticket like PROJ-123.
What's included
- Forge MCP server (
plugins/forge/.mcp.json) connects to
https://teams.shiptoday.ai/mcp.
forge-autopilot skill routes your request to the right Forge workflow
when you ask Forge by name.forge-workflow skill helps organization admins create or remove custom
Forge workflow overrides.forge-feedback skill sends feedback to the ShipToday team from inside a
session. It shows you the exact message first and sends only after you
confirm.- Hooks (
plugins/forge/hooks/hooks.json) coordinate session state and
workflow tracking, and hold tools while a question is waiting for you or a
write is waiting for your approval. They never read your message to decide
anything, make no network calls, and keep session state in local files.
Install
This repository is a self-contained Codex plugin marketplace. The marketplace
manifest lives at .agents/plugins/marketplace.json and the plugin itself at
plugins/forge/.
From the Codex app
- Open Plugins → ⋯ → Add marketplace.
- Source:
ShipToday/forge-plugin-codex
- Git ref:
main
- Sparse paths: leave blank.
- Click Add marketplace, then install Forge from the
shiptoday
marketplace.
From the Codex CLI
codex plugin marketplace add ShipToday/forge-plugin-codex
Then run /plugins, open the shiptoday marketplace, and install Forge.
Enable hooks
The plugin ships lifecycle hooks (session routing, workflow guardrails).
Plugin hooks are disabled by default — enable them in ~/.codex/config.toml:
[features]
plugin_hooks = true
Token usage capture
Forge captures per-session token usage from the local Codex rollout log
(~/.codex/sessions/…/rollout-*.jsonl) and delivers it on Forge's own
forge__update_state calls via a PreToolUse input rewrite
(hookSpecificOutput.updatedInput). Codex honors these rewrites from
rust-v0.131.0. To decide whether the rewrite is safe, the plugin reads the
running session's version from the rollout's session_meta record — so a
Codex Desktop build newer than the codex binary on your PATH is detected
correctly — and only falls back to a cached codex --version probe when no
rollout version is available. On older versions it skips the rewrite instead of
triggering per-call hook errors; capture then degrades to the best-effort
checkpoint relay. Upgrade to Codex ≥ 0.131.0 for reliable capture.
License
MIT - see LICENSE.
