Home › Prompts › Muse Spark Open (Meta, open weights) › Fix a bug from a screen recording with Muse Spark Open

Fix a bug from a screen recording with Muse Spark Open

Hand Muse Spark Open a screen recording with narration plus the relevant code, and get a timestamped diagnosis and a minimal patch.

Muse Spark Open (Meta, open weights)CodingRuleStack original

Written for Muse Spark Open (meta-models/Muse-Spark-Open-816B-A42B) · Updated 2026-10-18

Note: Review and test before use. Provided as is, without warranty. See Terms.

Attached: a screen recording of a bug in [app name] (with my voice narration) and the source files [list paths, or "the repo is mounted at [path]"].

1. Watch the video and list what happens with timestamps: each user action, what the UI shows, and anything I say about what I expected.
2. State the bug in one sentence: expected vs actual.
3. Find the most likely cause in the code. Quote the file and lines, and explain how the code produces what the video shows.
4. Propose the smallest fix as a unified diff. Don't refactor unrelated code.
5. Give a test (or manual steps) that would have caught it.

If the video doesn't show enough to be sure, say what extra recording or log would settle it instead of guessing.

Replace everything in [square brackets] with your own details.

Settings & parameters

• Muse Spark Open takes text, image, audio and video input (text output) with a 1M-token context
• Reasoning can't be turned off; set reasoning_effort medium or high for debugging (levels: low, medium, high, xhigh; xhigh is the default)
• In Transformers, pass load_audio_from_video=True so the narration is used; video is sampled at 2 FPS (max 96 frames) by default, so raise the FPS for fast UI glitches

Variations

• No narration: add a typed note with expected behavior and your device/browser.
• Multi-file regression: include the last good commit's diff and ask which change caused it.

Tips

• Hosted endpoints (Baseten, Fireworks AI, Groq, Modal, Nebius, OpenRouter, Together AI) expose it through OpenAI-compatible APIs; check each provider supports video input before relying on it.
• Keep clips short and focused on the bug; long recordings at low FPS can skip the frame that matters.