Comment by wiesbadener
3 days ago
They state:
> RLMs are not agents, nor are they just summarization. The idea of multiple LM calls in a single system is not new — in a broad sense, this is what most agentic scaffolds do. The closest idea we’ve seen in the wild is the ROMA agent that decomposes a problem and runs multiple sub-agents to solve each problem. Another common example is code assistants like Cursor and Claude Code that either summarize or prune context histories as they get longer and longer. These approaches generally view multiple LM calls as decomposition from the perspective of a task or problem. We retain the view that LM calls can be decomposed by the context, and the choice of decomposition should purely be the choice of an LM.
lol this is literally one of the only reason competent people are using subagents. it is literally
@summarizable(recursive=True)
def long_running_task(Subagent)
on my long horizon tasks, where the hierarchy is determined at agent execution time…