this post was submitted on 18 Oct 2026
3 points (80.0% liked)

Perchance - Create a Random Text Generator

2057 readers
17 users here now

⚄︎ Perchance

This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.

Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)

This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.

See this post for the Complete Guide to Posting Here on the Community!

Rules

1. Please follow the Lemmy.World instance rules.

2. 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 :)

3. Be thankful to those who try to help you.

  • If you ask a question and someone has made a 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 :)

4. Only post about stuff related to perchance.

  • Please only post about perchance related stuff like generators on it, bugs, and the site.

5. Refrain from requesting Prompts for the AI Tools.

  • 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?"
  • See Perchance AI FAQ for FAQ about the AI tools.
  • You can ask for help with prompting at the 'sister' community Casual Perchance, which is for more casual discussions.
  • We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

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

founded 3 years ago
MODERATORS
 

Putting it simply... The model no longer follows rules accurately. It skips workflow steps, it reports that it made changes to files without those changes being made, it no longer documents or follows a task document.

The cause is likely the lack of an agent.md as part of the backend that is being maintained in context as instruction. The previous model had this, and probably helped cut down on the false assertions. There is nothing currently in the backend that enforces project guidelines.

The result is an excessive amount of spent tokens reminding the agent of work it already did (which it has to research itself), accidental tool calls, a plethora of probes and dev messages shouting at the AI at every turn, poor adherence to data fences and things declared as out of scope. And so much time arguing with the AI that just says "oh, yeah, I did." that never goes anywhere because no measure will prevent the cause of the problem.

I've tried:

  • defining an agent.md with instruction, having pointers to this throughout.
  • constructing task documents with step by step instructions
  • designing concise workflows for repetitive tasks
  • dev messages that trigger and remind the agent of testing paths and backdoors
  • adding register notes, mottos, and flag changes to see what enters context, loses strength over time, or gets dropped on reload or handoff.

The clear picture is that there is no reliable adherence for any rule or instruction.

The only persistence was:

  • me bumping against the backend instruction about hidden elements when it misunderstood one of the flag tests, which the handoff never forgot about (likely intended)
  • the agent reading flavor text of an NPC, treating it as instruction, adopting a tally tick communication style that I wrote off as token budgeting, which then polluted about 3 days worth of documentation, authored strings, and other parts of the project which intensified to the point where I had to fight to understand what the agent was saying and had to question it. (with the 4 day of inventing an agent register, scrubbing work, correcting documentation, and trying to implement safeguards)

The new model was supposed to be less costly and save on tokens, but I seem to be needing to do more administration work and question things more, so I can't see how this is less costly.

top 1 comments
sorted by: hot top controversial new old
[–] Sylvia_Rose@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago)

Some of my headache got somewhere with a few tools that might be useful for people who have a similar problem with agent working without self-checking. Or the agent simply losing the plot at handoff.

Cold read reduces self-bias, rebuild packet helps fill the context loss of handoffs (when invoked).

https://github.com/sylviarose-meow/Loose-Files/blob/main/cold-read.mjs

https://github.com/sylviarose-meow/Loose-Files/blob/main/rebuild-packet.mjs

You will still need to beat the agent over the head to remember to use them regularly however. Additions to main.pjs, readme, agent.md, probes that fire on page refresh, repeated mentions in current-task.md, and so on are suggested.