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.

I didn't expect it to take this long for me to get the new text model under control. It's much more intelligent in general, but the repetition and random fixations can get surprisingly bad.

Sorry about that. This is just a heads up that I'm still working on it, and it'll likely remain a bumpy ride for the next couple of months.

Thanks to those who have complained here and on reddit, especially the posts that give concrete examples of issues, and attempted workarounds, etc.

Please do keep posting any issues/discoveries, ideally with share links to give me specific examples that I can test.

Other news:

• I'm still working on the next image gen update, and am hoping it will improve fine details, text rendering, and overall image quality. It should also be about 2x faster. If all goes well (which, from experience, it won't) I should be able to get that done in the next month or so.

• For a long time I've been very close to shipping a multiplayer plugin and database plugin. I've actually made multiple 'ready to ship' draft plugins of both, but have been disatisfied with the design and ended up not publishing each time. Using these plugins won't trigger ads on the generator, so I need to be really careful about the overall architecture to ensure the the servers for them are dirt-cheap to run. I also want to make them fun/simple to use of course. Once I get text and images stable, I'm going to focus on these two plugins and finally get them done.

Welcome to the Perchance Community!

Perchance.org is a platform for sharing and creating random text generators.

This Lemmy community is for:

• Asking for help with problems, issues, or requests about generators in Perchance
• Sharing and showcasing your created generators, templates, plugins, or pages in Perchance
• Starting friendly discussions about topics related to Perchance

If it is your first time in using Lemmy, please check out this message from Lemmy.World and the Support Page from Lemmy.World to get started on using Lemmy.

Posting from Mastodon

Feel free to checkout this post to know how to post in this Lemmy Community through Mastodon.

Other Community Links

• Subreddit
• Casual Perchance <- for more casual posts, AI Discussions (Prompting and Images), etc.
• Discord
• Mastodon #Perchance (mastodon.social)
• Fandom Wiki

Rules

Here are some rules in this community:

• Please follow the lemmy.world instance rules.
  • The full rules are posted here: (https://legal.lemmy.world/)
  • User Rules: (https://legal.lemmy.world/fair-use/)
• Be kind and friendly.
  • Please be kind to others on this community (and also in general), and remember that for many people Perchance is their first experience with coding. We have members for whom English is not their first language, so please be take that into account too :)
• Be thankful to those who try to help you.
  • If you ask a question and someone has made an effort to help you out, please remember to be thankful! Even if they don't manage to help you solve your problem - remember that they're spending time out of their day to try to help a stranger :)
• Only post about stuff related to perchance.
  • Please only post about perchance related stuff like generators on it, bugs, and the site.
• Search through the Community Before Posting
  • Please Search through the Community Posts here (and on Reddit) before posting to see if what you will post has similar post/already been posted.

Posting

Here are some optional tags to add in your title to categorize the posts. These are merely tags, you still need to title your post effectively.

• [Bug] - if you think you find any bug in Perchance, use this tag.
• [Question] or [Help] - this is to denote that your post is a question or requesting for help
• [Suggestion] - for any suggestions in Perchance
• [Feedback] or [Appreciation] - for any feedback or appreciation to any generator or to Perchance in general.
• [{Generator Category}] - Used to share any generator with the specified category
  • Text, Image, Template, Hub, Plugin, Preprocessor, Community/RP, Game, Experiment, Useful Generator
• [Fluff] or [Non-Generator] - Non-generator posts but about Perchance
• [Tutorial] or [Guide] - for any Perchance related tutorials or guides to help others

AI Plugins Posts

Here is a FAQ for the AI tools in Perchance.

We would like to ask to refrain from posting here needing help specifically with prompting/achieving certain results with the AI plugins (text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"

There are guides, tutorials, and resources on the internet that can be applied when prompting in the AI tools in Perchance.

We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

If you need help in prompting, please post on the 'sister' forum at Casual Perchance

Getting Started with Perchance

To get started with Perchance, check out the Perchance Tutorial or the Beginner Tutorial at the Perchance Hub Learn Tab to get to know the website.

• Also, check out this video by Chaoclypse as an introduction to Perchance.

Asking for help

Feel free to ask for help but please check out these tips on searching for an answer:

• Check the following pages, to see if your question has already been answered or talked about or a plugin has been made for it. We recommend using the browser's search function (ctrl+f) and searching for similar keywords to your question/problem.
  • Perchance Tutorial
  • Perchance Advanced Tutorial
  • Perchance Examples
  • Perchance Plugins
• If you didn't find anything about your problem there, feel free to search through the posts/articles here:
  • Perchance Subreddit
  • Perchance Lemmy
  • Perchance Hub Learn Tab (WIP)
• If you can't still find anything related to your problem, feel free to post a thread here.
  • Please title your post effectively.
  • Please provide a link to your generator with your attempts of solving the problem.
  • Try to explain what you want it to do and what example output it should be doing.

Hello to all,

First off, huge thanks to the Perchance devs. I've been using the site for ∼5 months and it's honestly amazing that this is all free. Really appreciate the work.

Small suggestion though... the features are super modern (like AI Helper, backups, etc.) but the site design feels a bit old.

Especially on mobile, the top bar is super cramped, buttons are tiny...

Would be cool to see a bit more spacing, cleaner panels, a light/dark mode toggle, better mobile layout, clearer save status like "saved locally / saved to cloud"...

And most importantly the modern-looking design.

I actually like that Perchance isn't corporate and soulless, so not asking for a "full" redesign. Just a bit of modern polish would make building generators way nicer.

Thank you so much again for making Perchance, Tony Lee from South Korea.

Dev Log

Concept: A controllable spider

Description :

A basic Spider has bendy legs and synced walk. So the Spider base

1. IK legs
2. body segments
3. synced gait.
4. 8 two-segment IK legs
5. cephalothorax
6. abdomen
7. eyes/fangs,
8. alternating-tetrapod stepping that syncs diagonal pairs.

Logs

Walk works — synced lift, turns toward motion. Keeping it on-screen fully now. added some flies, basically prey to chase. WASD/arrows to walk, Q/E to turn in place, hold mouse to follow, joystick on touch. Tweak speed/leg lengths in : main.pjs:spiderConfig.

Interaction / Controls

I added some basic control.

1. manual — you drive (WASD)
2. Manual — click OR drag anywhere for the spider to follow
3. drop prey releases 2 bugs (they wander, flee with zigzag, auto-restock when cleared).
4. pounce / eat lunges toward the nearest bug — or Spacebar.
5. Meals counter tracks kills and the abdomen swells after each one.

Modes

I added some different modes :

1. hunting mode,
2. stalking,
3. curiosity.

Breeds

I added Five breeds in the top bar, each with its own body and hunting style.

1. orb — the balanced default
2. widow — black with red hourglass, slim legs, bigger grab range (venom)
3. jumper — small with huge front eyes, monster pounce distance
4. tarantula — big, hairy, slow tank with the widest grab
5. huntsman — wide stance, fastest walker

error: The browser tool stopped unexpectedly. Reload the page and try again. (error code: AC-0027) — your message is saved for retry

I want to present ai character chat hard fork i was working for last months, and its finally somewhat close to being complete. https://perchance.org/ultima-character-chat

I will try to descrube all the new additions.

Custom code: It was remade into unlimited and open custom code. You can do everything you want at all, any javascript.

Console: Old comand system and textbox was modified to the console (not visually). I wanted something similar to linux bash. You can send console comands from custum code or type into chatbox. And you can register brand new console comand from within custom code that will work nativelly with native resolution.

Extraroleinstruction: Did you ever felt need to modify characters instruction (also known as description) for a single chat? Solution was to make a copies of character. With extraroleinstruction custom code comand you can assign a variable adress or text to your characters instruction and it will be automatically appended when ai reads roleinstruction. You can assign a variable and update it via custom code on triggers or you can assign literal text. Works with multiple characters at once in single chst, each can have their separate extraroleinstruction.

State tracking: My own inbuilt mod that utilizes extraroleinstruction. It assigns each character a separate json with current state and updates it every their message.

Multi character support: Original system of ai character chat where you had single main character and others was additional and didnt have same benefits was reworked in ultima character chat. Now you can chat with single character and effect will be the same as in original, no downsides. Or you can chat with multiple characters and it will still carry on, and all effects and benefits will be applied to all characters equally.

Advanced auto reply: Auto reply is now based not just on message sending fact, but on names. Every your message that contains name of adressed charcter, will trigger reply from that character. It has to be uppercase and followed or preceded by comma. And it even learns new names. If you call specific chaeacter by specific nickname and launch manual reply enough times, system will learn that and will start autoreplying on that nickname. And of cource it works with as many characters as you have in chat simultaniously.

Image generstion: Image generation was modified. To ensure some character consistency i turned default mode into portrait and backed it up by image to text generation, to capture original image as sucessfully as possible. Alternativelly, you can still draw scenes and anything you want at all, with all 3 shapes of images supported in console comand.

Writing style feedback: Did you ever want to give feedback to ai because it didnt follow your roleplay style instructions? Now you can do it and ai will modify roleplay style itself based on your feedback. It has some thinking ability, search tools, and everything in theory it needs to correctly detect what kind of changes needed. Still mainly untested, i wouldnt expect perfect results.

Main ai thinking: Optional thinking was added to ai. Replies are slower, but hopefully it helps with consistency and non contradiction and following writing style. You can still disable it if you dont like.

New summaries and memories: Summaries and memories was completelly remade. For better or for worse. Initial testing shows some consistency, but still can be not that good. Also, now main reply ai has to wait for summaries and memories to be finished.

Additionally, importing your threads from ai character chat is not supported, because all the plumbings of thread was changed to the point where old thread data is incompatible. But importing your characters is supported. You have to start new threads.

If you interested, try it out, and if you have questions, i will answer them.

This post is going to be a long one, filled with my personal experience and comparisons because I really need to get this off my chest. And yes, I’m a newbie here. I discovered the site 2 months ago, though I only registered this account recently.

As I think other Perchance users have noticed, the AI assistant has been acting incredibly dumb lately. It constantly glitches, writes in a dry, unpolished, and overly brief way, delivering the absolute minimum. It completely lacks any 'imagination.' Unlike the previous model, it can’t brainstorm ideas based on your project anymore; it just repeats what was already written in its readme file. It’s completely incapable of coming up with anything original, or at least it struggles heavily to do so.

I really loved how the old model used to write, highlighting and noticing every little detail. Heck, I even experimented with it, and the model could synthesize sound or literally copy a song, which is already amazing by itself, or edit audio. Sure, it can't actually 'hear,' but still! All of this is from my own experience. But if you compare it to the current model... well, I’ve already described it: it's dry. It is fast, that’s a fact, but I would much rather wait longer for the sake of quality.

So, what I’m getting at is that I hope this is just a temporary workaround by the developer. The website is great, and the AI agent used to be a massive help. It brought ideas to life. It was awesome to build a game framework and then just polish the minor details. It wasn't perfect, but the quality was high.

What makes it even more frustrating is the 'thinking' feature. When I first saw it, I wondered why it was even there. But then I realized it’s a brilliant feature. Now, though, I don’t see a single trace of actual thought from this dummy.

Anyway, I’ve rambled on for too long. I hope this doesn’t last. I can see that people are furious because, let’s face it, 'how could they take away our gold and give us copper instead?' But as harsh as it sounds, we also need to stop whining. No matter how disappointed I am, the developer might be having a hard time or dealing with temporary issues, so we probably just need to wait. Everything is so messy right now.

I might be inaccurate on some points, so please take this with a grain of salt. It's just my view on the current situation.

While mostly a personal project, I decided to build tools to support and extend the 'official' ai-character-chat rather than fork it. I have seen several forks and thought achieveing many of the added features could be done by enhancing the perchance chat rather than replacing it. My Character Workshop does that and more, allowing a method of extending what the ai-character-chat does without forking.

Certainly a work in process, the tools range from a utility to trim the fat off long chats, read them offline, build personal and public character and 'world' libraries, character generator, import and upgrade tools, image tools, and a World Builder that provides AI feedback and more.

The landing page title the post grabbed is a bit confusing, it was intially forked from a character generator, but now ties together a series of generators and tools: https://perchance.org/ess-adv-char-gen

for the love of god, just revert the ai helper already!!!!!!!!!!!!!!!!!! cant even do anything with the helper. it just says Ai Hiccup over and over. cant believe people are glazing this site!!!

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.

1. 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.

1. 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.

1. 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.

1. 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.

1. 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.

1. 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.

1. 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.

1. 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.

1. 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.

Thank you dev

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.

I want to report a fairly serious issue I ran into with the <skill_content name="server-plugin"> workflow and suggest some changes that would make server failures much easier to diagnose and much safer to recover from.

My server became stuck in quarantine, and it was extremely difficult to determine what was actually causing it. Even AI helper could not reliably identify the underlying problem.

The particularly problematic part was that tests and server-code/version updates could repeatedly trigger quarantine, and each time I was effectively locked out of the server for around 60 minutes. This made debugging extremely difficult because every attempted fix could result in another quarantine period.

I think the server plugin and especially the AI-helper guidance should handle this situation differently.

Suggestions

1. Make quarantine read-only instead of completely inaccessible

When the server enters quarantine, the server should ideally become read-only rather than being completely locked out.

Writes/mutations could remain disabled until the quarantine is resolved.

This would make quarantine a safe mode rather than a complete black box.

2. Treat WebSocket close code 4429 differently from ordinary network failures

The AI-helper/server-plugin documentation should explicitly explain what 4429 means and how an agent should react to it.

It should not be treated like:

"The connection failed, reconnect normally."

A 4429 quarantine is fundamentally different from an ordinary temporary network failure.

If an AI agent receives 4429, it should stop repeatedly modifying/testing/redeploying the server blindly.

Instead, it should enter a diagnostic workflow:

1. Detect 4429.

2. Stop aggressive reconnect/retry behavior.

3. Determine whether the server is in quarantine.

4. Read available diagnostic information.

5. Inspect storage/snapshot state if read access is available.

6. Only after the cause is understood should the agent propose a write, migration, repair, or server-code change.

7. Identify whether the problem is:

   • corrupted data,
   • malformed record,
   • sequence mismatch,
   • invalid snapshot,
   • migration problem,
   • server-code problem,
   • storage-size problem,
   • or an actual temporary service/network condition.

This would prevent an AI helper from getting into a loop like:

change server → deploy → 4429 → wait → test → change server → deploy → 4429 → wait again

That loop is extremely expensive when each quarantine can lock the developer out for approximately an hour.

3. The AI-helper skill should have an explicit 4429 recovery procedure

I think <skill_content name="server-plugin"> should contain a dedicated section such as:

### 4429 Quarantine Recovery

Do NOT treat 4429 as an ordinary network failure.

When 4429 occurs:

* stop repeated reconnect attempts;
* do not repeatedly deploy modified server code just to test whether the problem disappeared;
* do not perform destructive migrations;
* use read-only diagnostics first;
* inspect storage metadata and snapshot validation results;
* identify the exact failure before making changes;
* preserve/export the affected storage state where possible;
* only perform repair/migration after the corruption/failure has been identified;
* respect the server-provided quarantine/retry interval.

If diagnostic read access is available while quarantined, use it before attempting another deployment or mutation.

That would give an AI coding agent a much safer operating procedure.

4. Distinguish three different situations

The skill documentation should clearly distinguish:

Normal network failure

connection lost
→ reconnect with normal backoff

Temporary server/service problem

temporary server unavailable / overload
→ respect retry information
→ reconnect later

4429 quarantine

server entered quarantine
→ STOP normal retry/debug loop
→ enter diagnostic/read-only mode
→ inspect server state
→ determine cause
→ repair only after diagnosis

Those should not all be handled by the same generic reconnect logic.

5. Preserve diagnostic access even when writes are disabled

I understand why the server might need to prevent writes during quarantine. What caused the biggest problem was losing the ability to inspect what was actually happening.

A good compromise would be:

Quarantine = no mutations, but diagnostic reads remain available.

That would protect the server from further corruption while still allowing the developer and AI-helper to investigate it.

Main request

I would strongly recommend improving <skill_content name="server-plugin"> so that quarantine is treated as a diagnostic/recovery state rather than a complete lockout, and adding a dedicated, explicit 4429 procedure for AI-helper agents.

The biggest practical problem I experienced was not simply that corruption/quarantine happened. It was that once it happened, diagnosing the cause became extremely difficult, and every attempted test or version change could trigger another long quarantine cycle.

A read-only quarantine mode plus detailed 4429 documentation for AI agents would make these failures substantially easier and safer to troubleshoot without repeatedly locking developers out for long periods.

https://perchance.org/closing-forever

impersonating official and spreading fake new.

Saves fail for me now even on empty new generators, on phone and computer. This started around 4pm of Sep 28. I was on Cloudflare WARP at the time, but even with it turned off and my internet normal, the same error message kept popping up and still does. So, I don't know if WARP scrambled my shit up or not. I was wondering if anyone could fix this because I don't know if it will go back to normal on its own.

No rhyme or reason, just constant intermittent failure. No fix. Disable everything? Still happens. Try another (clean) browser? No change. Not using a VPN? Doesn't matter. Fixed by USING a VPN?? WTF. Is it a secret back channel "you've used this too much" block? FUCKING JUST SAY SO. Maybe provide a counter. Fuck... either fix this or provide ANY useful information other than "just try again later."

So perhaps I could be fooling myself, or maybe this is a bad idea...

But why not allow us to use local models as the helper? If we just added a pipeline to a local model as the brain of the helper, and kept all the resources that the old helper uses as a reference... That might alleviate a lot of stress and some cost off the function of the AI itself, which could save some money would it not?

I'm not super savvy on all the technical background required but as a concept I think this might at least somewhat help save on the COST side of things.

Thoughts?