Is Magic Dev Down?

If Prismix shows Magic Dev as "Operational" but you're having issues:

• Agent loop stuck on ambiguous task (no clarification prompt) — Magic Dev's agent executes tasks autonomously without pausing to ask clarifying questions mid-run. If your task description is ambiguous (e.g., "fix the bug" without specifying which file or behavior), the agent may loop indefinitely or produce an incorrect fix. Write detailed task prompts that include the file path, expected behavior, and reproduction steps.
• PR diff too large to apply cleanly — Magic Dev generates a single PR containing all changes for a task. When the generated diff is very large (thousands of lines) or touches many files simultaneously, applying it can fail with merge conflicts against your current HEAD. Break large tasks into smaller, incremental sub-tasks to keep PR diffs reviewable and conflict-free.
• Git conflicts on parallel agent runs — running multiple Magic Dev agents concurrently on the same repository can produce conflicting commits if they both modify shared files. Serialize long-running tasks or scope each agent to a separate feature branch to avoid cross-agent conflicts during simultaneous execution.
• API webhook timeout on long-running tasks (over 10 minutes) — Magic Dev's task completion webhook has a delivery timeout. Tasks that run longer than 10 minutes may complete successfully but fail to deliver the webhook notification, making the task appear stuck. Poll the task status endpoint directly for long-horizon tasks instead of relying solely on webhook delivery.
• Repo access token expiring mid-task — Magic Dev uses a short-lived GitHub access token scoped to your repository. If a task runs past the token expiry (typically 1 hour for OAuth tokens), subsequent Git operations within the task will fail with a 401 error. Re-authenticate the integration from the Magic Dev dashboard to refresh the token before starting long tasks.
• Task output not written to expected branch — by default, Magic Dev creates a new branch for each task using an auto-generated name. If you expect output on a specific branch (e.g., main or a named feature branch), configure the target branch explicitly in the task parameters before submission.