Slopcamera documentation

Learn, use, and extend Slopcamera: tutorials, task guides, reference, and explanation for agent-driven visual work.

Slopcamera is a local visual studio for coding agents. It retains editable sources, renders local or generated media, and assembles everything into inspectable projects on your machine. These pages describe Slopcamera from current source.

Install the verified v3.2.6 release, or build from source for the complete capability set:

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

Then give your coding agent the matching guidance:

slopcamera skill install --target agents
# For Claude Code:
slopcamera skill install --target claude

Learn by making something

• Create and revise your first diagram: make a two-node flow, inspect its five exports, then change a label by editing the source.
• Render your first native film: retain a Blender source, render a small shot, and export an ordinary project.

Set up your coding agent

• Claude Code: install the release and the Agent Skill so Claude Code can create visual media.
• Codex: install the release and the Agent Skill inside a repository.
• MCP clients: expose the fixed diagram and image toolset to Cursor, Claude Desktop, and other MCP-capable clients.
• Other agents: the portable skill target and plain CLI access.

Complete a task

• Build Slopcamera from source: record the commit, install locked dependencies, and build the SDK and CLI.
• Edit and deliver video: import footage, align related tracks, place overlays, and check a delivery.
• Generate images, video, and narration: discover Gateway capabilities, acknowledge selected uploads, and retain the result.
• Make an educational video: keep mathematical visuals, narration, and timing evidence revisable.
• Make a music video: render authored HTML visuals with a local track.
• Render and edit spatial scenes: patch named entities, use hardware rendering, or import a saved world.
• Author a native film: use Blender, CadQuery, or Manim and share assets across renderers.
• Direct short generated clips: budget, review takes, and preserve endpoint continuity.
• Run or recover a workflow: use a built-in recipe or trusted Bun module and inspect its durable run.

Look up a contract

• Capabilities, versions, and platforms: release availability, supported profiles, and runtime requirements.
• SDK surfaces: portable and local imports, operation projections, and execution contracts.
• The Slopcamera engine stack: what each part of the multimedia engine does, needs, and where its limits are.

Understand the design

• Source, representations, and projects: what stays editable, what a receipt proves, and how local and cloud work fit together.
• Why Slopcamera: what a retained-source local studio gives an agent that a loose toolchain does not.
• Extend Slopcamera: workflows, declarative graphs, the SDK, MCP, and separately installed native engines.
• Choose an HTML authoring surface: why DOM, vector, Three.js, and explicit GPU profiles serve different jobs.

Every page is also available as Markdown: request any page with Accept: text/markdown or append .md to its path.