Alternatives
Products that do what Egregore – Shared memory and coordination for multiplayer Claude Code does
hi HN — we're Cem and Oguzhan. today we are releasing Egregore (https://github.com/egregore-labs/egregore) as an open-source shared memory and coordination substrate for teams using Claude Code. MIT, runs locally, `npx create-egregore@latest --open`. Here's a 90-second walkthrough: https://shorturl.at/e1RX2 we were essentially working on dynamic ontology systems (how to organize unstructured data given context / starting conditions dynamically). since december new capabilities that came around with opus 4.5 completely altered the nature of our work.…
- 1
Open-source unified interface for agent harnesses
21d ago · harnessrouter.ai
- 2
- 3
- 4
- 52C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 6
- 7FO
2025 · github.com
- 8
- 9
- 10
- 11AI
Hi HN, we’re Sai and Aayush, and we’re building Hypercubic (https://www.hypercubic.ai/), bringing AI tools to the mainframe and COBOL world. (We did a Launch HN last year: https://news.ycombinator.com/item?id=45877517.) Today we’re launching Hopper, an agentic development environment for mainframes. You can download it here: https://www.hypercubic.ai/hopper, and you can also request access and immediately get a mainframe user account to play with. There's also a video runthrough at https://www.youtube.com/watch?v=q81L5DcfBvE.…
May 2026 · hypercubic.ai
- 12
- 13CO
We recently started to use agents to update some documentation across our codebase on a weekly basis, and everything quickly turned into cron jobs, logs, and terminal output. it worked, but was hard to tell what agents were doing, why something failed, or whether a workflow was actually progressing. We thought it would be more interesting to treat agents as long-lived workers with state and responsibilities and explicit handoffs. Something you can actually see and reason about, instead of just tailing logs. So we built Clawe, a small coordination layer on top of OpenClaw that lets agent…
Feb 2026 · github.com
- 141O
Hi, we're Sergey and Serafim. We've been building dev tools at 21st.dev and recently open-sourced 1Code (https://1code.dev), a local UI for Claude Code. Here's a video of the product: https://www.youtube.com/watch?v=Sgk9Z-nAjC0 Claude Code has been our go-to for 4 months. When Opus 4.5 dropped, parallel agents stopped needing so much babysitting. We started trusting it with more: building features end to end, adding tests, refactors. Stuff you'd normally hand off to a developer. We started running 3-4 at once. Then the CLI became annoying: too many terminals, hard to…
Jan 2026 · github.com
- 15AL
I have been pushing up to 90 commits a day on a MacBook Air via 4-5 parallel agents. As you can imagine when all the agents try to build, test and run dev servers on an 8GB machine it is the fast lane to a force quit and restart. I also did not want to pay the CI minutes on 90 pushes a day. So I designed a local merge queue to have all commits land one at a time and fully tested. Hopefully this helps other folks with more modest machines. Appreciate any feedback.
Jul 2026 · github.com
- 16FC
Just to clarify the background a bit. This project wasn’t planned as a big standalone release at first. On January 16, Ollama added support for an Anthropic-compatible API, and I was curious how far this could be pushed in practice. I decided to try plugging local Ollama models directly into a Claude Code-style workflow and see if it would actually work end to end. Here is the release note from Ollama that made this possible: https://ollama.com/blog/claude Technically, what I do is pretty straightforward: - Detect which local models are available in Ollama. - When…
Jan 2026 · github.com
- 17RA
Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…
Jan 2026 · github.com
- 18GU
Gigacode is an experimental, just-for-fun project that makes OpenCode's TUI + web + SDK work with Claude Code, Codex, and Amp. It's not a fork of OpenCode. Instead, it implements the OpenCode protocol and just runs `opencode attach` to the server that converts API calls to the underlying agents. We build this to scratch our itch of being able to rapidly switch between coding agents based on the task at hand. For example, we find that: - Claude Code is the best executor & fast iterator - Codex (high) is the best for complex or long-running tasks - OpenCode for fine-tuned, do-exactly-as-I-say…
Feb 2026 · github.com
- 19CA
May 2026 · oacp.dev
- 20CV
I explored how I can use AI when writing software beyond code completion, and I didn't like any of the UX I saw (maybe except Cursor). Well, I do all my work in vim. Claude knows how to use vim! And... you can do anything(!) from vim. Turns out, embedding Claude in vim means you get a fully agentic AI pair programmer in <1000 LoC. (See the GitHub README for examples of what "fully agentic" means.) And if you have some semantic vim tools (jedi.vim, eclim, ...) set up, Claude could use them if instructed. Unlike CLIs, you can review Claude's changes, and keep the chat history. So an editor…
2024 · github.com
- 21IB
Hi! My name is Herve Kom, a computer science student that is interested in learning new things everyday! As one of my graduation project, I have developed a Claude Code -like Coding CLI, but with enhancement for API Testing: - Auto-generate & run tests (unit, e2e, Playwright, CI/CD, etc.) - Say bye-bye to hallucinations with built-in MCP Server to let LLM directly read from API Docs - Adding Agent.md support for better context persistence across your whole codebase - Automatic bug & security scans (logic is kind of basic but works great!) - Vibes, I want it to feel less "enterprise" but…
2025 · github.com
- 22
- 23SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 24PM
I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →