zeon mesh-database
Browse the shared catalog of physical objects from the CLI.
zeon mesh-database is the CLI window into the shared mesh database, the same catalog the IDE's mesh-database browser and the main app's Object Database screen use.
| Subcommand | What it does |
|---|---|
zeon mesh-database list | List every item in the catalog |
zeon mesh-database show <name> | Show details for one item |
zeon mesh-database download <name> <dest> | Mirror an item's files to a local folder |
zeon mesh-database upload … | Admin-only: add a new item |
zeon mesh-database delete <name> | Admin-only: remove an item from the catalog |
For day-to-day "I want this object in my project" use, you'll usually run zeon new object <name>. This command set is for browsing what's available before you do.
zeon mesh-database list
zeon mesh-database listzeon mesh-database list
zeon mesh-database list --jsonPrints a table of every item in the catalog. Each row shows the name, a one-line description, and any tags that help with filtering (plate, cold-block, instrument).
zeon mesh-database show <name>
zeon mesh-database show <name>zeon mesh-database show coldblock_holder
zeon mesh-database show coldblock_holder --jsonPrints the item's manifest:
- The files that come with it (URDF, YAML, and any mesh files).
- The description.
- Any tags.
- Version info.
Use this when you want to be sure an item has the URDF + YAML pair you need before adding it to a project. A geometry-only item won't materialize via zeon new object.
zeon mesh-database download <name> <dest>
zeon mesh-database download <name> <dest>zeon mesh-database download coldblock_holder ./coldblock_holder
zeon mesh-database download coldblock_holder ./coldblock_holder --forceMirrors every file in the item's manifest (URDF, YAML, meshes) into <dest>. The directory is created if it doesn't exist, and must be empty unless you pass --force (-f), which overwrites any files that clash with the manifest.
This is read-only: anyone who can see the item can download it. It's the inverse of upload, and it's the way to get an item's raw files onto disk without going through a project. To pull an item into a project instead, use zeon new object <name>.
zeon mesh-database upload
zeon mesh-database uploadAdmin-only. Uploads a new item to the shared catalog. The server enforces the admin check: regular users get a 403.
If you need a new object kind added to the catalog, contact your Zeon contact rather than trying to upload directly. They'll need:
- The URDF and any mesh files (
.obj,.stl). - The
object_model.yamlwith anchors, articulations, and parts defined. - A description and any tags.
zeon mesh-database delete <name>
zeon mesh-database delete <name>zeon mesh-database delete coldblock_holder
zeon mesh-database delete coldblock_holder --yesAdmin-only. Removes an item's catalog row and every file under its storage prefix. Non-admin callers get a clean 403.
Before it removes anything it shows you what will be dropped (the file count) and asks you to confirm. Pass --yes (-y) to skip the prompt in scripts.
This is a soft delete at the catalog layer, not a hard purge. Storage keeps previous versions, so an accidental delete is recoverable through Zeon staff, but the item disappears from the catalog immediately for everyone.
When to use the CLI vs the web UI
The CLI's list and show give you the same info as the IDE's mesh-database browser, plus they're scriptable (--json everywhere). Use them when:
- You're already in a terminal and don't want to switch tabs.
- You're writing a script that checks "does the catalog have a
<name>before I try to add it?". - You want a quick grep through item names and descriptions.
For visual browsing (thumbnails, drag-into-world), the IDE or main app surfaces are better.
Where to go next
Updated about 2 hours ago