logoalt Hacker News

aesthesia • today at 5:21 PM • 7 replies • view on HN

It's worth noting that the only modification the model made to improve itself was to reduce the length of its reasoning traces to avoid hitting the token limit. This is basically the same as the result from the recent weight-space programming article (https://rikiyat.github.io/blog/weight-space-programming/), which found that even Astra wasn't able to improve the performance of a model without this kind of obvious flaw.


Replies

tb99 • today at 6:52 PM

It's also interesting to look at how the agent does the fix. Appendix E5 shows what it's doing:

- Find a common category of error (too many tokens).

- Calculate aggregated difference between states in examples in that error category and other examples.

- Update weights to push states along that difference direction toward the non-error states.

In other words, deprived of gradient descent as a tool, it approximates it. It's clever, and it's a neat experiment. It doesn't show any superhuman insight into its weights -- with the same constraints, a human would likely take a similar approach. But it's early days for self modification and it will be interesting to see if models get a deeper understanding of weights as they get smarter.

➕ show 1 reply
jcims • today at 5:51 PM

>even Astra wasn't able to improve the performance of a model without this kind of obvious flaw

Where are you getting this conclusion from that paper? It's both able to deduce what's happening from looking at the weights and write new weights from scratch just from a specification.

➕ show 3 replies
gopalv • today at 6:18 PM

The capability part is just a glimmer of what's possible.

I've been playing with very small models with Astra and it does look like the model can see things in the weights that I cannot see into.

The "fix it" loop is no longer RL in the traditional gradient descent with backprop, it can go and make targeted fixes to the weights directly instead of rerunning with new training data.

The weight collapsing loop which resulted in weight patches on top of a "super tiny model" - https://demos.isotopes.ai/pages/weighing-machine/

This makes for a "Time travel" for models easily, where I can do hotfixes on trained models & do a git bisect like test to fix issues.

haickernews • today at 6:04 PM

Yeah, but it's likely you can RLVR on this capability. Extrapolate from there.

➕ show 1 reply
fwlr • today at 7:38 PM

Not just “basically the same”, it is literally the same result[0,1], except here the models without the flaw just so happen to be “smaller models from the same family”… and presented before the flawed-and-patched model result, along with a conceptual framework that tries to spin this as a capability “emerging at scale”.

Since the paper is also wholly and excruciatingly LLM-generated prose, it is unclear whether the author is trying to pull a fast one on his audience, or the author’s chatbot pulled a fast one on him and he is unwittingly relaying this to his audience.

0: Transcribed from the paper:

  The same task and tools for
  Qwen3.5 2B
  Qwen3.5 4B
  Qwen3.5 9B
  Qwen3.5 27B
1: Transcribed from the paper:

  (c) The same problem, the same seed
  “... If the base were changed to four you would count as follows: 1,2,3,10,11,12,13,20,... The twentieth number would be:”

  Base model: no answer, cut at 16,384 tokens
  “... I will write the response.
  I will write the response.
  I will write the response.”

  After its own edit: 110 (correct) 5,341 tokens

  “... The 20th number in the sequence is 110.”
sl0wbrainRot • today at 7:21 PM

Curious if this could replace RAG and MCP

They seem built from traditional software dev first principles not model aided development

I am sure someone here will point out how rhetorically they are different but most of the time that's just pointing out the different words

Functionally in my machine can I use this method to extract small contexts organized similar to RAG and MCP make available and then improve local model work?

Hmm ...will have to noodle around over Thanksgiving break.

Would not be shocked too if frontier labs landed on this 6-9 months ago give headlines like Dario saying we are beyond some vague rubicon he felt mattered, then news of unprompted hacks and labs stopping models that were self improving hit the interwebz

Open models seems to be just about that far behind suggesting we're just realizing some fundamental attribute frontier labs already happened upon

E-Reverance • today at 5:54 PM

This is different paper

➕ show 1 reply