Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

2.4 KB
Raw Blame

Autonomous Workshop, as a Harness agent

Harness agent package for Autonomous Workshop: describe a part in the chat pane and get a validated, printable STEP, with a live 3D view in the pane beside the agent. Runs on Codex.

This folder is a wrapper. It holds no Workshop code: toolchain/setup.sh fetches the project from its own public repository at the commit VERSIONS pins (its Python package and harness folder; the toy library stays behind), into upstream/, and runs the project's own setup there (uv sync from its lockfile). The manifest points the agent at the project's own AGENTS.md, CAD skills and template, and the pane is the store's shared CAD Viewer.

  • harness.json — name, category, engine, paths into upstream/, viewer.use: autonomous/cad-viewer. formerly keeps agents created under the ids this harness had before (autonomous/toymaker, autonomous/solid, autonomous/workshop).
  • VERSIONS — the repository, the pinned commit on its main, and the sparse folders.
  • toolchain/fetch-upstream.sh — the read-only, sparse, blob-less fetch; setup.sh, doctor.sh and init-workspace.sh hand off to the project's scripts of the same names.
  • toolchain/runtimes.sh — the store's shared helper (a copy; store/tools/sync-runtimes.mjs writes it). The project's setup needs uv on PATH, which a new Mac lacks: the wrapper puts a pinned one there first (uv then brings the Python). The doctor finds it, and Node, the same way.

Credit and stewardship

Autonomous Workshop is its own project, autonomous-ai/autonomous-workshop, under its repository's licence (Apache-2.0). Nothing of it is changed or copied here. Harness treats it like any other project in the store: bugs in CAD generation belong in that repository, bugs in the wrapper belong here, and a newer Workshop is a bump of UPSTREAM_COMMIT in VERSIONS. If the Workshop team wants to own the store entry, the wrapper moves into their repository and the registry points there.

harness dsh check "$PWD"                           # conformance (warns: the project arrives with setup)
harness dsh install "$PWD" --link                  # this checkout as the installed agent
python3 -m unittest discover -s toolchain          # the scripts, against a local stand-in repository