A run started through the API or the MCP trigger_agent_run tool can now carry data for the agent to work on, not just a repository and a pull request:

curl -X POST https://api.ferrfleet.com/agents/my-agent/runs \
  -H "authorization: Bearer $FERRFLEET_TOKEN" \
  -H "x-ferrfleet-org: $ORG_ID" \
  -H "content-type: application/json" \
  -d '{"input": {"url": "https://example.com/item/42", "notes": "check the price"}}'

The agent finds it in the event context of its prompt under payload. It sits there rather than at the top level so it cannot override the fields FerrFleet sets itself, such as the repository a run is scoped to. The MCP tool already sent input; until now the API dropped it.