Skip to main content
Version: 2026-09-21 (current)

The dashboard

Everything about a hosted tool happens in the Voshi dashboard. Open Tools, pick your tool, and the tabs below are down the left side.

note

The dashboard calls tools "tools". These docs say tool for what you build and tool only where the API does; the two mean the same thing.

AI Builder​

Your tool's first page, and where it gets built. The page has two panels:

  • Discuss Design on the left is a conversation. Describe what the learner should be doing; the AI asks what it needs to know and says when it has enough. The build button (the wand) hands the whole conversation to the builder, which writes the tool and uploads it as your draft. A correction is just another message, followed by another build. A message that led things astray can be set aside (dimmed and struck through, reversibly) so the next build ignores it. New conversation starts over against the same tool; past conversations are kept.
  • Running Tool on the right launches your draft — a real launch, in your tool's Sandbox course. Choose which location to launch and whether to launch as a student or an instructor. Both roles share one course, so an instructor launch sees what the student launch just saved, exactly as in a real course. Refresh launches again.

The Running Tool header also holds the two code controls:

  • Download Code gives you the draft as a zip. It includes an AGENTS.md that briefs a coding assistant (Claude Code, Cursor, and the like) on the rules of a hosted tool, so you can edit the code outside the dashboard and bring it back.
  • Upload Code takes a folder from your computer and makes it the draft. Choose the folder that holds manifest.json, or that holds app.js if there is no manifest.

See Your tool's files for what is in the folder.

Sandbox​

A private practice course that only you can see, with your tool already in it. Its tabs mirror what a course has:

  • Links are placements of your tool in the Sandbox course. New Link opens the same picker an instructor uses, so you can place any of your locations and launch it as a student or an instructor. Reset throws away everything stored at a link, so the next launch starts as a first launch; Remove deletes the link.
  • Launches lists every launch in the Sandbox.
  • Grades is the Sandbox's gradebook: the scores your tool reported, by link and by persona.

The Sandbox always runs your draft. See Testing in the Sandbox.

Locations​

The destinations your tool offers an instructor — each with a name, an external ID (your tool's own, permanent identifier for it), a Voshi ID, and a type. Add Location adds one; Edit changes its label and type; Stop offering hides it from the picker without breaking links already placed. A tool with one activity has one location, home. See Locations.

Launches​

Every launch of your tool, from every course: when, which course, which user, which location, and whether it succeeded. Filter by course, user, or location to follow one student's path, or to see whether a particular placement is being used.

Grades​

Every score your tool reported, from every course, with the result the LMS gave. A score the LMS refused shows here with the reason. Open one to see the full record.

Pricing​

Whether a student pays to launch your tool, and how much, with different prices for different audiences. A tool with no prices is free. Pricing is described on the Pricing tab itself and on Voshi's website; it is not part of your code — a paying student is sent to checkout before your tool is launched, and your tool never knows the difference.

Settings​

The tool's identity: its Tool ID, its platform status, its hosting (which was fixed at registration), and the name and description instructors see.

Platform statusMeaning
DraftThe initial status. Instructors cannot see the tool, and it launches only from the Sandbox.
ActiveLive: instructors can add it to courses.
SuspendedDisabled by the platform team.

Only the Voshi platform team changes the status. When your tool works in the Sandbox and you have published a version, contact the MyEducator team to activate it.

A hosted tool has no API key and no URLs to configure, because it has no server. Those fields exist only for a self-hosted tool.

Team members​

Tools are managed by their members, and membership is flat: every member has full rights over the tool. The dashboard has no members screen yet — ask the MyEducator team to add or remove teammates.