7 comments

  • ksajadi 8 minutes ago
    looks cool. how's that different from things like markbase dispatch where you can fire up the agent remotely with some given context. i mean what is the advantage of having the agent run always vs start and stop when you need it but give it a long-term memory context? maybe i'm missing something.
  • swyx 4 hours ago
    • kmansm27 4 hours ago
      haha yes! this was the reasoning for making durability native in our harness
    • isehgal 3 hours ago
      thanks swyx! the log is the agent is a core insight behind this
      • swyx 3 hours ago
        you beat pi-durable to it!
  • asherdale1 4 hours ago
    feels like everyone is converging on durable agents lately: pi durable, cloudflare agents on durable objects, vercel's durable harness
    • kmansm27 3 hours ago
      Yep, I think that all harnesses will require native durability, and pi-durable is a step in the right direction. I'm skeptical of bolted-on durability, like vercel's durable-harness, because they have to neuter the harness for things they can't reliably make durable (e.g. https://github.com/vercel-labs/durable-harness/blob/fb056a3c...)
  • divamgupta 1 hour ago
    Wow Literally what I was looking for.
  • rohan_joshi 2 hours ago
    i was looking for good self-hostable durable agents to automate a persistent keyword watcher across sm. gonna give this a go. any pointers you recommend?
    • isehgal 2 hours ago
      nice, this is close to something we run ourselves. we put up examples of sm agents that scan socials daily for keywords and DMs us (docs here https://docs.omnara.com/examples/x-signal-agent). probably the fastest starting point is to point your agent to it and ask it to swap in your keywords
  • alexcodebytes 15 minutes ago
    [flagged]
  • singh_abinashi 4 hours ago
    [flagged]