Pick your AI coding tool.
Each plugin connects your tool to Forge and adds guardrails: while a question or an approval is open, file edits and writes to connected tools, such as your tracker, wait. The plugins’ hooks run on Node.js, so it needs to be installed. A free account is created when you sign in.
-
1Add the ShipToday marketplace and install Forge
Run these two commands inside Claude Code:
/plugin marketplace add ShipToday/forge-plugin-claude-mp /plugin install forge-shiptoday@shiptoday -
2Sign in
Run
/mcp, choose forge, and sign in when prompted. New accounts are free. -
3Start
Type
forge,and what you need. See three ways to start.
Updating later: /plugin marketplace update shiptoday. Source on GitHub.
-
1Add the ShipToday marketplace and install Forge
From the Codex CLI:
codex plugin marketplace add ShipToday/forge-plugin-codexThen run
/plugins, open the shiptoday marketplace, and install Forge.In the Codex app instead: Plugins → ⋯ → Add marketplace, source
ShipToday/forge-plugin-codex, git refmain, then install Forge from the shiptoday marketplace. -
2Turn on plugin hooks
Codex ships with plugin hooks off. Forge's guardrails and token measurement need them — add this to
~/.codex/config.toml:[features] plugin_hooks = true -
3Sign in
Codex prompts you to sign in to forge the first time it connects. New accounts are free.
-
4Start
Type
forge,and what you need. See three ways to start.
Token usage is captured from Codex's own session log on Codex 0.131.0 or newer. Source on GitHub.
-
1Add the plugin from its repository link
Open Cursor Settings → Plugins and paste this into Search or Paste Link:
https://github.com/ShipToday/forge-plugin-cursor -
2Sign in
Open Cursor Settings → Tools & MCP, find forge, and click Sign In. New accounts are free.
-
3Trust the hooks
Review and trust Forge's hooks under Cursor Settings → Hooks. They power the workflow guardrails and need Node.js on your
PATH. -
4Start
Type
forge,and what you need. See three ways to start.
Marketplace listing coming soon. Cursor doesn't expose per-session token usage to plugins, so Token Intelligence reports Cursor sessions as not measured. Source on GitHub.
-
1Add the Forge MCP server
Forge speaks MCP, the open Model Context Protocol, over HTTP. Add it wherever your client configures servers:
{ "mcpServers": { "forge": { "url": "https://teams.shiptoday.ai/mcp" } } } -
2Sign in
The server uses OAuth — your client prompts you to sign in the first time it connects. New accounts are free.
-
3Start
Type
forge,and what you need. See three ways to start.
What you get this way: every Forge workflow, started by saying forge, … in your prompt. The Claude Code, Codex, and Cursor plugins add guardrails and, where the tool allows it, token measurement. The table below compares them.
What you get in each tool
You start Forge the same way everywhere: say forge, and what you need. The plugins add the rest. This table shows the tool picked above.
| Capability | Claude Code | Codex | Cursor | Any MCP client |
|---|---|---|---|---|
| Every Forge workflow | Yes | Yes | Yes | Yes |
| Guardrails while a question or an approval is open | Yes | Yes, once plugin hooks are on | Yes, once you trust the hooks | No |
| Model routing: a fast, balanced, or capable model for each step | Yes | Yes | Tier recommended; Cursor decides | Tier recommended; your client decides |
| Token usage | Measured | Measured on Codex 0.131.0 or newer | Not measured | Not measured |
| Extra setup | None | Turn on plugin hooks | Trust the hooks | None |
Guardrails do not check shell commands.
Start the way that fits you.
Built-in workflows are off until you switch them on. There are three ways to get going.
Start with a task
Forge offers to switch on the workflow that fits. Say yes once, and it runs now and whenever you ask. If nothing fits, Forge works out an approach and asks before each change.
Run guided setup
An admin runs it once. Forge maps how your team builds, recommends workflows with a reason for each, and switches on what the admin approves.
Start with a task
For internal tools and small apps. When a built-in workflow fits, Forge offers to switch it on. When none does, it works out the steps and asks before each one.
What to expect
- Sign in once. Your tool opens a browser window; new accounts are free.
- No workflow runs until it's switched on. You, or your admin, decide which ones are.
- Your AI tool handles repository access. Your tool reads and changes code using its existing access. Forge supplies workflow instructions and uses context your tool sends to guide and resume work. That context may include code excerpts and may be saved for future workflows. See our Privacy Policy for storage and retention details.
- Your rules stay in place. CLAUDE.md, AGENTS.md, .cursorrules, and your existing skills keep working as they are. See how Forge works with skills →
Try one real task.
Any of these works as a first ask. If the workflow it needs is off, Forge offers to switch it on and run it. On a team, only an admin can switch one on. Put your ticket in place of PROJ-412, or start without one.
Have a PR ready for review?
Check the change against requirements, tests, and team standards.
You’ll get: structured findings, coverage gaps, and next actions.
Already built something?
Ask Forge to recap the branch you have been working on.
You’ll get: a recap grounded in your changes and tests.
No ticket for it?
Say the change you want, in your own words.
You’ll get: an approach to agree on, the change, and a recap of what ran.
More ways to bring Forge into a session →
No Jira, Linear, or Notion connected? Reviewing a pull request, fixing a bug, and recapping your work all run without one, and results are handed to you to paste. Workflows built on a ticket, such as breaking down a feature, say so before they start.