Alternatives
Products that do what OpenShears – I built an uninstaller because OpenClaw refuses to die does
Hey HN, I've been using OpenClaw for a few months as my local LLM gateway. It was genuinely fun — the convenience of routing multiple models through a single endpoint is hard to beat. But along the way, I stumbled upon a few surprises that made me uncomfortable: - Config files scattered in unexpected places (~/.openclaw, ~/.clawdbot, and more) - Background processes that respawn after termination - Logs that quietly accumulate without rotation - Cached data persisting long after I thought I'd removed it None of this is necessarily malicious, but when I decided to move on, I wanted…
- 1
- 2ZS
I’ve been cautiously (and nervously) playing with openclaw and a number of other claw and code agents for a while now, but trying out different ones was tricky so I wanted a simple way to switch out channel ownership… then I wanted more. Security is hard, and I wanted to make it easier. This is FAR from polished, and no claims that I’m a “security expert” but I tried to think and research a bit on different threat models (I think of 2 broad ones for agents, external adversaries and internal agentic failures) and try and offer best in class protection on both, while also not having any…
Apr 2026 · github.com
- 3
- 4AO
Hey HN! I've been wanting to use something like OpenClaw for a while but couldn't get myself to give it access to anything important due to all the risks involved. Prompt injection is still a problem (even though some people seem to ignore it) and so are hallucinations and mishaps that cause agents to do things like delete production data [1]. Even harnesses like Claude Code and Codex are subject to this, particularly since we're getting progressively looser about how we run them e.g. Conductor is really popular and runs agents without any sandboxing. That means we're in a bit of an…
Apr 2026 · agentport.sh
- 5IB
Hey HN, I'm Daniel, solo dev from Germany. I built ClawHosters (https://clawhosters.com), a managed hosting platform for OpenClaw, the open-source AI agent framework. Quick timeline: domain registered February 5th. First paying customer six days later. I probably should have spent more time on it, but it works. If you haven't seen OpenClaw, it lets you run a personal AI assistant that connects to Telegram, Discord, Slack, and WhatsApp. Self-hosting it is absolutely possible, but it's a pain. You're dealing with Docker setup, SSL certs, port forwarding, security hardening, keeping…
Feb 2026 · clawhosters.com
- 6
Zero-config hosting to launch specialized AI teams instantly
Feb 2026
- 7PI
People seem to be blindly hooking up their OpenClaw’s to their personal data. So, I built runtime controls to prevent at the least, very simple prompt injection attacks. Once installed, it hooks to Node.js child_process module in the gateway process and listens to tool calls and their response streams. And a fetch hook to monitor user prompts (both could’ve been through fetch, happy to discuss why this whole layer couldn’t just be a proxy). There are two layers of protection: First: Whenever there is a read-only tool call whose response an attacker can modify, we extract that part of the…
Feb 2026 · github.com
- 8TO
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
- 9IM
As a handsome local AI enjoyer™ you’ve probably noticed one of the big flaws with LLMs: It lies. Confidently. ALL THE TIME. I’m autistic and extremely allergic to vibes-based tooling, so … I built a thing. Maybe it’s useful to you too. The thing: llama-conductor llama-conductor is a router that sits between your frontend (eg: OWUI) & backend (llama.cpp + llama-swap). Local-first but it should talk to anything OpenAI-compatible if you point it there (note: experimental so YMMV). LC is a glass-box that makes the stack behave like a deterministic system, instead of a drunk telling a story about…
Jan 2026
- 10IB
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
- 11CO
Hi HN, I’m building ClawDeploy for people who want to use OpenClaw but don’t have a technical background. The goal is simple: remove the setup friction and make deployment approachable. With ClawDeploy, users can: - get a server ready - deploy OpenClaw through a guided flow - communicate with the bot via Telegram Target users are solo operators, creators, and small teams who need a dedicated OpenClaw bot but don’t want to deal with infrastructure complexity. Would love your feedbacks :)
Feb 2026 · clawdeploy.com
- 12OS
I built a skill library for OpenClaw (always-on AI agent runtime, not session-based) where the agent can teach itself new behaviors during normal conversation. The idea: you tell your agent "every time I ask for a code review, always check for security issues first." It invokes a create-skill skill, writes a new SKILL.md, and that behavior is live immediately — no restart, no config change, no developer required. What I think is actually useful (the safety cluster): • loop-circuit-breaker: OpenClaw retries ALL errors identically. This halts on the 2nd identical failure before it burns your…
Mar 2026 · github.com
- 13OS
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
- 14OS
Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…
Jan 2026
- 15LC
Hey HN, wanted to share this cli and skill I built @ Steel (I'm the founder) I was trying to set up openclaw on railway and quickly bumped up against issues with a lack of browser access, a core component of the system. Agents like OpenClaw and CC are super good at using browsers but, similar to code sandboxes, they should be able to control these browser in the background, in parallel, without getting blocked by captchas. So I reworked agent-browser, the most popular cli for browser agents, to navigate Steel cloud browser sessions to they can run at scale and unhindered. It's a relatively…
Mar 2026 · twitter.com
- 16IV
Feb 2026 · github.com
- 17ON
I was wondering... why do we need a Mac Mini, a VPS, or a Docker container to run OpenClaw? Your browser already has a secure sandboxed OS, a database, a filesystem, and a JS engine. What if we just... used those? So I built OpenBrowserClaw inspired by the simplicity of NanoClaw but running entirely in a browser tab. - Claude API with full tool-use loop - Shell commands in a v86-emulated Alpine Linux (yes, a Linux VM in WASM, in your browser) - File I/O via OPFS - Data persistence in the browser local storage - Telegram integration over plain HTTPS - Zero runtime dependencies No server.…
Feb 2026 · openbrowserclaw.com
- 18CR
Clawbernetes turns OpenClaw into an AI-native infrastructure manager. Instead of YAML, Helm charts, and kubectl — you have a conversation. "Deploy Llama 70B on the node with the most VRAM" → agent selects the best node, pulls the image, starts the container with GPU passthrough, sets up health monitoring. "Why is inference slow?" → checks GPU temps, VRAM, CPU load. "GPU 0 at 89°C — thermal throttling. Want me to reduce batch size?" 23 crates, 74K lines of Rust, 1,866 tests, zero unsafe in core. Supports CUDA, Metal, ROCm, Vulkan, and CPU SIMD. Components: - clawnode: node agent with 80+…
Feb 2026 · github.com
- 19HA
Hey HN. I'm an engineering student at Waterloo building stateful AI agents, and I kept hitting the same wall: whenever my Python scripts crashed or dropped a connection, the underlying Puppeteer or Ollama processes would just sit there orphaned, eating RAM until the node OOM-killed itself. Standard load balancers break sticky sessions, and passive HTTP timeouts are too slow for cleanup. I couldn't find a good local process pool that actually cleaned up dead stateful sessions reliably, so I built Herd in Go. It uses a persistent stream (gRPC/Unix sockets) strictly as a dead-man's switch.…
Mar 2026
- 20CA
TL;DR: we built a framework-agnostic agent runtime that uses gVisor for isolation and runs on k8s. It’s open-source under AGPLv3 Recently we’ve been working on a customer support “AI assistant” - essentially an interactive knowledge base/L1 support but with an option to touch resources that belong to a customer it’s talking to. We found existing tools to be lacking in these aspects: 1. Fully intercepted i/o. We wanted to trace out LLM calls as well as any other networking calls attempted by the harness so that guardrails and audit trails apply to all current and future systems…
Jul 2026 · github.com
- 21PU
After seeing a cool demo of a hack on Twitter, I built a cross platform version of it that works well and uses streaming. From anywhere on Mac and Linux, trigger Ollama and optionally feed it your clipboard. I built it yesterday and it's already very useful to me. I'm pretty excited about it and wanted to share!
2024 · github.com
- 22OL
Hello Hacker News, I often hear people saying "all build-systems suck", an opinion I have been sharing for years, and this is the motivation for this project. I finally got the opportunity to make it open-source, and here it is. In a few words, it is like make, except it can be comfortably used even in big projects using HPC (with millions of jobs, thousands of them running in parallel). The major differences are that: - dependencies are automatically tracked (no need to call gcc -M and the like, no need to be tailored to any specific tool, it just works) by spying disk activity - it is…
2025 · github.com
- 23WA
Hi HN I built WrapClaw, a SaaS wrapper around Open Claw. Open Claw is a developer-first tool that gives you a dedicated terminal to run tasks and AI workflows (including WhatsApp integrations). It’s powerful, but running it as a hosted, multi-user product requires a lot of infra work. WrapClaw focuses on that missing layer. What WrapClaw adds: A dedicated terminal workspace per user Isolated Docker containers for each workspace Ability to scale CPU and RAM per user (e.g. 2GB → 4GB) A no-code UI on top of Open Claw Managed infra so users don’t deal with Docker or servers The goal is to make…
Feb 2026
Ranked by how close each launch is in meaning, then by votes. Refine with a description →