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.
| Interface | Surface |
|---|---|
| Agent Skill | Version-matched instructions installed by slopcamera skill install --target agents (or slopcamera skill install --target claude for Claude Code) |
| CLI | The 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 server | slopcamera mcp --root <workspace> exposes a fixed toolset inside one selected root; see Use SlopCamera from an MCP client |
SlopCamera exposes ten operation codes: diagram check/render, image generate/vectorize, image icon/gallery, icon compose/render, and soundtrack compose/grid. Its MCP server has 21 named tools: check_diagram, render_diagram, search_slopcamera, execute_slopcamera, 13 scene tools for inspection, evaluation, direction, effects, behavior, and temporal audits, and compose_icon, render_icon, compose_soundtrack, and derive_soundtrack_grid. The icon compose/render and soundtrack compose/grid codes, their MCP tools, and the image icon compose|render and media soundtrack compose|grid commands were introduced in v3.9.0; they run locally with no model or network request. The complete local host has a separate, larger closed registry. No surface accepts caller-registered operations.
Install the release
bun add --global https://github.com/hraness/slopcamera/releases/download/v3.10.3/hraness-slopcamera-3.10.3.tgz
The verified release is published at https://github.com/hraness/slopcamera/releases/tag/v3.10.3 and requires Bun 1.3.14 or newer on macOS, Linux, or Windows. Build SlopCamera from source to develop SlopCamera or follow main.
Verified release contents
The published release provides these capabilities. Run slopcamera --version and the installed command's help when you need to check a particular installation.
| Capability | SlopCamera v3.10.3 | ||
|---|---|---|---|
| HTML scene export, all seven authoring profiles, music-clock helpers, audio-reactive bands | Included | ||
| Blender, CadQuery, Manim, seven native starters, retained video takes | Included; runtime/provider requirements apply | ||
| Spatial scenes, calibrated camera tracks, hardware/Spark profiles, saved-world import | Included | ||
Static capabilities --json manifest; image icon and candidate-gallery recipes | Included | ||
| Local icon.place and Soundfish commands: `image icon compose\ | render and media soundtrack compose\ | grid` | Included; no model or network request |
| Scene builders/admission, audits, rendered galleries, vision critique, character/performance and cinematic camera APIs | Included | ||
| Scene effects, particles, simulation bakes, semantic direction, temporal/behavior audits, project cinema plans | Included | ||
Seventeen read-only visual style profiles (style list and style show), deterministic exposure and variation helpers, film-finishing controls | Included; authoring guidance, no effects applied | ||
Launch films: html init --template launch-film, html still, html preview, html deliver, and the local/html-film motion helpers | Included; html deliver needs FFmpeg | ||
Terminal status: status, tui, commands --json, outputs list, and on macOS `outputs open\ | reveal and legacy retire` | Included; the menu-bar companion is removed | |
| Built-in workflows | Eight, including cinematic-world; inspect workflows list | ||
| New screen, camera, microphone, or system-audio capture | Absent |
The static and rigged/morph GLB profiles have separate admission limits within this release. Model, browser, native-engine and hardware availability still require inspection on the machine doing the work; presence in an archive is not a live qualification result.
This release includes the three renderer corrections introduced in v3.3.4 that v3.3.1 lacks: static-overlay duration and positioned-layer RGB blending in project exports, and negative-color handling in saved-splat rendering. The project-cinema commands ship in v3.3.1 and later; reproduce an example that depends on these corrections with v3.3.4 or later, or with a source build.
Parametric architectural designs
SlopCamera v3.10.3 includes scene design catalog|init|inspect|set|compile|gallery and portable design helpers in @hraness/slopcamera/code. Named dimensions and constraints compile into retained geometry and ordinary scenes. Four original starters include materials, lights, and cameras. Inspection and compilation run locally with the SlopCamera CLI; rendering uses the existing spatial browser runtime. Follow the parametric design guide.
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. The CLI and the Bun package are separate interfaces with separate installation requirements.
Discover the installed contract
| Need | Discovery command |
|---|---|
| CLI version and top-level commands | slopcamera --version, slopcamera --help |
| Grammar for a command family | slopcamera help project, slopcamera help studio, slopcamera help scene |
| Local tools and readiness | slopcamera doctor --json |
| Closed operation catalog and exact schemas | slopcamera operations list --json, slopcamera operations show <kind>[@<version>] --json |
| Built-in workflow input schema | slopcamera workflows list --json, slopcamera workflows show <id> --json |
| Live Gateway model capabilities | slopcamera ai models list --type <type> --json, slopcamera ai models show <id> --json |
| Static capability manifest | slopcamera capabilities --json |
| HTML scene export | slopcamera help html, slopcamera html render --input <scene.json> --dry-run --json |
| HTML profile locks | slopcamera html catalog --json |
| Version-matched packaged agent instructions | slopcamera skill path |
Runtime and platform requirements
| Work | Required runtime and boundary |
|---|---|
| Diagram JSON, SVG/PNG, and tldraw export | Bun package and bundled rendering dependencies; no tldraw app required |
| Vectorization | Bounded macOS/Linux profile; checksum-pinned VTracer can be obtained on first use. Windows deliberately rejects this profile |
| Ordinary media and delivery | FFmpeg and FFprobe; doctor reports additional analysis dependencies |
| HTML or Three rendering | Admitted local Chrome runtime and declared assets; dependencies may need initial verified provisioning |
three-webgl2-hardware-v1 | Qualified macOS ANGLE Metal WebGL2 context; software or unknown fallback rejects |
three-spark-webgl2-hardware-v1 | Separate qualified Spark profile for bounded saved splats; its format, camera, and output limits apply |
| Blender | Explicit executable selection; CPU or requested GPU, and a GPU request never silently falls back to CPU |
| CadQuery and Manim | Explicit Python environment; Manim uses its qualified Cairo profile and owns silent visuals |
| External vgpu native example | Separately 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 an existing finished recording bundle, a successful studio or directing assembly, or 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_KEYbeforeVERCEL_OIDC_TOKENin the local process environment, never persist credentials, pin the Gateway origin, and send withmaxRetries: 0. - Hraness Credits:
slopcamera creditscontactscredits.hraness.comto buy credits and read the balance, and hosted image generation sends one prompt and model ID toapi.slopcamera.comwith the stored device token. - 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.
Native browser requirements
Native HTML rendering uses a private copy of a supported, Google-signed macOS Chrome runtime and checks it before rendering. A Chrome for Testing build with an ad-hoc signature does not meet that native-renderer requirement. Run slopcamera doctor --json to inspect the tools available on your machine.
CLI updates
Automatic updates require SlopCamera 3.10.0 or newer. Upgrade an older installation once through its package manager.
Supported Bun and npm global installations on macOS and Linux check for a newer release at most once a day before a command starts. Automatic updates are enabled by default. Help, version output, CI, and commands already running do not trigger an update. If another command is using the installation, the update waits for a later invocation.
slopcamera update status --json
slopcamera update check
slopcamera update
slopcamera update disable
slopcamera update enable
Set HRANESS_NO_UPDATE=1 to suppress automatic updates for an invocation. Exact Bun version installs stay pinned until update enable. Ordinary Bun ranges, tags, and GitHub release archive installs track newer releases. npm does not reliably retain the original global version constraint; use update disable to keep an npm global at its installed version.
Source checkouts, local project dependencies, temporary bunx or npx installs, linked copies, and copied skill scripts keep their existing update process. On Windows, update through the package manager. Library imports do not check for updates or change installed code.
The updater stores its preference, last check time, and installation/process records locally. It keeps verified archives beside the global installation because the package manager may reference them. Keep an archive while the installation references it. Update checks send no application data to the release service.
Updates use immutable GitHub releases. An authenticated GitHub CLI (gh) checks the archive against its release and verifies its attestation against the release tag, source commit, and GitHub-hosted release workflow. Local image vectorization, diagrams, local icons, and soundtrack composition stay offline. Private compiled binaries use their native installer and do not update automatically.