| ▲ | general_reveal 7 hours ago | |||||||||||||||||||||||||||||||
Isn’t this just a form of the bitter lesson? Our attempts to make engineered context and agents will simply be made obsolete with bigger and better models. Those transcripts are probably extremely useful for lesser capable models, and near unnecessary for frontier ones, maybe? | ||||||||||||||||||||||||||||||||
| ▲ | andai 6 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||
Yeah, the question is whether this applies to all of context management. I've been using a custom harness based on https://minimal-agent.com/ (itself based on swe-mini-agent), which is like 50 lines for the core logic. Bash is all you need. For small tasks, I find it's about 8x faster (and uses 8x fewer tokens) than the standard harness for each model. For bigger tasks I haven't tested it much. It seems to work too but I think they're a bit less focused and productive in that case. It could be that those big harnesses' 20k token system prompts are doing something important with regard to steering software development workflows. (e.g. I heard Fable has a custom system prompt in Claude Code which might explain its markedly more proactive behavior.) So I want to say there's still a lot of value in context engineering though it seems to diminish with each model release (since they're fine tuned on mostly non stupid behavior and need less hand holding). | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
| ▲ | theahura 5 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||
interesting take. I think I disagree, but I like this take a lot and I had to think about it. First, I think that models still need a context layer. One way to think about 'context' is as a form of compression. You provide the model context because it makes it easier for the model to figure out what to do. Even in a world with infinite model capacity and infinite model context, this is still useful because it allows the model to avoid rederiving everything from first principles every time. As long as models perform better using fewer tokens and as long as we care about token spend, context is a useful (necessary?) shortcut. Once you bite that you need some form of context layer, the question is which. Here I do agree that it is better to work with what the models will find familiar (markdown files colocated with code, for eg). But this speaks to over-engineered solutions not understanding their main user (the agent) more than it does the need or lack there of. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
| ▲ | Xcelerate 6 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||
I've wondered this. We have chain-of-thought, harnesses, etc. — workarounds of a sort due to lack of core model capabilities. But I am very curious if much better next token prediction would simply obsolete that whole setup or not. Either way, the answer would be very revealing. | ||||||||||||||||||||||||||||||||
| ▲ | HarHarVeryFunny 6 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||
I don't think so - I think we'll find that to build a brain you need more built-in structure and biases, not less. Bear in mind that brain architecture is learnt too - just over a much longer timescale than an individual lifetime. | ||||||||||||||||||||||||||||||||