Durable Actor Session Protocol
Details
- External ID
- 49877270
- Source
- HN
- Company
- —
- Product
- Durable Actor Session Protocol
- Website domain
- github.io
- Launched
- Sept. 28, 2026
- Cohort
- —
- Upvotes
- 17
- Upvotes percentile
- 0.7129186602870813
- Tags
- —
- Fetched at
- Sept. 30, 2026, 5:01 p.m.
- Updated at
- Sept. 30, 2026, 5:01 p.m.
Description
Hey HNI'm the author of Jido, an Elixir Actor & Agent SDK. I was building out an Elixir Durable Actor/Agent server and hit a wall regarding communication protocols. I reviewed all the existing protocols; A2A, ACP, AHP and nothing met my needs.I wanted a language agnostic durable actor session protocol. Agent Host Protocol (AHP) from Microsoft was close, but was centered around "chat".The future I envision for agents goes far beyond just text chat. Thus, DASP was born.I'm submitting to HN because I know this is the one place where I'll get real feedback on whether this is an actual need or my tokenmaxxing got the best of me this weekend.This is a builder protocol. I'll be building out clients beyond Elixir and TypeScript, but plan to only support an Elixir server built around my Jido ecosystem.
Enrichment
- Theme
- browser automation and scraping for AI
- Vertical
- Horizontal
- Function
- Data infrastructure
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- durable actor session protocol for distributed systems
- Manually corrected
- False
Could you build this?
No Creating a foundational, distributed distributed-actor communication and recovery protocol requires formal systems design and deep distributed systems consensus expertise.
What it would actually take: The project requires designing a formal wire specification (state machines, idempotency keys, cursor replay semantics, deterministic reconciliation) and reference implementations in Elixir (OTP/GenServer) and TypeScript. The hard part is guaranteeing durable state transitions across network partitions, split-brain scenarios, and multi-client concurrent stream recovery without message loss or out-of-order execution. This demands distributed systems engineers experienced in consensus algorithms, event-sourcing, and actor theory.
Discussion
7 comments analyzed.
Competitors mentioned: celld
Concerns raised: Uncertain state mapping between protocols, Polling vs event subscription
Feature requests: Event subscription stream instead of polling, A2A adapter support
Competitors
Other products that read as similar to this one — 99 launches clear the similarity bar, closest 8 shown.
Attention rank: #26 of 100 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 331 days after the earliest competitor.
- Jido 2.0, Elixir Agent Framework · hn · 2026-03-05 · 323 upvotes · similarity 0.57
- dasp · github · 2026-09-25 · 13 upvotes · similarity 0.54
- Open-source browser for AI agents · hn · 2026-03-11 · 155 upvotes · similarity 0.48
- Mwe-MCP · hn · 2026-07-23 · 5 upvotes · similarity 0.45
- Jido Assembly; Slack Clone in Pure Elixir with Integrated Agents · hn · 2026-08-04 · 25 upvotes · similarity 0.45
- Agent Action Protocol (AAP) · hn · 2026-03-03 · 13 upvotes · similarity 0.44
- PageAgent, A GUI agent that lives inside your web app · hn · 2026-03-05 · 147 upvotes · similarity 0.41
- Rtrvr.ai · hn · 2025-11-12 · 6 upvotes · similarity 0.41
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a data infrastructure tool for Media & entertainment yet.