Slopcamera

Reference

Capabilities, versions, and platforms

Current Slopcamera capabilities, release availability, and supported runtime boundaries.

This page is the current contract for the Slopcamera CLI: what it produces, which surfaces each installation form provides, and where its runtime and trust boundaries sit. A package's version number alone does not identify a source checkout, so inspect the commit and the installed build's own command help.

Output families and interfaces

Slopcamera covers four output families: images, diagrams, animated loops, and video. Audio and captions are composable project inputs rather than another project model.

InterfaceSurface
Agent SkillVersion-matched instructions installed by slopcamera skill install --target agents (or slopcamera skill install --target claude for Claude Code)
CLIThe slopcamera command; reads and mutations support --json receipts
TypeScript SDK@hraness/slopcamera portable imports plus the complete-local-host ./local/* surfaces; see SDK surfaces
MCP serverslopcamera mcp --root <workspace> exposes a fixed toolset inside one selected root; see Use Slopcamera from an MCP client

The portable code search and code execute surface and the MCP server share four operations: diagram check, diagram render, image generation, and vectorization. The complete local host has a larger closed registry. Neither surface allows a caller to register arbitrary operations.

Install the release

bun add --global https://github.com/hraness/slopcamera/releases/download/v3.2.6/hraness-slopcamera-3.2.6.tgz

The verified release is published at https://github.com/hraness/slopcamera/releases/tag/v3.2.6 and requires Bun 1.3.14 or newer on macOS, Linux, or Windows. Build Slopcamera from source for the complete capability set, or to follow main. The historical Atet v3.2.3 archive contains @hraness/atet and the atet command; it does not install Slopcamera. Do not substitute the renamed package or executable into an old Atet archive URL, silently switch versions, or use historical paid-world commands as a substitute for the current saved-world workflow.

Release availability

SurfaceHistorical Atet v3.2.3Slopcamera v3.2.6
Diagrams, vectorization, Gateway media, recording, ordinary project edits, local workflowsAvailable with the relevant local tools and credentialsAvailable
Editable spatial scenes, calibrated scene cameras, V2 shots, Three hardware and Spark profiles, saved-world importAvailableAvailable
Paid World Labs world commandsPresent in the historical releaseRemoved; saved-world import and historical provenance replay remain
Retained short-video directing: directAbsentAvailable
Blender, CadQuery, Manim, and acquisition: studioAbsentAvailable
Native output admission: studio assetAbsentAvailable
Calibrated camera samples: scene camera-trackAbsentAvailable
External vgpu 0.4.1 native exampleAbsentExplicit example runtime; not a new registered studio engine

What requires the source-backed distribution

Durable workflow planning and execution bind a build identity over the installed host source tree. slopcamera workflows plan, slopcamera workflows run, slopcamera code check, slopcamera code plan, slopcamera code run, and slopcamera runs resume therefore require the Bun package or a source checkout — both ship the checked host sources — rather than a copied standalone executable, which embeds no physical source tree; Run or recover a workflow covers the run model. The same boundary applies to local SDK imports through @hraness/slopcamera/local/code.

Read-only catalog commands such as workflows list, workflows show, runs list, runs show, and operations list work from any install. The copied macOS executable supports direct studio commands with embedded starters and drivers. A desktop UI, a copied binary, and the Bun package are not interchangeable installation prerequisites.

Discover the installed contract

NeedDiscovery command
CLI version and top-level commandsslopcamera --version, slopcamera --help
Grammar for a command familyslopcamera help project, slopcamera help studio, slopcamera help scene
Local tools and readinessslopcamera doctor --json
Closed operation catalog and exact schemasslopcamera operations list --json, slopcamera operations show <kind>[@<version>] --json
Built-in workflow input schemaslopcamera workflows list --json, slopcamera workflows show <id> --json
Live Gateway model capabilitiesslopcamera ai models list --type <type> --json, slopcamera ai models show <id> --json
HTML profile locksslopcamera html catalog --json
Version-matched packaged agent instructionsslopcamera skill path

Runtime and platform requirements

WorkRequired runtime and boundary
Diagram JSON, SVG/PNG, and tldraw exportBun package and bundled rendering dependencies; no tldraw app required
VectorizationBounded macOS/Linux profile; checksum-pinned VTracer can be obtained on first use. Windows deliberately rejects this profile
Ordinary media and deliveryFFmpeg and FFprobe; doctor reports additional analysis dependencies
Screen, camera, microphone, and system-audio recordingNative macOS capture support and the selected operating-system permissions
HTML or Three renderingAdmitted local Chrome runtime and declared assets; dependencies may need initial verified provisioning
three-webgl2-hardware-v1Qualified macOS ANGLE Metal WebGL2 context; software or unknown fallback rejects
three-spark-webgl2-hardware-v1Separate qualified Spark profile for bounded saved splats; its format, camera, and output limits apply
BlenderExplicit executable selection; CPU or requested GPU, and a GPU request never silently falls back to CPU
CadQuery and ManimExplicit Python environment; Manim uses its qualified Cairo profile and owns silent visuals
External vgpu native exampleSeparately provisioned pinned Node and Dawn runtime; distinct from the browser overlay lock

Native studio qualification used Blender 5.2.1 LTS on an Apple M4 Max, CadQuery 2.8.0, and Manim Community 0.21.0. These observations do not certify every plugin, solver, device, or imported asset. The engine stack describes what each part does, needs, and where its limits are.

Ordinary project add and SDK media.ingest imports require an existing project. Creation starts from a stopped recording, a successful studio or directing assembly, or, in current source, an authored scene rendered with slopcamera html render. Arbitrary standalone files alone cannot create an empty project.

Trust boundaries

There is no Slopcamera account or hosted project database. Editing and rendering stay local, and these are the surfaces that can cross the network boundary:

  • Gateway model discovery and paid generation, which read AI_GATEWAY_API_KEY before VERCEL_OIDC_TOKEN in the local process environment, never persist credentials, pin the Gateway origin, and send with maxRetries: 0.
  • Selected cloud analysis and optional private Blob reference hosting, each behind its own acknowledgement.
  • Poly Haven asset acquisition and first-use runtime or tool provisioning.

Credentials and upload or trusted-code acknowledgements remain invocation-scoped: --allow-cloud-upload, --allow-cloud-audio-upload, --allow-paid-generation, --allow-reference-hosting, and --allow-trusted-code apply to one invocation, and a local source import does not authorize executing it or sending it to a model. Rendering from a prepared local closure does not upload a project.

Native studio jobs and custom Bun workflow modules run as the current user without an OS sandbox; hash receipts and process supervision provide provenance and control, not confinement. Directing budgets use catalog estimates, not provider-enforced spending caps.