lukebuehler

7 ms·

1.
by lukebuehler 6d ago
The key here is that they are _not_ just turning "running codex on a VM" into an API. Their harness is running outside a VM, interacting with a VM when needed. See the diagram in their post. This allows them to scale the agent run
2.
by lukebuehler 6d ago
I've been working on a custom managed agent (see my other top-level comment), I find it is actually a manageable undertaking. It does feel herculean, but somehow doable. I do not find their hidden reasoning tokens to be insurmountable
3.
by lukebuehler 6d ago
I think this is an important direction: managed agents that control compute. For those who are interested in a self-hosted version of the same concept, I've been working on something like this here: https://github.com/s
4.
by lukebuehler 1mo ago
The OpenAI API style (completions) support is coming this week. Currently working on it.
5.
by lukebuehler 1mo ago
Im working on one here: https://github.com/smartcomputer-ai/lightspeed The core is there. But there is some work to be done to have a nicer shell and all, which I’m currently focusing on.
6.
by lukebuehler 1mo ago
Fully agree that in the end sandboxes are required to get frontier performance out of the models. But you can have both: rund the agent outside the vm/sandbox and orchestrate work on it, either directly via shell calls or kicking off a
7.
by lukebuehler 2mo ago
All the power to you, and I hope Pi will be able to continue its unified layer. However, there is an alternative: model the session fully in the provider native structures, extract only what is needed for harness specific branching, and tre
8.
by lukebuehler 2mo ago
Yes, I agree with your point and article regarding hidden or sealed state. So, I'm aware that this is a separate point from the article, and I'm well aware of Pi's model abstraction layer, which is one of the best (others are
9.
by lukebuehler 2mo ago
Fair. But in the background of the article is clearly the goal to make sessions portable, not just being able to inspect it. It's partially implied even in the title. There is just a whole discussion to be had about the second issue an
10.
by lukebuehler 2mo ago
I think there are two things going on more generally: 1) providers increasingly adding hidden state that the user or developer cannot inspect, port, or do anything with. This is clearly bad. 2) providers increasingly diverging how they impl
11.
by lukebuehler 2mo ago
It’s endlessly fascinating to read the AI transcript of an expert who _really_ knows how to cut to the chase. It just shows how much you can potentially squeeze out of these models. I’m also surprised to see that even Terrence Tao seems to
12.
by lukebuehler 2mo ago
I’m thinking along my similar lines. Expansion, if it happens, will likely not be on a recognizably human substrate, but rather something else. But currently it’s more of an intuition than a rigorous argument for me. How do would you formul
13.
by lukebuehler 2mo ago
A self-hostable Claude Tag or OAI Work [0]. A while ago, I realized that most new agent harnesses being built must be hosted on your machine or on a VM--in other words the agent needs a full OS process at all times. But we do not have good
14.
by lukebuehler 2mo ago
Make hay while the sun is out.
15.
by lukebuehler 2mo ago
Very interesting: I wonder if the RL approach is diverging between Anthropic and OAI? I noticed that Fable uses shell tools almost exclusively (even to search and edit files), compared to previous Anthropic models. Having run some experimen
16.
by lukebuehler 2mo ago
yes, basically people that want to host powerful, long-running agent runs not on dedicated VMs (although lightspeed can use those too), but on an abstraction layer above. My thesis is that the right abstraction is durable workflow engines.
17.
by lukebuehler 2mo ago
I think these kind of semi-coding agents--but hosted--are the future for enterprises. Claude Tag, Claude Cowork, now Work by OAI. Agents-on-your-machine clearly have their place, but for many workflows this is too unruly. Hence, the "l
18.
by lukebuehler 2mo ago
Oh man, I love capitalism spoiling us here. I was just enjoying my extra Fable credits, now I'll switch to using 5.6 this weekend. I was planning to ration my Anthropic credits, I guess now I do not have to. And I was half wondering if
19.
by lukebuehler 2mo ago
getting downvoted for my other answer. I wasn't clear: yes, there is of course a lot of prior art in pi, and pi specifically does not just store the session events, but adds an abstraction for easy branching which is great. But what I
20.
by lukebuehler 2mo ago
most coding harnesses store the exact messages that have been sent to the llm and the messages items that have come back from the llm, not much else. Then, there is also a set of events/commands/etc that are in-memory only. Togeth
21.
by lukebuehler 2mo ago
Very cool. I settled on the same/similar design in my agent harness. All relevant events that affect the context window are stored in an event log. Forking agents and sessions is simply setting a pointer to the sequence number of anoth
22.
by lukebuehler 3mo ago
I work with large enterprises that _only_ run critical workloads on locally hosted models. Think banks, insurance, etc--businesses that absolutely cannot leak any data. They also have CC and Codex, but their use is extremely restricted; any
23.
by lukebuehler 3mo ago
Agent harness for durable workflows, starting with Temporal. Most agents for durable workflows feel like toy examples. There is no "Codex" or "Claude Code" for, say, Temporal. So I'm building full-featured agent for
24.
by lukebuehler 3mo ago
Arguably, if your agent needs a lot of custom logic to drive the agent loop it isn't an "agent" at all. At best it is an agentic workflow, or rather a workflow with some LLMs calls in between. I think that's why agent SD
25.
by lukebuehler 4mo ago
This is why taking investments too early is usually a mistake. It locks you in to one hand. Of course, you can pivot, but it is much harder with investors looking over your shoulder.
26.
A Critique of Cybernetics, by Hans Jonas (1953) [pdf](s3.amazonaws.com)
3 points by lukebuehler 4mo ago|1 comments
27.
by lukebuehler 4mo ago
Still one of the best critique of AI agents, even today.
28.
by lukebuehler 4mo ago
I keep saying this is the single most important article to consider when talking about AI assisted software building. Everyone should read it. The question should always be: is a human building a theory of the software, or is does only AI u
29.
by lukebuehler 4mo ago
See A Canticle for Leibowitz
30.
by lukebuehler 6mo ago
It's a tradeoff. Technically, you need very few programs, you can let an agent do everything and coordinate everything. But that is also inefficient, it's slow and uses a lot of tokens. So you allow the agent to build tools and co

More ›