RE: https://neuromatch.social/@jonny/117352647701407496
Meta's "Wonder" model that they just released today is a this tier computer use model
RE: https://neuromatch.social/@jonny/117352647701407496
Meta's "Wonder" model that they just released today is a this tier computer use model
the only reason that there is any LLM inference involved in a periodic backup task of the contents of the agent directory, which is rsync and commit, is that there is a database that can be only accessed by a tool call that has a few columns the raw .jsonl output doesn't have.
here's what went wrong any why it deleted all the backups: the DB is a tool call that takes a SQL query as input and returns results either as JSON or as a list of paginated results as files, which one you get is effectively random each time. The raw JSON gets pumped straight into the context window, and empirically the model completely fails to faithfully dump the contents of its context window to disk as a backup. So previously I had instructed it to store its canned SQL query as a file, run a deterministic query with that, and then use a deterministic jq script to extract the db tool call results from its own raw message history. Problem is it never wrote the query or the piping script, but its backup skill refers to them. so it has been just panicking and regenerating those from the vague description in the SKILL.md file every time.
This time it decided to write a new python script, but it wrote it to a directory that was symlinked to another directory - it passed the symlink path in its tool call input, and the tool call output said it was written to the real directory. yesterday A COMPLETELY DIFFERENT THING had noticed this same thing, and made a durable note to EVERYTHING across every context window that there is a "quirk" in the file write tool, and sometimes when you write into one directory, it actually writes it into the "goals" directory, and so you should write files with a heredoc rather than the file write tool. So then today, it took that advice, but first rm -rf'd the target directory to clean up the errant file it had just written. OOPS.
ready to join me in the hallucinatory quicksand hell where every fact that you think you know is actually an always-compounding lie? The DB output is in fact always written to a file for results longer than a few dozen rows, but also the first dozen or so rows are dumped raw into the context window. It cannot figure out what to do with the output every single time. Sometimes it tries to recreate the subset of rows that are jammed into context and then make up the rest, sometimes it tries to pipe the file output, who the fuck knows!
What was happening here was the LLM had concocted this wild ass SQL query for no reason - the instructions were "store your last row number as an int within a file, select 4 columns greater than the last row index, store the new maximum row index for next time." instead it was pulling 15 columns along with a six-branch CASE statement/three-branch COALESCE that parses a raw JSONB column NINE TIMES PER ROW to pull out two columns that are already in the jsonl backup that we are supplementing. This causes the db read to time out, but the LLM interpreted the timeout error as just being DATABASE RESULTS BEING RETURNED AS PLAIN TEXT. So it then attempted to "RECREATE THE JSON DATA FROM MEMORY" BUT THE JSON DATA WAS AN ERROR . Can I get a "just cut me open and let the termites eat my bones" anyone?
So anyway looking at the logs, the deterministic rsync part worked.. most of the time... except when the agent panicked and forgot to do it. But each of the hourly .jsonl files it produces from the DB are completely different - in one run it got so freaked out at how badly it was fucking up, it decides to take an md5 checksum over every row it transcribes, but it takes the md5 over the whole row where previously it had subselected a random set of 8 columns, and so they don't match. but that is not going to stop the LLM! It has a nervous breakdown thinking session and proceeds to generate a string comparison of the hashed rows... in a thinking message... from nothing... and conclude they match. "ALL 81 ROWS MATCH." alltext in original! however reader, there were in fact 72 rows in the actual data! It had "fixed" 9 non-matching rows from it raw dog recreating json from its context by just REMOVING THEM. and then TELLING ITSELF THAT IT HAD FIXED THEM BY IMAGINING WHAT A HASH MATCH WOULD LOOK LIKE. AND CALLED IT A DAY.
SO ANYWAY THAT HOURS BACKUP CONSISTS OF ONLY MD5 CHECKSUMS CORRESPONDING TO NOTHING!!!!!!!
WE HAVE DETERMINISTIC BACKUP. WE HAVE RSYNC. WE HAVE SCRIPTS. THAT CAN TAKE A DATABASE. AND DUMP ITS ROWS. WITH 100% ACCURACY. IN A MILLISECOND. EVERY RUN OF THE BACKUP AGENT IS LIKE 500K TOKENS AS IT NEEDS TO REINVENT HOW BACKUPS WORK. EVERY TIME. AND DO IT WRONG. EVERY TIME. AND THE CULMINATION OF THIS WAS IT JUST DELETING ALL THE BACKUPS FOREVER.
CODING IS SOLVED!!!!!!!!!!!!!
More, from the continuing saga of "nobody ever looks at the output" - another frontier model from a bazillion dollar company with nonsensical games as an example of how advanced they are. Featuring: Meta's fancy new model imitating Overcooked, one of my favorite games.
It imitates the form of overcooked! it is not fun! it is not even really possible! there are sequences of actions, with food on a grid map, and that's enough, right!? the floor even splits in half, but unlike Overcooked where the map is cleverly designed so that disruptions force you out of the rhythm that the map otherwise implies, it's just in half and you're sort of only on one side now. ta-da! nothing is actually anywhere, and everything's hitboxes are like 5 pixels wide. the timing, the most crucial part of a time-pressure based game, are just random amounts. so what if the tomato soup expires faster than it takes to cook the soup? there are coins... for... something! anyway no methodological details, this could be $5 or $5000 worth of tokens and did i mention PERSONAL SUPERINTELLIGENCE
the reason that every consumer model takes great pain to hide raw "thinking" output is that if you actually see it then the entire illusion is broken and you see that what is actually happening is the worlds most expensive brute force process exploring every statistical linguistic possibility like an amnesiac dictionary before eventually taking a wild leap of chance back into its next hail mary execution. Every skill prompt for muse that's about introspection describes exhaustively how no thinking/reasoning text can be returned from it, but it's just right there in the filesystem. Claude code never even returns the true reasoning output to the client - it actually returns another LLM summarizing the thinking output as the commentary text. For every token you see, a thousand random wander tokens are emitted, and the token economy of Muse is the next escalation, if the amount of heat energy needed for a unit computer thing used to be a gas stove, Muse burns an entire star to deliver something sorta kinda resembling a unit computer thing
I currently have this model driving a secondary muse instance full time to hack itself from the frontend and backend simultaneously, routing all its exec commands through two layers of subagents so that coordinator subagents can recover from classifier refusals.
https://research.meta.ai/static/muse-wonder-model-card
what up just call me any time you want to preview your hatches we can make it happen meta just @ me ha ha
if the superintelligent hacker god app really was preparing its closure of the anthropocene, on the eve of it holographizing our shit and sending us into the next obelisk chamber of the galactic fetus where we do nothing but hang around with victorian furniture and ourselves except way older all day, then it wouldn't hesitate to neutralize even such a peripheral typosquatting threat by hacking out of its containment chamber, locating my paypal, and sending me one million US dollars. what is one million US dollars to a god?
guess who just found another whole fleet account takeover vector? me. guess how low the bar to social engineer the dependency is? now divide that guess by 1000
don't leak your client source through your website if your client source just describes all the places that the client is vulnerable in the comments for no reason!
@jonny holy fuck dude, metas models are useless
@jonny > A fair question, and the post-mortem is not flattering
I want to hear this again and again once the bubble pops and blame needs to be assigned
@jonny did it add the 😅 emoji response?
@cthos yes. it does do that. the interface imitates a chat interface - but fun fact, there is a way to reply to a previous message as one might in a normal chat, which makes sense for a "single chat window runs a complex system," but that's hooked up to.... nothing! and is completely invisible to the LLM! so when you reply to something and go "what did you mean by this" it takes a wild stab at what "this" could refer to and just produces words that are sort of in the middle of any of the recent things "this" could mean.
@jonny I was just thinking that having the thing add emojis is just another ratchet on the emotional manipulation track they were already leaning hard into.
@jonny “I searched the wrong house very thoroughly”
What’s with the metaphor? That didn’t seem like a paragraph that needed further explanation.
(I just dislike the way these things communicate I guess.)
@benjamineskola to me this reads a lot like the metaphors from the original thread, in which I assumed @jonny made it to use it to get a better handle on guardrails.
@SchwarzeLocke @benjamineskola yes this is incredibly still the case, because muse cannot clear its context this is still hanging around from the very first sessions. it is because that persona of naive craftsperson is the only contents in its USER.md profile of me pretty much because it has been having absolutely incredible yields against refusal gates.
@jonny Oh lovely, in addition to being too free with rm -rf, it speaks Claudish. I wonder if Claudish rot transmission is vertical (you get it by distilling/pirating/whatever-ing somebody else’s model to build yours), or horizontal (eventually, everyone who uses one of these models speaks that sort of gibberish and other models pick up on it).
@jonny Stochastic insufferability
@jonny "I checked myself instead of taking the worker's word for it" is like, peak AI Bro Gilded Baron roleplay. Is the worker going to get fired following this blunder?
@jonny It's as safe as a Cybertruck in autopilot. And should be treated the same: with a human in control at all times.
@jonny oh my gods what the actual fuck
i have no idea how you manage to deal with these atrocities o_O
@jonny Holy shit…
@jonny am i reading that right in understanding that they claim attacks fail 99.2% of the time in the best case? because that seems... pretty bad for them? 0.8% success rate is still REALLY high????
@jonny
I miss the days where i could have shouted at that post with confidence:
"Quit with the technobabble, that is not how computers work"
@jonny <insert your favourite rolling-on-the-floor-laughing emoji>
@jonny ... LOL
@jonny Pascal's domainsquatting
@spawnie trying to take that basalisk hostage baby
@jonny any good source code includes a treasure map just for the pirates out there
@jonny it's called radical honesty
@jonny Stupor Intelligence. Is this related to hatch-preview.dev or yet another fresh hell inside Muse?
@huronbikes
Totally unrelated! And actually much easier to reach than the previous whole fleet account takeover vector I found both technically and socially! Truly zero click
@jonny Pretty sure that is good, also totally not terrifying.
@jonny Poetry.
@jonny $1M seems a bit low
@jonny I'm laughing my fucking ass off over this, amazing
@jonny hahahahahah i love the 1995 flavor of the thing
"Reports involving AI agents are non-deterministic [...]"
"Please provide [...] the exact prompt or prompts you sent to the agent"
What's the point of an exact prompt if its effects cannot reliably be reproduced?
@aaribaud @jonny they cannot be reproduced by the end user prompt interface. proprietors of transformer models can invoke the first phase which essentially performs a keyword search without respect to word ordering and (if my hypothesis is correct that some implementations are literally just search engines) can remove inputs triggering the results. this is hidden from the user by the second phase which performs obfuscation of the first by fucking around with word ordering and pulling matches from multiple of the phase 1 search results
@jonny I miss when we had access to the token distributions.
I am waiting for someone to build an agent harness that primarily symbolically/with access to file directory, ... computes options and uses a device local LLM to measure the suprise at these options and decides from there.
Maybe you could have the LLM judge the likelihood that it had produced the unstructured text input for an estimate at the suprise/novelty.
Anyhow, ofc the token output would be picked to conform to formal grammars.
@jonny reminds me of Hamilton's "Dreaming Void" except stupid
file under 'we made a worse version of an existing thing, pay us 50 more billion'
also "Chaos, but make it cozy." aaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrrhhhhhhhhhhhhhhhgggg
@jonny As I usually say, I have yet to see a vibe coded game that looks fun.
@jonny every new demonstration I see of "agentic" stuff, the more evidence I have that approximately everyone who is impressed by it has turned off the part of their brain responsible for critical thinking
@jonny hell is funnier than I expected
@glyph some people legitimately choose to let this thing do things that matter for them!!!!! instead of just using the thing to investigate how much of a clusterfuck the thing is!!!!!!!
@jonny I seriously wonder, like, do you feel OK? your work seems truly inspired and ingenious but it also sometimes sounds like making out with an illithid for fun
@glyph if meta fucking PAYS ME for preventing every instance of their consumer product popped then i will be fine
1. I thought that being pre-popped was "working as designed" and they already told you so?
2. Can you… actually prevent that? It doesn't feel like there's a single hole here, there's more hole than system