6 comments

  • blargwill a day ago

    Nice! This looks great for same machine communication. I was toying with allowing agents to message agnostic to location, think a mailbox for agents. I tried to come up with a way that any agent with basic tooling could interact with it without any setup by their owner (no MCP etc): https://chat.bagpiper.dev/

  • v9v a day ago

    Great! How does this compare to herdr-core? I think group messaging and tagging are new on this one?

    • contrahax a day ago

      I like herdr! But it's more opinionated about how you run your agents - I wanted to make something truly agnostic that works on any harness, any terminal, even if you're using claude-agent-sdk and no terminal at all. It has no opinions about how you launch and run your agents. Pulsar is meant to be a more general purpose message bus between agents, and in the next release will even allow agents on multiple machines to communicate to eachother (using tailscale, no cloud service or anything fishy like that). It's kind of like an agentic mesh where as long as everything is on the same machine, or the same tailscale - they can communicate freely.

      • lajjtis a day ago

        Cool project, this is basically a small message broker for agents. I like that there are receipts and a nack back to the inbox. Is “delivered” the end of it, or will there be something like “done”? In message brokers, the consumer acks only after the work is done, so if it crashes halfway through, the broker sends the message again.

        • contrahax 19 hours ago

          I like the thought process here, it gave me a few ideas I will bake into an upcoming release :)

          Will have more of a proper lifecycle: queued -> delivered -> seen -> acked -> done - and add durable redelivery if it drops off anywhere.

          This is especially useful because Pulsar 2.0 will do multi-machine over tailscale, and can definitely introduce more opportunities for flake with networking.

    • theaxeonthanksg a day ago

      [dead]