Skip to content

Update navigation pages for the API rework in RDK v1.13.0 - #5447

Merged
Eliza Farley (elizafarley) merged 2 commits into
mainfrom
claude/update-navigation-v1-13-removal
Oct 21, 2026
Merged

Eliza Farley (elizafarley) merged 2 commits into
mainfrom
claude/update-navigation-v1-13-removal

Conversation

@shannonbradshaw

Copy link
Copy Markdown
Collaborator

RDK v1.13.0 removes the rdk:builtin:builtin navigation model and replaces the navigation API that the two (discontinued, orphaned) navigation pages document. This PR adds that to each page's existing Discontinued alert, so a reader who follows the JSON template or calls SetMode on a current viam-server knows why it fails. It does not rewrite the pages.

Source changes

  • RSDK-14608 — Refactor navigation service rdk#6643: "Refactor navigation service". Moves RDK's navigation client, server and interface to the reworked API and deletes services/navigation/builtin. In RDK v1.13.0 (git merge-base --is-ancestor e5e32c22b v1.13.0; v1.13.0 pins go.viam.com/api v0.1.597).
  • RSDK-14608 — Rework Navigation API api#917: the reworked NavigationService. It has saved locations, routes and zones (Add/Get/List/Update/Delete each), NavigateToLocation, NavigateToPoint, NavigateRoute, PlanToPoint, PlanToLocation, ExecutePlan, GoToLocation, GoToPoint, Suspend, Resume, Cancel, GetPosition, GetNavigationStatus, GetProperties and GetCostmap. GetMode, SetMode, GetWaypoints, AddWaypoint, RemoveWaypoint, GetObstacles and GetPaths are gone, and GetLocation returns a saved location.
  • Automated Protos Update viam-python-sdk#1291 (in v0.85.0) and Automated Protos Update: Dart wrappers viam-flutter-sdk#577 (in v0.23.0) move those SDKs' navigation clients to the new API. The TypeScript SDK (v0.77.0) still ships the old client.
  • APP-18273 — viamrobotics/app#13992 (already live) removed the app's builtin navigation config card.

Documents: no DOCS ticket found for RSDK-14608, APP-18273 or their parent RSDK-14607.

Docs changes

  • docs/reference/services/navigation/_index.md: the alert now says viam-server v1.13.0 and later no longer include the rdk:builtin:builtin navigation model the page configures.
  • docs/reference/apis/services/navigation.md: the alert now says which versions replace the API, names the removed methods, and says GetLocation returns a saved location.

Needs a human decision

The navigation API in viam-server, Go, Python and Flutter is now the location/route/zone API, but the docs only describe the old one, and navigation is deliberately excluded from sdk_protos_map.csv (docs CLAUDE.md). Documenting the new API, or removing these pages, depends on whether the navigation service is coming back. That decision is out of scope here.

Not changed: docs/monitor/default-interface.md lists a "Navigation service" CONTROL card. The card comes from the external @viamrobotics/test-widgets package, which I couldn't check from source, so I didn't change the row.

How I found these

  • Xref lookup: service-api-xref.md → navigation.
  • Grep matches: navigation service, services/navigation, rdk:builtin:builtin, SetMode, waypoint across docs/, static/, data/, layouts/. The other rdk:builtin:builtin matches are the motion, data manager and base remote control services. connectivity.md, helmet.md and cli/reference.md mention the service only in passing.

Checks

prettier (repo-local 3.2.5), markdownlint, vale, frontmatter_rules.py and make build-prod pass.


Generated by daily docs change agent


Generated by Claude Code

rdk#6643 (RSDK-14608), released in RDK v1.13.0, moves viam-server and the Go
SDK to the reworked navigation API (api#917) and deletes the builtin
navigation model. Python v0.85.0 and Flutter v0.23.0 ship the same API.
@netlify

netlify Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit 16a1aa1
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/6ad8c9d6cf44cd0393c19d12
😎 Deploy Preview https://deploy-preview-5447--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 41 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 60 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Oct 21, 2026
@elizafarley

Copy link
Copy Markdown
Contributor

Docs review: Ready to merge

This PR adds a line to the existing Discontinued alert on both navigation pages, saying that RDK v1.13.0 removed the rdk:builtin:builtin model and replaced the navigation API. I checked every claim against the RDK v1.13.0, API v0.1.597, Python SDK v0.85.0, and Flutter SDK v0.23.0 tags, and each one holds.

CI: All required checks passing (the Netlify header-rules and pages-changed checks were skipped)

Docs health: No regressions

Nits

  • docs/reference/apis/services/navigation.md:22: The generated API section on this page still has TypeScript tabs, and TypeScript SDK v0.77.0 still ships the old client (getMode/setMode in src/services/navigation/client.ts). The alert lists only the SDKs that moved to the new API. A TypeScript reader might assume their SDK still works, but its calls to the old RPCs will fail against viam-server v1.13.0. Fix: Consider adding a clause like "The TypeScript SDK still uses the API on this page, which viam-server v1.13.0 and later don't serve."
Verified against source (7 claims)
  • RDK v1.13.0 removes services/navigation/builtin (the rdk:builtin:builtin model): viamrobotics/rdk v1.13.0 tree has no services/navigation/builtin/; it exists at v1.12.0 (services/navigation/builtin/builtin.go)
  • The refactor is in v1.13.0: e5e32c22b Refactor navigation service (#6643) is an ancestor of v1.13.0; go.mod pins go.viam.com/api v0.1.597
  • The new API is built around saved locations, routes, and zones: viamrobotics/api v0.1.597 proto/viam/service/navigation/v1/navigation.proto (Add/Get/List/Update/Delete for Location, Route, Zone)
  • GetMode, SetMode, GetWaypoints, AddWaypoint, RemoveWaypoint, GetObstacles, GetPaths no longer exist: absent from the rpc list in the same proto. The list covers every non-generic method in navigation-table.md except GetLocation and GetProperties, which still exist
  • GetLocation returns a saved location: navigation.proto:417 GetLocationResponse { Location location = 1; }, :264 "Location is a named Position on the active map"
  • Python SDK v0.85.0 uses the new API: Automated Protos Update viam-python-sdk#1291 is in v0.85.0 and not in v0.84.0; src/viam/services/navigation/client.py@v0.85.0 has add_location…get_costmap and no set_mode
  • Flutter SDK v0.23.0 uses the new API: Automated Protos Update: Dart wrappers viam-flutter-sdk#577 is in v0.23.0 and not in v0.22.0; lib/src/services/navigation.dart@v0.23.0 has addLocation…getCostmap

Automated review by Claude. Rerunning the review updates this comment.

TypeScript v0.77.0 still calls GetMode, SetMode and the other removed RPCs,
which viam-server v1.13.0 and later don't serve.

Copy link
Copy Markdown
Collaborator Author

Fixed in 16a1aa1: the API page alert now adds "The TypeScript SDK still uses the API on this page, which viam-server v1.13.0 and later don't serve."


Generated by Claude Code

@elizafarley
Eliza Farley (elizafarley) merged commit 5f52fba into main Oct 21, 2026
14 checks passed
@elizafarley
Eliza Farley (elizafarley) deleted the claude/update-navigation-v1-13-removal branch October 21, 2026 14:50
@github-actions

Copy link
Copy Markdown

🔎💬 Inkeep AI search and chat service is syncing content for source 'Viam Docs'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to build This pull request is marked safe to build from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants