Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The two concepts of Durable Agents and Distributed Tools pair really well together.

- At work, I don't want to run agents on our overworked and unstable on-prem infra, but there is data we need to access there, so I build agents in the cloud and have on-prem services that listen for work.

- At home, I want to access my agents from the internet, but I don't want to punch holes in my network, so I build agents in the cloud and have at-home services that listen for work.

Of course, it's a bit slower than a single process with local tools, but it can still be a very productive user experience.

And then I think... we're not really inventing something new with Durable Agents and Distributed Tools, we're just moving closer to the event driven architectures that we already know. I can build a durable agent with Lambda Durable Functions and waitForCallback or Lambda Step Functions and waitForTaskToken. Or any pool of compute with a queue or two and persistent state.

So I guess my thought is... you don't need to learn a harness to build an agent. Use what you know. If a harness helps you conceptualize, use it.

 help



Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: