Skip to content

Changelog

A record of released, shipped changes to Rover Nexus, newest first.

This page lists changes that have already shipped to customers. It is not a roadmap and does not list planned work.

2026-09-19

REST API

  • Added nested reads for mission templates, features, and tracked objects, plus GET …/objects/{object_id} and GET …/features/{feature_id}.
  • Added POST …/stop-all to pause every active robot in a fleet, matching Agent API control-robot stop_all.
  • Added PUT …/field-rules/{directive_id}/active to enable or disable a Field Rule without a full upsert.
  • Added Agent API tools control-feature and upsert-field-rule, plus object as a query-entities / get-entity kind.
  • Extended control-robot so mode, invoke_action, and update_settings accept bulk robot lists, split into one command per robot.
  • Extended control-operation with enable_mission and disable_mission.
  • Added Agent API edit-schedule for updating an existing mission schedule, including optional retry_limit and retry_interval_secs on schedule intake.

2026-08-04

REST API

  • Added the 15-tool Agent API, including single-call submit-job, live schedule diagnosis, bulk robot control, and typed entity queries.
  • Added GET /openapi.json with an OpenAPI 3.1 contract for mounted REST and Agent API routes.
  • Added nested mission-template authoring, feature deployment, tracked-object endpoints, and Field Rules CRUD.
  • Added GET /v1/events for correlated fleet event timelines and richer mission schedule and run filters.
  • Made mission deployment responses explicit and asynchronous. deploy-mission now returns scheduleId and status: "scheduled".
  • Added durable, actor-scoped idempotency for mission-template and schedule creation workflows.
  • Added optional bounded robot acknowledgement waits and structured delivery outcomes, including 207 partial_failure and 422 policy_rejected.
  • Added opaque keyset pagination to Agent API entity queries.
  • Removed obsolete plan, export, nested activity-log, flat mission-schedule write, and flat mission-template write routes. Integrations should use the Agent API and nested authoring routes documented in this API reference.