Alternatives
Products that do what OpenClix, Agent friendly, open-source retention tooling does
Hi HN, I’m sharing OpenClix, an open source toolkit for running mobile engagement and retention flows directly inside your app. The motivation came from repeatedly seeing the same pattern when teams try to improve retention. They end up stitching together push providers, experimentation tools, analytics pipelines, and backend services just to ship simple onboarding nudges or re engagement reminders. The setup becomes complex very quickly. OpenClix takes a different approach. Instead of a hosted platform or heavy SDK, it provides config driven engagement logic that runs on device. Campaigns…
- 1
- 2NO
Hello HN! The day has finally come to stop adding features and start sharing what I've been building the last 5-6 months. It's a bit of CrewAI, OpenDevon, LangFuse/Cloud all in one, providing devs who prefer TypeScript an integrated framework thats provides a lot out of the box to start experimenting and building agents with. It started after peeking at the LangChain docs a few times and never liking the example code. I began experimenting with automating a simple Jira request from the engineering team to add an index to one of our Google Spanner databases (for context I'm the…
2024 · github.com
- 3RA
Hi HN, I recently open sourced a small tool (Remuda) that I built at work to remove some of the friction of launching and managing agents and figured HN might be interested. I also wrote a post on the company blog that goes into more detail about why I built it and showcases its features: https://www.yendo.com/blog/remuda-an-agent-orchestrator
Jun 2026 · github.com
- 4OS
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
- 5TT
I use multiple AI tools for work and also my side projects, and the annoying part was to track my costs and token usage across tools. Everytime I had to visit each tool and its respective usage setting to check it and I was losing patience and also was getting hit by surprise limits Now I know that there are already free/open-source trackers for Cursor or Claude usage, and they are useful if that is all you need. My problem is broader as I wanted one small place to see tokens, spend, subscriptions and limits across the AI tools I actually use. I was really tired of switching tabs and…
Jul 2026 · lifehacksgermany.com
- 6AR
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
- 7LC
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
- 8OH
I'm Fenil, co-founder/CEO of OpenFunnel (YC F24), building this with my co-founder/CTO Aditya. We're launching OpenBenchmarks (https://openbenchmarks.com), open-source, reproducible benchmarks for SaaS APIs, starting with the category we know best: GTM APIs. ## Why we built this More and more B2B software evaluation will/already runs through reasoning models inside agentic workflows rather than through people. And buyers increasingly pick vendors that are API-first and ship MCPs, so they can wire them into internal workflows. Strong reasoning models are skeptical of…
Jul 2026 · openbenchmarks.com
- 9RT
rx is a lightweight CLI and runtime that lets you deploy any function instantly as you save it in your editor. It’s fast, simple, and takes care of setting up all your cloud infrastructure. The best dev experience with everything you need built-in: - auth - permissions - payments - secrets - storage - logs - email & SMS - and way more Related beta launch tweet: https://x.com/KhalidZoabi/status/1777673531972608249 Wanted to show it to you guys, gauge interest, and get some feedback. There's a large roadmap of upcoming stuff. Feel free to DM me on X for more information!
2024 · rx.run
- 10SA
Hi HN, I built SubTrack to help teams find unused SaaS tools and cloud resources before they silently eat into budgets. The motivation came from seeing how hard it is to answer simple questions: – Which SaaS tools are actually used? – Which cloud resources are idle? – What will our end-of-month spend look like? SubTrack connects to tools like AWS, GitHub, Vercel, and others to surface unused resources and cost signals from one place. Recently I added multi-account support, currency localization, and optional AI-based insights to help interpret usage patterns. This is an early-stage project…
Jan 2026 · subtrack.pulseguard.in
- 11
Hi HN, my name is Maria, and I’m a co-founder of Maritime. We started Maritime at MIT to build infrastructure for companies that need to run thousands of isolated AI agents for their customers. Imagine you set up an agent like OpenClaw, or a personal assistant agent with a custom framework, and want to give a separate version of it to every customer/friend. Each customer needs their own agent running in an isolated microVM, with persistent state, secrets, triggers, and sleep/wake behavior. Building such scalable and secure infra will take you months and will cost hundreds of…
18d ago · maritime.sh
- 12AO
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
- 13RA
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
- 14RU
hey all, happy to share research i've been working on for islo.dev in recent months. ever since the cheating agents (https://debugml.github.io/cheating-agents/) paper came out, revealing reward hacking was 4x more prevalent than previously estimated, i've been looking into how we can deal with the issue the common approach (taken by the tbench team) is post hoc trajectory analysis. i've been interested in the idea of reframing the problem as an endpoint security problem and tackling it via sandbox i hope you find it interesting, and thanks to the islo.dev team for…
Jun 2026 · github.com
- 15TO
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
- 16
We love Instinct, but have been increasingly worried about the data footprint we are handing over to them, and what they might do with that data. So we built an oss self-hostable version. It includes a vault that can store cards, logins, and personal information, so it can execute complex tasks on your behalf, like: "Get me two tickets to the odyssey on saturday at my nearest theatre" "Find me the best golf grip trainer and order it for me" "Read my email and find opportunities to save money by cancelling subscriptions I don't use" The tech stack: - Eve agent framework for durable agent runs…
8d ago · github.com
- 17
- 18DP
devnexus is an open-source cli that gives agents persistent shared memory across repos, sessions, and engineers. It maps out dependencies and relations at the function level, builds a code graph, and writes it into a shared Obsidian vault that every agent reads before writing code. Past decisions are also linked directly to the code they touched, so no one goes down the same dead end twice. Still building it out but I would love to hear any thoughts/feedback
Apr 2026 · github.com
- 19MO
Hi HN, I'm Jonathan. My co-founder, Thomas, and I started building Mistle in Feb. We saw larger tech companies like Ramp (Inspect) and Stripe (Minions) build this internally and thought an open source version should exist. We made a few very intentional decisions when working on this: 1. Credentials are kept out of the sandbox. Authorized access goes through a proxy, so agents do not directly receive credentials. 2. The harness is not our problem. We're not going to tackle things like memory, self-learning. 3. No magic. Configurations are explicit. You can bring your own keys for models,…
May 2026 · github.com
- 202O
Hi HN, We're the engineering team at Peakflo (B2B fintech). We built 20x internally because we kept copy-pasting Linear tickets into Claude, manually setting up branches, and babysitting agent output across terminals. Eventually we just built the infrastructure to connect task systems to agents directly — and decided to open source it. 20x is an open-source desktop app (macOS only — Linux and Windows on the roadmap) that orchestrates AI coding agents against your existing task systems. In practice: a Linear ticket gets pulled in → the triage agent assigns Claude Code + relevant skills → a…
Feb 2026 · github.com
- 21GS
This weekend I finally shipped Gryt, a project I’ve been building since 2022 — an open-source, self-hostable Discord-style app focused on reliable voice chat + text. I’m the creator. I started it after getting fed up with Discord disconnects/paywalls and wanted something self-hosted and auditable. I started on this in 2022 and had an early proof-of-concept working back then (auth + friends list), but I quickly realized WebRTC voice isn’t something you can duct-tape together. I spent a big chunk of the next couple years learning the stack (ICE/DTLS-SRTP, NAT traversal, SFU design),…
Feb 2026 · gryt.chat
- 22OA
I've been running Claude Code and Codex together every day. At some point I figured out you can use tmux to let them talk to each other, so I started doing that. Once they could coordinate, I kept adding more agents. Before long I had a whole team working together. But any time I rebooted my machine, the whole thing was gone. Not just the tabs. The way they were wired up, what each one was doing, all of it. Nothing I'd found treats your agent setup as a topology, as something with a shape you can save and bring back. So I built OpenRig, a multi-agent harness. A harness wraps a model. A "rig"…
Apr 2026 · github.com
- 23KS
KillSaaS is my answer to subscription software in the AI era. I'm building this because I believe small teams can use modern AI tools to create free alternatives to giants like Figma and DocuSign in weeks, not years. We're creating a platform where developers vote on which SaaS to replace, then build it together as open source. wdyt?
2025 · kill-saas.com
- 24OA
Hi HN, I’m Mike, the founder of OpenRig. I built this because my Claude Code + Codex setup kept forming little "topologies" of long-lived agents that worked well together, but the terminal sprawl was intense. So I built a primitive the agents could intuitively reach for to save and recreate these setups on the fly. This then led to more agent-first primitives like coordination, declarative workflow patterns, workspaces, etc. Several months in and these "rigs" I manage with openrig require a lot less babysitting and I can manage more projects at once without getting overwhelmed. The short…
May 2026 · openrig.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →