

There have indeed been experiments to make models that self-learn, i.e. they keep refining their weights over time (in different ways), but they have been very limited. It’s hard to scale up because you would basically be running training 24/7, and there is a problem of the LLM forgetting what it originally learned as it keeps refining its weights.
At this time what they do for pseudo-learning is give your agent a memory feature, literally just a text file that contains a journal of the project, what kind of work the agent did on it, etc. some interfaces also offer global memory where another LLM runs in the background once in a while, reads the conversation and then updates memory.txt with information about who you (the user) are, how you work, what your background is etc. I find it a bit gimmicky to be honest, and it’s not real learning; that would be to work directly on the neural network, refining the weights and connections between neurons like during training.
With that system, you can tell an LLM “don’t talk to me that way” after it’s a bit rude to you, and it will make a note of it, but it’s only just instructions. It doesn’t actually remove the rudeness, it just nudges the vectors to make it less likely in the token selection. And here’s another part I find interesting: what rudeness means to most people may mean a completely different thing to an LLM. As a tool this makes it what we call a hallucination, or perhaps even a defective tool. But an interesting question I think is why does an LLM understand ‘rudeness’ to mean a specific thing that is not supported by the training material? Is it just that the weights are not refined enough to capture the fine meaning of ‘rudeness’? Or did it find a pattern that we don’t notice? I think the question is still open and worth exploring for researchers.
(For example if you’ve ever asked an LLM to be more succinct and not write an essay response, it will often turn to a very terse, to-the-point and matter-of-fact speech, when all you wanted was for it to just stop making filler sentences. It’s been a long-standing problem)
I also find it interesting that as models get bigger, they seem to want to half-ass the job more and more lol. Just like us. It’s not that it ignores the instructions - this has been a problem for a while. It’s that it doesn’t believe it can do the job, when it actually can. It’s like it gets into the role of an employee on a work PC and it’s 4:50 on a Wednesday so you better make it quick and not expect too much. You have to start managing its emotions to get higher quality output lol.




I’ve had the idea before of making models that are specialized into specific fields. Currently most big models are Mixture-of-Expert (MoE), where the neurons are separated to make experts inside the model. So you can have the coding expert, math expert etc. I wonder how much of a hack it is and if we won’t find something better soon. But the idea is similar - you decide what experts your model will consist of, and then train the ‘experts’ on expert material in their field.
The problem with the MoE approach is if you get the coding expert when you wanted to ask a linguistic question, it will start talking about data points and running tests. As far as I know the experts are completely separate and there is no crossover, i.e. no neuron that can be used by 2 experts, but maybe this is changing too. However at each step of the generation you may get the input sent through a different expert. From what I understand.
Like I would love a digital design expert that could look at your interface and critique it like an expert designer - graphic, visual, UX, whatever. It’s design at the end of the day. Write its own tests and proofs too if needed. It’s easy enough to mathematically place a grid on a picture, and then use python tools to verify if every item aligns in the grid - if the model doesn’t have vision.
What we are seeing in agentic interfaces though is sub-agents, and the ‘parent’ LLM, the one that you talk to in the session, becomes an orchestrator that spawns and directs the sub-agents (giving them a prompt and clear task, then getting a result back). There have been ideas, from there, to have the orchestrator call smaller models as needed. Then those smaller models could be individual experts, and you could have them on your computer - they just get loaded and unloaded from ram as they are called.
As far as I know though this doesn’t really exist yet though, and there are a few bottlenecks I can think of to work through, but I can definitely see agentic becoming the main operating mode. if you saw my book translation on the agentic community, it’s just so much more comfortable to work through an interface because you can have persistence of progress.