SlopCamera is a media studio for coding agents. Your agent works with editable source and a media project. The CLI checks and renders them, and a revision keeps those inputs available for the next version. Choose a guide for the work you want to do.
It works with Claude Code, Codex, Cursor, and other coding agents through the CLI, the Agent Skill, and an MCP server. The source can be a diagram, an HTML animation, a 3D scene, a Blender, CadQuery, or Manim program, or edit decisions over your own footage.
Install the current SlopCamera release for the CLI, SDK and matching Agent Skill. Each guide lists the tools it needs and explains when an example requires a source checkout. The capability reference covers formats, interfaces and local runtime requirements.
- Create and revise your first animation: send a midnight tram toward the moon, enlarge the moon, and keep both films.
- Create and revise your first diagram: make a two-node diagram, inspect its five exports, then change its source.
- Render your first native film: retain a Blender source, render a small shot, and export an ordinary SlopCamera project.
-
Remix the showcase: open the finished films, study the creative decisions, and make your own version.
-
Direct a film: write a useful brief, test the hardest shot, and refine composition, movement, and sound.
-
Run current-source commands: build an exact checkout of SlopCamera.
-
Prepare patent-style drawing sheets: retain diagram source, check physical bounds, and render monochrome SVG sheets and a PDF.
-
Paint a deterministic oil study: mix named pigment tubes into piles, carry wet paint with bounded bristles, and replay the result.
-
Render motion graphics from HTML: choose among seven authoring profiles, render a graphic, and retain its source.
-
Direct a film or animation style: use reusable art direction and render the original style studies; requires current source.
-
Edit and deliver video: import footage, align related tracks, place overlays, and check a delivery.
-
Make a music video from an HTML scene: render authored visuals with a local track and retain separate sources in an editable project.
-
Convert raster images to SVG: trace artwork locally, compare a duotone treatment, and inspect fidelity.
-
Generate images, video, or narration: discover Gateway capabilities, acknowledge selected uploads, and retain the result.
-
Make a scrolling pixel landscape: compare continuous backgrounds and turn them into palette-checked alpha pixels.
-
Direct short generated clips: budget, review takes, preserve endpoint continuity, and recover uncertain work.
-
Render Blender, CadQuery, and Manim films from source: use Blender, CadQuery, or Manim; retain caches; share assets and calibrated cameras.
-
Build and revise a parametric design: generate architectural models from retained parameters, inspect dependencies and render alternatives.
-
Render and edit Three.js 3D scenes: patch named entities, use hardware rendering, import a saved world, or prepare a V2 shot composition.
-
Build a directed cinematic character world: admit a rigged world, direct it semantically, plan effects and galleries, and audit temporal evidence.
-
Plan camera moves, lighting, and effects for a 3D scene: author an inert recipe pack and run the
cinematic-worldplanning-and-review workflow. -
Make a math explainer video with Manim: keep mathematical visuals, narration, and timing evidence revisable.
-
Make web-ready 3D assets with Blender: bake detail onto a light mesh, export GLB levels of detail, and check budgets.
-
Run or recover a workflow: use a built-in recipe or trusted Bun module and inspect its durable run.
-
Configure Vercel, publish SlopCamera, operate the hosted API, or file a platform submission: provider and maintainer procedures.
- Capabilities, versions, and platforms: formats, commands, platforms and runtime requirements.
- SDK surfaces: portable and local imports, operation projections, and execution contracts.
- Techniques catalog: every packaged technique by job, with its first command, guide, and a rendered example where one exists.
- CLI help: exact grammar and JSON schemas from the installed host.
- Source, representations, and projects: what stays editable, what a receipt proves, and how local and cloud work fit together.
- Extension architecture: the closed registry, inert recipe packs, trusted workflows, and where authored code can and cannot go.
- Why SlopCamera: why the agent keeps a source file and reuses installed techniques, with comparisons to Remotion, HyperFrames, and other tools.
- Does installing SlopCamera cut Claude Code token costs?: a controlled study of four media tasks, with the harness and raw results in
bench/token-savings. - Choose an HTML authoring surface: why DOM, vector, Three.js, and explicit GPU profiles serve different jobs. Its ecosystem research is dated separately from its supported locks.
The SlopCamera Agent Skill routes an agent to the relevant task reference. Install the skill from the same release or source build as your CLI; installing a skill alone does not install the CLI or native tools. See the installation instructions.