Beta Coming soon. This feature is still being built, so names and details may change before it ships.

Missions

A mission takes a goal from plan to pull request. The agent writes a plan, you review it, then it works step by step and runs your project's checks after every step. At the end you get a proof of what changed and a Ship button that opens the pull request.

Start a mission

Type /mission <goal> in the agent chat. It is also in the / menu.

The agent first reads the project in a read-only turn, then writes a plan:

  • the goal
  • the files it expects to touch
  • the steps, each with the files that step touches
  • the tests it will add or run
  • the risks

Review the plan

The Mission card above the chat box shows the plan with three buttons:

  • Approve and run starts the first step.
  • Edit plan opens the plan as plain text in the same format. Ctrl/Cmd+Enter saves, Escape cancels.
  • Cancel drops the mission.

Tick Let missions run without plan review to skip this card and start right after the plan is written.

Step by step

Each step runs as its own agent turn. After the step, Ingot runs the project checks it found:

  • the gate, test, lint and typecheck scripts in package.json
  • or the test command for the project's manifest, such as pytest, go test or cargo test

A failing check becomes a fix turn: the agent gets the failure and fixes it, then the checks run again. A step can take up to 3 fix turns (a setting). If the checks still fail, the mission stops and says why.

Steps tick live on the card and in the chat checklist.

Edits still go through Agent review (Accept / Reject) unless auto-accept is on. The checks run once you have decided the step's edits.

Proof

When the mission ends, the card shows the proof:

  • what changed, with lines added and removed per file
  • the last result of every check
  • files changed outside the plan
  • steps that were not done
  • the plan's risks

The plan and the proof are saved to .ingot/artifacts/missions/<date>-<goal>.md. Project layout keeps this folder out of git.

Ship

A finished mission goes all the way to a pull request. Click Ship: commit, push and open a pull request on the proof, or let it happen on its own for a verified mission with the after-the-mission setting on ship automatically. Ingot:

  1. creates feature/<goal>, unless you are already on a feature branch
  2. commits only the files the mission changed, with the attribution trailer (Co-Authored-By: Ingot)
  3. pushes with upstream
  4. opens a pull request whose description is the plan and the proof, through your connected Git Hosts account

Without a connected account, it links the host's new pull request page instead. See Ship.

With Follow PR to green on, the agent then watches the pull request and fixes failing CI and review comments.

Project map

Every agent run, missions included, starts with a ranked overview of the open project:

  • languages and frameworks
  • entry points
  • build and test commands
  • top folders
  • the most-imported files, with their exported names

It fits in 2,000 tokens by default. Ingot builds it on the backend, caches it and rebuilds it a few seconds after files change. Run Ingot: Show Project Map to write it to .ingot/cache/repo-map.md and open it.

Symbol tools

Two agent tools find code by name:

ToolWhat it returns
ingot/find_symbolwhere a function, class, type or variable is declared: workspace symbols from the language servers plus a declaration search
ingot/document_symbolsthe outline of one file

When no language server covers the file, both fall back to a declaration search and say so.

Run a mission headless

ingot agent run runs one mission from the command line, for CI and scripts. It uses the same prompts, mission engine and project map as the IDE.

For now it runs from a clone of the Ingot repo as npm run ingot -- agent run …; the installed ingot CLI gets it in a coming release.

ingot agent run --task <file> [--repo <dir>] [--json]
  • The mission runs in a temporary folder, a detached git worktree of --repo. The folder is removed afterwards; --keep keeps it.
  • The run is scored on the end-to-end outcome: the feature works (hidden tests copied in after the run), the project checks pass, a pull request with the proof is open, and the diff stays in scope. The score also lists steps done, fix turns, tokens and time. --json prints it as JSON.
  • By default the pull request is recorded in a bare repository next to the temporary folder. --ship gh pushes to origin and runs gh pr create instead.
  • Pick the model with --model anthropic/<id> (ANTHROPIC_API_KEY), --model openrouter/<id> (OPENROUTER_API_KEY) or --model ingot/<id> (INGOT_EVAL_TOKEN, with --server), or set INGOT_AGENT_MODEL. Without the key, the run reports skipped.

Settings

Under Settings › Agent tools › Missions:

SettingDefault
Missions on or offOn
Let missions run without plan reviewOff
Fix turns per step3
Run multi-step requests as missions without /missionOff
After the mission: Ship button, ship automatically, or offShip button

Under Settings › Agent tools › Project map: on or off, and its size (2,000 tokens by default).

Settings › Features and the first-run setup list it as Missions.

The desktop app and the browser work the same way.