2 ms·
This is great, and I keep my fingers crossed for Hatchet! One use case I imagine is key here is background/async agents, so OpenAI Codex/Jules style, so that's
by movedx01 1y ago
This is great, and I keep my fingers crossed for Hatchet!
One use case I imagine is key here is background/async agents, so OpenAI Codex/Jules style, so that's great if I can durably run them with Pickaxe(btw I belive I've read somewhere in temporal docs or some webinar that Codex was built on that ;), but how do I get that real-time and resumable message stream back to the client? The user might reload the page or return after 15 minutes, etc. I wasn't able to think of an elegant way to model this in a distributed system.
- gabrielruttner 1y agoperfect use case and this was one of the reasons we built pickaxe, we have a number of coding agents/pr review platforms powered by hatchet with similar patterns already... more to come on the compute side for this use case soon we'll have agent->client streaming on the very short term roadmap (order of weeks), but haven't broadly rolled out since its not 100% ready for prime time. we do already have wait for event support for client->agent eventing [1] already in this release! [1] https://pickaxe.hatchet.run/patterns/human-in-the-loop https://pickaxe.hatchet.run/patterns/human-in-the-loop
- cmdtab 1y agoPretty much was my first question if there was support for streaming events. Any way we could be beta tester? ༼ つ ◕_◕ ༽つ
- gabrielruttner 1y ago100% shoot me a note at gabe [at] hatchet [dot] run and we can share some details here for the signatures that exist, but are going to change