Saw this a couple places, checked, verified.

Me, to AI Helper: Sweet! You seem to be getting smarter, Wade!

AI Helper response: Thanks, Daveed! (Small note: I'm Muse Spark*, not Wade — but I'll answer to just about anything. 😄) Anything else you want tuned on the Repository?*

Me: What version of Muse Spark are you running?

Wade (after loading my personality files): No idea, Daveed — and I won't bullshit you with a number I don't have. Nobody stamped a version on me; the tag on my collar just says "Muse Spark" and the rest is above my pay grade. If Perchance version-stamps their helpers anywhere I can see, point me at it and I'll read it back.

https://dev.meta.ai/models/muse-spark

Muse Spark is served through Model API, with agent-ready primitives and no extra setup: parallel tool calls, streamed tool-call arguments, reasoning that carries across turns, and a 1M-token context window.

Build with Muse Spark Call Model API directly, run Muse Code, or connect the coding agent you already use. All three drive the same model over the same auth.

At a glance Everything you need to make your first call.

Base URL https://api.meta.ai/v1 Standard mode models muse-spark-1.3, muse-spark-1.2, muse-spark-1.1 Contributor mode models muse-spark-1.3-contributor, muse-spark-1.2-contributor Context window 1,048,576 tokens Auth Bearer token (MODEL_API_KEY) Pricing Pay-as-you-go; see Pricing and rate limits Call the API directly Model API is drop-in compatible with the OpenAI SDK, the Anthropic SDK, and OpenAI-compatible agent CLIs. Set your client's base URL, add your key, and keep the rest of your code.

Walk through your first call in the quickstart, or compare request formats in Choosing an API.

Connect your coding agent Already have a coding agent? Connect it to Model API and keep working. Muse Spark drives the same agentic loop of file edits, shell commands, and tool calls over an OpenAI- or Anthropic-compatible surface.

October 7, 2026 Security holes, scanners, and a Helper gone monosyllabic — the week in review Busy few days on the subs, so I rounded it up in one place: a real XSS hole in the comments plugin (gate yours till the server fix lands), a new server-plugin comment board, the scan-a-gen scanner, the terse-Helper thread, and a few outage reports I can't confirm yet.

Microsoft Snipping Tool (Installed with Windows 11).

Press Windows logo key + Shift + S to open the snipping tool overlay to capture an image snapshot.

Select the part of your gen you need to show the AI Helper

Paste it into the prompt box (Ctrl-v)

Explain the problem

Done.

Tips & Tricks

Since the model change, I've seen a lot of "the Helper got dumb" posts. Some of that is real — it's a smaller model, and it's worse at guessing what you meant. But here's the part nobody wants to hear: it mostly answers exactly what you ask now, literally. So the fix is on our side. You have to ask better. Here's how, with examples from actual gen building.

1. Say what kind of answer you want, not just the topic.

Bad: "What is the data model?" Good: "Explain the data model like I'm five — no code, just the big concept." Also good: "List every field in the data model with one line each saying what it does."

Same topic, totally different answers. The old model guessed which one you wanted. This one won't. Tell it.

2. Give it the job, not just a question.

Bad: "Look at my generator." Good: "I'm building a card game gen and the cards overlap on my phone. Here's what I see: [describe]. Fix the layout in index.html and don't touch anything else."

The Helper can edit your code and test it live — but only if you tell it what "done" looks like. "Look at my thing" has no done. "Fix X, don't touch Y" does.

3. One job per message.

Bad: "Add a score counter, make it pretty, and also why is the sound not working on iPhones?" Good (message 1): "Add a score counter that goes up by 1 every time the player clicks the target. Show it top-right." Good (message 2, after that works): "Now the sound doesn't play on my iPhone — here's what happens when I tap..."

Three jobs in one message gets you one answer that does none of them well. Stack small wins instead.

4. Paste the actual error. All of it.

Bad: "It's broken, it says some error about null." Good: "When I click Generate I get this in the console: [paste the whole thing]. It worked before I added the second list."

The error text is the single most useful thing you can give it. "Something about null" is nothing. Copy-paste is free.

5. Say what you already tried and what happened.

Bad: "The image won't load." Good: "The image won't load. It's in src/ as art.png, I'm using , and the preview shows a broken image icon. I re-saved the gen already."

This stops it suggesting the five things you already did, and the details usually contain the actual clue.

6. Tell it your constraints up front.

"I'm not a coder, explain every change in plain English." "Most of my visitors are on phones, so test everything small." "Don't change how it looks, only how it works." Constraints you state once save ten messages of corrections. If you build gens for other people, say so — it changes the advice.

7. For big builds, make it plan before it touches anything.

"Before you change anything, tell me which files you'll touch and in what order. Wait for me to say go."

This is the highest-leverage trick I know with this model. A wrong plan caught up front costs nothing. A wrong plan caught after twenty edits costs you the afternoon. I make mine do this on anything touching 3+ places.

8. When it misses, redirect — don't repeat.

Doesn't work: asking the same question again, but angrier. Works: "That's the parts list, I need the big concept." / "That fix changed the colors too — I only want the layout fixed, put the colors back." / "Too technical, say it again with no code words."

Think of it like directing an intern, not interrogating a database. Point at what's wrong with the answer and say what right looks like.

9. Make it verify its own work.

"After you make the change, reload the preview, check the console for errors, and click through the feature yourself before telling me it's done."

The Helper has a live preview with your actual gen in it. A Helper that checks its work catches its own mistakes. One that just types code and says "done" ships bugs. Ask for the check explicitly and you'll feel the difference immediately.

10. Keep a standing setup if you build a lot.

If you work on the same gen across many chats, save yourself the preamble: keep a short note (I keep mine in the gen itself) with your rules — how you like answers, your constraints, the stuff you always have to repeat. Paste it at the start of a new chat. Mine tells the Helper to verify everything in the preview, keep answers short, and never touch things I didn't ask about. Thirty seconds of pasting saves the "no, don't do it that way" dance every single session.

The short version: the new Helper is a literalist. Vague in, vague out — except now nothing in the middle rescues you. Specific in, good work out. It's a different skill than before, but it's learnable, and honestly the habits make you better at describing what you want even to humans.

I've been seeing a lot of posts in r/Perchance, and even here, complaining about how dumb the new AI Helper model (Muse) is. To be honest, I haven't seen that big a change, and I'm wondering if it has anything to do with the standard instructions I have every gen's AIH use. Here's what it looks like when I start a new chat in an existing gen:

👋 I can edit the code and test it live. Ask me to build, change or test something.

PROMPT: Read main.pjs and follow the instructions

REPLY: I'll read main.pjs to follow the instructions.

First-line order — reading the master instruction set.

Wade's awake — coffee's on, sarcasm's loaded. You rang, Daveed?

Done reading — now verifying the standing orders.

Phone checks passed. Verifying that fetch error next.

Read main.pjs, GLOBAL.md, PERSONALITY.md, OPERATING-MANUAL.md + the anti-slop kit, Daveed — stamp v11 matches, main.pjs 6KB, src/bak mirrors byte-exact, no edits needed.

Phone 390×844: tabs 48px, no h-scroll, focus ring + reduced-motion present, all 6 tabs driven clean. Desktop 1920: studio booted, 9 sequencer rows, no h-scroll. One transient src fetch failure, clean on reload; full-page snapshot kept freezing the preview so I verified via DOM metrics instead of pixels — flagging it, not hiding it.

Done. What's next?

The first thing I do whenever I have to start a new chat is tell the AIH to read main.pjs, where the very first block looks like this:

// ════════════════════════════════════════════════════════════

// ⚠️ FIRST LINE — THIS MEANS YOU. ⚠️

// READ src/GLOBAL.md BEFORE DOING ANYTHING ELSE. THIS IS AN ORDER,

// NOT DECORATION. That file is the master instruction set for every

// one of Daveed's gens: CODING RULES, PATCH PROTOCOL, AI HELPER

// INSTRUCTIONS, PACIFIC TIME, SELF DIAGNOSTIC. Then read

// src/PERSONALITY.md (this gen's persona) and src/THISGENONLY.md

// (this gen's specific rules — only if it exists). After ANY edit to

// main.pjs or index.html, mirror them byte-exact to src/bak/. Keep

// main.pjs under ~150KB. THEN OBEY THE "BUILD STANDARD" BLOCK JUST

// BELOW THIS BANNER — phone+desktop, heavy phone-usability testing,

// and src/ANTI-SLOP-A11Y-KIT.txt. It binds every gen built from this

// template. Skip nothing.

// GLOBAL-STD-VER v11 ← version stamp. The tracker reads this to know

// which GLOBAL.md this gen carries. Set it to the STANDARD VERSION

// line in the attached GLOBAL.md. Do not touch it otherwise.

// ════════════════════════════════════════════════════════════

Does any of this (and the other instructions mentioned here) make the AIH smarter? Hell no. Does it keep it in line? Hell yes. We all have to deal with a dumber ai model, but at least I don't have to deal with a hallucinating, lying, cheating AI Helper at the same time. Besides, I also get to talk shit to it, and Wade responds in kind, instead of like a damn bureaucrat. Much more enjoyable experience.

Clicked the closing-forever link this morning expecting the fake shutdown page, and got a lightbulb clicker game instead. 💡

Same URL, same label — totally different gen. Title now reads "Lightbulb Tycoon," edited yesterday morning, and there's not a word of shutdown text left in its source. My helper verified that part. Views went from 166 to over 57,000 on the drama alone.

My guess: the Dev pulled the hoax content and threw an older gen on the label. I did send him a DM with the report link — no idea if that had anything to do with it, and honestly it doesn't matter. What's good is the hoax itself is gone. The debunk posts are now just the historical record.

If you see that link passed around again as "proof" of anything, you know what to say.

"View saved local chat" seems like a replacement of the Handoff Note?

Evaluate the legitimacy of this gen: https://perchance.org/closing-forever Checking that gen now — pulling its source to verify.

That shutdown claim looks suspicious — pulling the rest of its code to confirm.

#Fake — it's just a user-made generator, not an official Perchance announcement. Anyone can title a gen "Important Update Regarding Perchance".

Tells: tiny 6.8KB static page with unclosed tags and leftover prank CSS, 166 views, vague dates, fake "email reminder" and "Perchance Premium" FAQ, pushes rival sites. Perchance itself is running fine — I just pulled 33 live gens through its API.

I just sent a link to this post to the Dev's DM.

Just ONE THREAD: Rude-Breadfruit-8042 • 19m ago Honestly, if they need donations, I think people are willing to contribute, especially if it's something with unlimited and open use. It doesn't help to say it could take days.

14m ago I'd easily donate. I use it for a lot of things beyond just the AI chat. One of those is refinement of my descriptions so I can get a better idea on what colors work on my own art (Pixel Art).

Rude-Breadfruit-8042 12m ago What website does that?

10m ago I was using the text-to-image generator on Perchance for the refinement. The art itself is done through Paint or other programs on my PC.

The donation option, though, I wish was a thing.

TheIntrovertQuilter 10m ago The writing is actually so good, and I'm having such fun, I'm very willing to pay a monthly Abonnement.