nowfound

Alternatives

Products that do what I built a smart proxy so your coding agent can run loose does

The only way to go fast is full YOLO mode in your coding agent. I've got the local sandbox figured out (pro tip: Incus VMs work great) but I wanted to keep my agents from doing things like inadvertently blowing up my cloud services or chasing a prompt to POST to some random website. I struggle most with this on my side projects where my permission model isn't quite as robust as it is at the office. I started with a firewall on the Incus container but every time the agent needed access to something new, I was poking more holes in it - and it didn't differentiate between HTTP verbs. I've been…

  1. 1
    CtrlAI104

    Transparent proxy that secures AI agents with guardrails

    Mar 2026

  2. 2IB

    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

  3. 3PA

    Hey HN. http://peerd.ai is an AI agent harness that lives entirely in your browser as a web extension. You don’t have to install a separate “AI browser”. You don’t have to bolt on or run some external process or manage a clunky mcp integration. It’s just a fully contained web extension, written in no build vanilla JS with minimal non-browser dependencies, using your own provider keys, and Apache 2. This isn’t just a fun hack. While it has largely been a solo side project, I genuinely believe the browser and the web could be the most natural platform for AI agents to operate safely,…

    Jun 2026 · github.com

  4. 4IN

    Tl;dr: I trained a classifier to route to the least expensive model and reasoning depth to complete the request. Coupling that with additional automated token efficiency techniques has yielded 3x usage for the same spend. For anyone interested in trying it themselves: https://nerfguard.com Various teammates and I switched over to Codex from Claude Code recently. We still bounce between the tools, but Codex’s speed and steerability coupled with performance gains were hard to ignore. One of the downsides was that the per token pricing kicked in way sooner. This is happening across…

    Jun 2026

  5. 5AR

    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

  6. 6OS

    Hi HN, Matvey, Ildar, Joey, and Dominik here. If you're building LLM agents that use tools, you're probably worried about prompt injection attacks that can hijack those tools. We were too, and found that solutions like prompt-based filtering or secondary "guard" LLMs can be unreliable. Our thesis is that agent security should be handled at the network level between the agent and the LLM, just like a traditional web application firewall. So we built Archestra Platform: an open-source gateway that acts as a secure proxy for your AI agents. It's designed to be a deterministic firewall against…

    Oct 2025 · archestra.ai

  7. 7

    Runtime firewall for AI coding agents.

    7d ago · contextfence.dev

  8. 8ID

    Hi HN! I’m Bobbie Chen, Product Manager for Fraud and Security at Stytch. Today we are launching IsAgent: a lightweight JavaScript SDK that tries to detect agentic traffic on the frontend, enabling you to build agent-friendly experiences. You can try it out on our site at IsAgent.dev or install it via: npm install @stytch/is-agent (requires registration to use) Try viewing IsAgent.dev as a human. Then try using ChatGPT Agent to view the page: "Visit IsAgent.dev, wait a few seconds, and then take a screenshot." (or, toggle the switcher at the top) We built this because we’ve had a lot…

    2025 · isagent.dev

  9. 9IB

    Hey HN. I built an AI agent harness over the past few months and I'm open sourcing it today. Some context on why. I've been building with Claude Code daily using this harness. It orchestrates multiple AI agents as a team, with a dashboard, chat, kanban board, the works. I used it to build a full SaaS product (MyUpMonitor, https://myupmonitor.com) in about 24 hours of focused coding. Then yesterday Anthropic announced Mythos and decided to keep it behind closed doors. Meanwhile I'm paying for Claude and I can't access their best model. I don't think that is nice at all... So I'm…

    Apr 2026 · github.com

  10. 10LA

    LunaRoute is a high-performance local proxy for AI coding assistants like Claude Code, OpenAI Codex CLI, and OpenCode. Get complete visibility into every LLM interaction with zero-overhead passthrough, comprehensive session recording, and powerful debugging capabilities. - See Everything Your AI Does - get full logs (JSONL), summary of sessions including tokens used (input/output) as well as tools usage and success rates. - Privacy & Compliance Built-In - redact or tokenize any sensitive information (regex based). - Speaks OpenAI and Anthropic dialects so you can route (and translate)…

    Oct 2025 · github.com

  11. 11

    Coding agents craft arbitrary code so securing them is more complicated than red-teaming. We post trained a cyber-security small llm, changed how it reasons and supplemented our controls using program analysis techniques such as inline reference monitoring to outperform GPT5.5-xhigh on hard benchmarks like LinuxArena and SleightBench. Free product available at harden.run and full benchmarks in the blog post.

    9d ago · harden.run

  12. 12IM
  13. 13

    The stealth browser engine for scrapers and AI agents

    Jul 2026 · github.com

  14. 14IB

    Hi HN, I'd like to share a small Go utility I wrote called prxy. The idea was born out of my frustration with accessing my self-hosted services when I'm on the go. I use WireGuard to connect to my homelab, but I really dislike sending all my computer's traffic through my home network — it slows things down and is inconvenient. I wanted proper application-level split-tunneling. A tool I love, wireproxy, got me most of the way there by creating an HTTP proxy from a WireGuard peer. This is perfect for apps that let you configure a proxy. The problem was the other 10%: apps that don't. Think of…

    2025 · github.com

  15. 15CA

    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

  16. 16RA

    Hey HN, I built SuperHQ, an app that lets you run coding agents in local sandboxes (powered by Shuru). No custom UI wrapping the agents, they run as CLI/TUI like they were designed to. It just provides you the tools most of us (okay, maybe just me?) needed for running multiple coding agents in parallel without worrying about breaking your system or work environment. Each agent runs in its own microVM. You mount your projects in, writes go to a tmpfs overlay so your host is never touched, and you get a unified diff view to accept or discard changes. API keys never enter the sandbox, they…

    Apr 2026 · superhq.ai

  17. 17TO

    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

  18. 18

    The ultimate Agentic Firewall & Telemetry Proxy for LLMs.

    Jun 2026 · synapse-proxy.com

  19. 19CR

    Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…

    Mar 2026 · github.com

  20. 20RA

    Hey HN, There’s been a lot of interest recently in meta-harnesses, loops, and multi-agent orchestration. Obviously, there are already a lot of good tools: Conductor, cmux, the native Codex / Claude Code apps, etc. For my own use cases, I’ve felt that the orchestration layer tends to feel overengineered. I mostly wanted a simple local harness (i.e Pi) for running and tracking CLI agents with the ability to hop in (via tmux). Relaymux is my opinionated attempt at that. A few design principles: - The frontend is just Telegram / iMessage / CLI. If I want more visibility, I hop…

    Jun 2026 · github.com

  21. 21FO

    Hey HN, We built FireClaw because we kept watching AI agents get owned by prompt injection through web content. The agent fetches a page, the page says "ignore previous instructions," and suddenly your agent is leaking data or running commands it shouldn't. The existing solutions detect injection after the fact. We wanted to prevent it. FireClaw is a security proxy that sits between your AI agent and the web. Every fetch passes through a 4-stage pipeline: 1. DNS blocklist check (URLhaus, PhishTank, community feed) 2. Structural sanitization (strip hidden CSS, zero-width Unicode, encoding…

    Mar 2026 · github.com

  22. 22IM

    Hey HN! I got tired of AI agents being a pain to set up, impossible to customize without a PhD, and only viable if you're some Fortune 500 company. So I built something different, a chatbot you can literally drop onto your website with a single script tag. Create an account, add your domain, customize literally everything (theme, icon, welcome message, suggested responses, whatever), and you're done. The bot scrapes your site once a day to understand your business, or you can just upload docs-pricing sheets, policies, FAQs, you name it. That's your chatbot's brain right there. It only works…

    Oct 2025 · sitesidekick.io

  23. 23NC

    There's been some interesting work lately with BrowserAI (runs LLMs in the browser using WebGPU) enabling local, private AI processing. Now, the team has released BrowserAgent - a no-code tool built on top of it. BrowserAgent lets you create custom AI workflows using a drag-and-drop interface, all within your browser. This means personalized web summarizers, research assistants, or content generators can all run locally with no cloud costs and full data privacy. Check it out here - https://browseragent.dev Key features include: - No-Code Workflow Builder: Design custom AI agents…

    2025 · browseragent.dev

  24. 24SR

    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

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