Skip to content

DOCS-5059: Update model upload docs for the Robot policy task type - #5477

Open
Shannon Bradshaw (shannonbradshaw) wants to merge 1 commit into
mainfrom
claude/DOCS-5059-robot-policy-task-type
Open

Shannon Bradshaw (shannonbradshaw) wants to merge 1 commit into
mainfrom
claude/DOCS-5059-robot-policy-task-type

Conversation

@shannonbradshaw

Copy link
Copy Markdown
Collaborator

The Viam app's model upload form now has a Robot policy task type, but the upload steps still say to pick Other for "a model that controls an arm". This PR adds Robot policy to the task type list and drops that example from Other.

Source changes

  • APP-18203 — viamrobotics/app#14054 (233bca343, merged 2026-10-27, continuously deployed): adds a Robot policy ML model type to the app UI. It appears in the model upload and edit forms, with the description "Map sensor inputs, like camera images and joint states, to actions", and in the registry and model Task type filters. It is stored as robot_policy. Built-in training rejects it ("robot policy models are not supported for built-in training"), and deploying one doesn't offer a vision service.
  • APP-18203 — [APP-18203] Add MODEL_TYPE_ROBOT_POLICY for robot control policies api#932: adds MODEL_TYPE_ROBOT_POLICY = 4 to the ML training ModelType enum.
  • APP-18203 — [APP-18203] Accept robot_policy as an ML model type rdk#6674: the CLI side (--model-type robot_policy on viam packages upload and viam train submit custom with-upload, --type robot_policy on viam training-script upload) is merged but not in a published RDK release (after v1.14.0). The CLI reference is left for that release.

Documents: DOCS-5059

Docs changes

  • docs/vision/deploy-and-maintain/deploy-custom-model.md: adds Robot policy to the upload form's Task type list, with the arm-control example, and makes Other "none of these". Labels come from ModelTypeDisplays in ui/src/lib/ml-model.ts, and the option list from MODEL_TYPE_OPTIONS_WITH_OTHER in ui/src/lib/components/data/model-options.ts.

Left alone:

  • docs/train/overview.md's Task types section describes the built-in training wizard, which doesn't offer Robot policy. Open draft [DRAFT] Add how-to for training a VLA model #5412 (training a VLA) also edits that page.
  • The CLI tables in docs/cli/reference.md wait for the RDK release.

How I found these

  • Xref lookup: app-api-xref.md (MLTrainingService ModelType).
  • Grep matches: single_label_classification, "single label classification", "task type", MODEL_TYPE_, model_type and "robot policy" across docs/, static/, data/ and layouts/. Of 20 matches, only the upload form list describes the UI that changed. The rest are CLI tables (waiting on the release) or built-in training, which excludes the type.

Generated by daily docs change agent


Generated by Claude Code

app#14054 (APP-18203, deployed) adds Robot policy as an ML model task type
in the model upload and edit forms and the registry filters, backed by
MODEL_TYPE_ROBOT_POLICY (api#932). The upload steps still told users to
pick Other for a model that controls an arm.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Nja2Xo3uJzsMexV6Ff7RiB
@netlify

netlify Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit 98ca23f
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/6ae1c1a1775b6eae226df6f3
😎 Deploy Preview https://deploy-preview-5477--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: 37 (🔴 down 6 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 28, 2026

This branch has not been deployed

No deployments
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.

3 participants