Alternatives
Products that do what Claurst does
Agentic coding for builders who ship
- 1
- 2
- 3JA
Hello HN, I don't post on here much, but wanted to get some eyes on a new project I'm just launching. I think we definitely need one more AI code agent.. I'm a long-term C++ dev, and over 30+ years I've created some successful audio dev tools (JUCE, the Tracktion DAW, the Cmajor DSP language). All of these came from me getting annoyed with something I had to use, and deciding to have a go at my own take on whatever it was. So Juggler is my attempt at an AI code agent, after spending too many hours loving what the models could do, but hating the CLI experience, and having some opinions of…
Jul 2026 · github.com
- 4
- 5
- 6
OSS IDE for controlling AI coding agents with built in loops
Jul 2026 · auravcs.com
- 7
Technical Q&A that helps grow your Slack / Discord community
Oct 2025
- 8
- 9
- 10
- 11
- 12AO
Hi! I’m Nathan: an ML Engineer at Mozilla.ai: I built agent-of-empires (aoe): a CLI application to help you manage all of your running Claude Code/Opencode sessions and know when they are waiting for you. - Written in rust and relies on tmux for security and reliability - Monitors state of cli sessions to tell you when an agent is running vs idle vs waiting for your input - Manage sessions by naming them, grouping them, configuring profiles for various settings I'm passionate about getting self-hosted open-weight LLMs to be valid options to compete with proprietary closed models. One…
Jan 2026 · github.com
- 13RA
Hey HN! I've been building Claurst - a clean-room implementation of Claude Code in Rust, with extra features to make my ideal agentic Open-Source AI CLI. It's WIP and rough, but I'm shipping a lot to make it amaze amaze amaze. Inspired by this HN post [1] I saw a few hours ago about caveman speak for token-efficient output, I added /Caveman and /Rocky (from project Hail Mary) to Claurst. Caveman grammar drops ~70% of output tokens keeping technical substance and Rocky brings a close compression with more personality. Both are first-class slash commands with three levels: lite,…
Apr 2026 · github.com
- 14
- 15HM
We built a Rust MCP server, which wraps the excellent headless terminal (HT)[1] to makes it available for agentic coding tools. Most agentic coding tools struggle with blocking, interactive terminal tools (all the boilerplate generator, infra CLI tools etc). This is because many existing CLI dev tools are built for humans and require interactive input. We built this so agentic coding tools (Claude Code, Cursor, Memex, etc) can “see” and “interact” with terminals exactly like humans do. In our demo video [2], you'll see it operating vim/emacs just as a human would - selecting options,…
2025 · github.com
- 16KC
We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The problem isn't just secret sprawl. It's that there's no lineage of access. You don't know which developer launched which agent, what it accessed, or whether it should have been allowed to. The moment you hand raw credentials to a process, you've lost the ability to enforce policy, audit access, or rotate without pain. The…
Apr 2026 · github.com
- 17CS
Coding agents don't have long-term memory. But you do have months of full-fidelity agent transcripts stored on your machine. A simple solution that goes a long way: ingest those transcripts and logs into a structured SQLite database, then search them with ranked text match. Everything is fully local and doesn't require anything fancy like a graph database or hosted memory service. This is the idea behind ctx, a Rust CLI that handles the ingestion and searching. We give our agents a skill that tells them to reference past sessions before working in an area. Usually we do this through an…
Jul 2026 · github.com
- 182C
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
- 19CB
Clink lets you use the coding agents you already pay for (Claude Code, Codex CLI, Gemini CLI, Z.ai GLM) to build → live-preview → ship apps in an isolated container. No token purchases, no extra cost for coding. Just link your existing Claude/OpenAI/Gemini account and start building and deploying instantly. Why we built this: Claude Code is our go-to for coding, but it lacked preview + deploy capabilities. We didn't want to pay Lovable again just for that. Different agents excel at different tasks - Claude Code for versatility, Codex for complex work, GLM for speed. We needed one…
Oct 2025 · clink.new
- 20OM
I built OpenSwarm because I wanted an autonomous “AI dev team” that can actually plug into my real workflow instead of running toy tasks. OpenSwarm orchestrates multiple Claude Code CLI instances as agents to work on real Linear issues. It: • pulls issues from Linear and runs a Worker/Reviewer/Test/Documenter pipeline • uses LanceDB + multilingual-e5 embeddings for long‑term memory and context reuse • builds a simple code knowledge graph for impact analysis • exposes everything through a Discord bot (status, dispatch, scheduling, logs) • can auto‑iterate on existing PRs and…
Feb 2026 · github.com
- 21MA
Apr 2026 · github.com
- 22
Your agents share one source of truth
May 2026 · agentnorth.io
- 23AO
Hello Folks! Agentic Orchestrator is a terminal tool that takes complex feature requests and builds them by orchestrating coding agents through a series of phases that emulate a full-fledged engineering flow: requirements clarification, research, design, multi-phase planning, implementation, and review. It is a single pane of glass for all your features and exposes post-publish utilities such as resolving merge conflicts and responding to review comments. The key design choice is that this is deterministic orchestration on top of undeterministic agents: things like "human review gates",…
Jun 2026 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →