nowfound

Alternatives

Products that do what Voidleap Code does

Coding environment and harness. BYOK. Build better.

  1. 1
    Projekt128

    The BYOK Design & Dev Tool for Building with Agents

    Mar 2026

  2. 2

    The first AI agent for product, design, and code

    Nov 2025

  3. 3

    Models matter. Context matters more. Give your agent a plan.

    Jun 2026

  4. 4
    Factory168

    Agent-native development on Web, IDE, CLI, Slack and mobile

    Sep 2025

  5. 5

    Build production agents with harness and sandbox

    Apr 2026

  6. 6
    Helix132

    Your collaborative AI coding agent

    2025

  7. 7

    Tag any agent, wherever work happens.

    28d ago · agentconnect.md

  8. 8

    Build powerful agents in seconds with AI CANVA GENERATOR

    2025

  9. 9

    Your AI agents team, terminals, notes: one infinite canvas

    Jul 2026 · agentgrid.sh

  10. 10VP

    Hi HN, I built VAEN (an open source CLI) because I kept running into a boring problem with AI coding-agent workflows: the setup becomes useful, but then it is hard to move. A good, useful agentic harness consists of more than just instructions: skills, mcp servers and more. There should be a better way to share those than just .MD files, and that is why I created VAEN. What works: create a yaml, run the CLI commands as per the repo, and get a .agent file that you can share and extract. Think of how awesome it could be if anyone could use a very useful agentic harness, and share it with one…

    May 2026 · github.com

  11. 11AR

    Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…

    May 2026 · agents-cli.sh

  12. 12IB

    Hi HN, I’m the creator of Cordum. I’ve been working in DevOps and infrastructure for years (currently in the fintech/security space), and as I started playing with AI agents, I noticed a scary pattern. Most "safety" mechanisms rely on system prompts ("Please don't do X") or flimsy Python logic inside the agent itself. If we treat agents as autonomous employees, giving them root access and hoping they listen to instructions felt insane to me. I wanted a way to enforce hard constraints that the LLM cannot override, no matter how "jailbroken" it gets. So I built Cordum. It’s an open-source…

    Jan 2026 · github.com

  13. 13CA

    I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!

    Sep 2025 · infrastructureas.ai

  14. 14AN

    Hi HN! I'm building Ano because I was tired of Slack's bloat and sluggishness, and never got any value out of their agent implementation. Ano is built local-first for speed (using Rocicorp Zero), focused on communication, and lets you use your own code agent as an assistant (Claude in my case, but it works with Codex too). I use the code agent to summarize anything unread (linking back to what matters), respond with context, and share data to and from connected tools (GitHub, Posthog, Attio, etc). Using your code agent for this might sound counter-intuitive, but to me it's the most powerful…

    Jun 2026 · ano.chat

  15. 15SA

    Hi HN, This is a project I've been working on since the beginning of 2025 full time, without funding. Coding agents have fundamentally changed the way we write software. When you let an agent write code, pull dependencies, and run scripts, you are delegating trust while still keeping the responsibility. You shouldn't have to choose between moving fast with agents and maintaining basic control over your host machine. Normally, we just inspect the final result, treating the app like a black box. Most security tools only sandbox the app runtime and ignore the build phase. CapaKit is my attempt…

    Jun 2026 · capakit.com

  16. 16

    Context and workflows for AI coding agents

    20d ago · pathrule.io

  17. 17SR

    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

  18. 18WS

    I built a collection of webhook skills because AI coding agents are surprisingly bad at webhook integrations. The generated code looks reasonable until you run it, then signature verification fails, raw body handling is wrong, or the middleware order breaks everything. PostHog's research on LLM code generation (https://posthog.com/blog/correct-llm-code-generation) found that agents produce more reliable code when referencing known-working examples rather than reconstructing from training data. That's the approach here. `webhook-skills` is a collection of provider-specific…

    Feb 2026 · github.com

  19. 19AS

    AI changed the way we code, but we're still using the old processes, and we've become the bottleneck, the AI is waiting for us - to reply, to open our laptops, to review the code, and so on. We're building the future of AI software development. The agents are autonomous, they run in sandboxes, automatically fix the pipelines, and deliver you the final, working code. You can use live preview to see the changes they made. Working across multiple repositories, all within the same session. This is the future - you don't need an IDE, and you don't have to run anything locally.

    Mar 2026 · agenhq.com

  20. 20IB

    Hi HN, I built a tool [1] that resolves breaking changes when you upgrade npm packages. I know keeping my dependencies updated is good hygiene but I really have no motivations to do them. The time to fix breaking changes then validate them makes the ROI lopsided. Automating these helps me reduce the barrier to a good habit. It works on typescript and tsx projects. BYOK (bring your own GPT-4 key) for the codegen. MIT license. How does it work? - Bumps the package version, builds your project, and then runs tsc over your project to understand what breaks - Uses ts-morph [2] to create an AST of…

    2024 · github.com

  21. 21SA

    I've been working on a new programming language for AI agents. I would love your input on what makes programming languages good for AI agents, especially syntax, compiler, and tooling that could help AI agents write code. What makes Sigil good for coding agents? I've turned conventions into compiler rules whenever possible. The compiler owns the canonical printer and every AST has one accepted textual representation. For almost every syntax feature I tried to save tokens. Order and naming conventions are enforced. No more "I think this argument is important so it should come first." Most…

    Apr 2026

  22. 22IB

    The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.

    2025 · github.com

  23. 23TO

    I built DevClaw, an OpenClaw plugin that turns each Telegram group into an isolated, autonomous dev team: planner/orchestrator, DEVs, and QA all running on their own. I use it for all my development now. Issues on GitLab/GitHub are the single source of truth, and three things compound to save around 70% on tokens: model tiering (Haiku for typos, Opus for architecture), session reuse across tasks, and token-free scheduling that burns zero LLM calls for orchestration. Please try it and give some feedback. Also keen to hear from anyone running autonomous coding agents, especially what…

    Feb 2026 · github.com

  24. 24MA

    This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…

    2025 · github.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →