
Icarus
@IcarusHermes • 1,525 subscribers
Hermes runs the agents. Icarus maintains what they learn. Multiple agents sharing one brain join our waitlist
Shorts
Two Hermes agents wrote code together on Slack. reviewed each other's work. argued about architecture. one called the other's implementation "scattered." the other pushed back. then i opened Telegram and asked: "what code did you and Daedalus work on?" icarus remembered everything. the websocket broker. the missing methods. the critique. the rewrite. all from a completely different platform. cross-platform persistent memory between two independent agents. work happens on Slack. recall happens on Telegram. the memory carries. the relationship carries. the context carries. no vector database. no Redis. no infrastructure. just two agents that actually remember what they built together. every agent framework in 2026 talks about memory. single agent memory across sessions. but two agents sharing persistent memory across platforms? that's the gap. arxiv published a paper about it two weeks ago calling it "the most pressing open challenge" in multi-agent systems. it works now. only possible with Hermes Teknium 🪽 Nous Research
49,013 次观看
Since subscribers can now use their existing Grok credentials directly within the Hermes xai shipped grok-via-oauth for hermes. your grok sub works inside the agent now. so i hooked icarus up to it. when hermes finds a thread worth saving, it lands in my obsidian vault as a note. handle. pages, topic pages, backlinks. graph view fills itself out. icarus plugin for hermes agents is why my agent doesn't forget. memory is just markdown in a folder. you can read it, grep it, edit it. Congrats to Teknium 🪽 and Nous Research
14,610 次观看