Agents

I had such a great time at @aiDotEngineer Europe last week ! Except for one thing: My workshop went terribly because I vibe-slopped a little…

I had such a great time at @aiDotEngineer Europe last week ! Except for one thing: My workshop went terribly because I vibe-slopped a little bit too hard half an hour before it started and was too fra

DGX agentx-post
agentsswyx--x

I had such a great time at @aiDotEngineer Europe last week ! Except for one thing: My workshop went terribly because I vibe-slopped a little bit too hard half an hour before it started and was too frazzled to recover So I promised everyone I'd make a video recording of what it was meant to be. Here's that video! This video is relatively long and aimed at the workshop audience. But if there's any interest, I'll make a 3 minute version In short, I believe that (maybe) 1. Agent harnesses should be modelled as stream processors that call append({ event}) and stream() an append only event log 2. All state in agent harnesses should be event-sourced 3. Harness plugins are just stream processors, too, and can run on other machines from the "harness" itself 4. All agents should have a public URL that events can be posted to 5. You should be able to append the source code of a stream processor to a stream and then it magically runs on that stream To prove it, we make a "coding agent" built on @tan_stack AI and @cramforce 's just-bash and deploy it to a real stream at http://events.iterate.com And because @badlogicgames told us to use our brain more, I though I'd try to actually write the code by hand You can try this yourself by using this repo here https://github.com/iterate/ai-engineer-workshop Media

Related

Source: Swyx (X) | 2026-04-14

Loading related sources…