Alternatives
Products that do what Closed Rings – A CLI-first time tracker for developers does
Hi, HN. I built Closed Rings. A developer-friendly, AI-agent-first time tracker that integrates with my workflow. I wanted something that lives in my terminal and my coding agent. You can run `rings start "OAuth 2.0" -m "Start integrating OAuth 2.0"` when you start a new task and `rings close` when you're done with your current work. In between, it tracks context switches. You get a stand-up-ready summary, a focus report (longest focus block, number of context switches, time per project), and an export grouped by project or day. You can also ask your AI agent: _Start tracking "OAuth 2.0"._…
- 1
- 2
- 3
- 4
- 5IB
TLDR; I built a tool that turns any API into a CLI designed for ai agents --- Got tired of dealing with bloated context windows from MCP servers and skills that stuff entire API docs into the agent's context CLIs fix this, agents run a single command to self-discover everything an API has to offer So, built a tool to generate them for any api. All CLIs are written in Go, fast and lightweight, no dependencies Help text (via the --help flag) is the killer feature: all context for each command/endpoint/parameter is extracted directly from the user-facing API docs and enhanced with…
Mar 2026 · instantcli.com
- 6
Zero-config hosting to launch specialized AI teams instantly
Feb 2026
- 7
- 8OS
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
- 9TO
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
- 10DC
Hi HN I recently published docs-cli to pypi. I created this tool because I noticed that my docs kept getting out of sync: I've been using markdown to track the project's implementation and progress, and it became really hard to keep track of everything. This is a simple tool for your agents to ensure that links and indexes are kept fresh. I included the agent-playbook-suite marketplace since this is how I use it. The docs repo was actually built also using it, so dogfooding since day one :) The Agent Playbook Suite includes everything needed to create a project from start to finish. Linked…
May 2026 · artrichards.github.io
- 11TC
Agents can run non-interactive commands, but they often fail once a workflow needs a real terminal (SSH sessions, installers, debuggers, REPLs, TUIs). I built term-cli so an agent can drive an interactive terminal session (keystrokes in, output out, wait for prompts). And it comes with agent skill for easy integration. It supports in-band file transfer: the agent can move files through the terminal stream itself (same channel as the interactive session), which is useful when the agent doesn’t have scp/sftp, shared volumes, or direct filesystem access across boundaries. Recent example:…
Mar 2026 · github.com
- 12KD
Every AI agent that does something useful - opening a PR, posting in Slack, updating a ticket - needs to call an API on behalf of a user. That means OAuth. Authorization flows, token storage, refresh logic, per-user credential isolation. Today, most teams solve this with a long-lived API key in an .env file, shared across every user and every session. As everyone in an organization becomes a software engineer - whether they know it or not - you can't expect each of them to roll their own OAuth. Secure credential handling needs to be baked into the infrastructure. The core issue: agents are a…
Mar 2026 · kontext.dev
- 13CA
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
- 14RA
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
- 15AS
Hi, this is my first npm package that is getting a couple of hundreds downloads. It's a super simple CLI time tracker, mostly suitable for 9 to 5 jobs I hope you check it out and tell me what you think. Demo and etc. https://github.com/omidfi/moro
2017
- 16PO
Hi HN, We are excited to share patchwork - an open-source CLI for dev chore automation that you can use with your LLM of choice. Dev Teams can orchestrate custom workflows (called ‘patchflows’) using a combination of reusable steps and prompt templates to fix vulnerabilities, upgrade breaking dependencies, generate documentation, and more. We built scanning tools in the past, and saw how overwhelmed developers get with their DevSecOps pipelines. LLMs have the potential to help - but there is a need for an 'outer-loop' solution that can be customized to accommodate the processes, priorities,…
2024 · github.com
- 17OA
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…
Mar 2026 · github.com
- 18TA
Hi everyone! I built this because I wanted a little bit more organization around my Claude sessions, worktrees and plans while staying in the terminal and not relying on another SaaS tool. Since it's a command line tool, the added bonus is that Claude can use `td` directly. The td calendar was just a fun add-on but the Claude session stats have been pretty interesting! Let me know what you think!
Apr 2026 · github.com
- 19DP
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
- 20DA
I've been running Claude agents for various automation tasks — monitoring crypto news, syncing Todoist, running health checks — and I kept hitting the same problem: there's no clean way to deploy an agent that just runs on a schedule without a human babysitting it. Every agent framework I looked at was built around chat interfaces or one-shot workflows. I wanted something closer to cron for AI agents — define a task, give it a schedule, let it run forever. So I built Ductwork. You define tasks as simple JSON files — a prompt, a schedule, optional memory and skills — and ductwork handles…
Mar 2026 · github.com
- 21BC
I've been building a cli for my homelab/self-hosted setup. The original motivation was getting tired of stitching together deployments, monitoring, remote SSH access and random scripts. It’s a open source CLI, all-in-one tool for monitoring, secure remote accces (tunnel and terminal), log forwarding, automated deployments. No exposed ports, or endpoint, everything is configurable how the user wants it. One use case that multiple friends are interested in is replacing HomeAssistant’s Nabu Casa subscription with tunneling through BeaconInfra. The cloud/control-plane part…
May 2026 · github.com
- 22
- 23AL
AGENTS.lock keeps AI agent skills, instructions, and MCP servers in sync across Claude, Codex, Gemini, and Copilot CLIs using a single TOML lockfile as the source of truth. Instead of manually copying skills and configs between tools, you declare everything once in AGENTS.lock and run `al sync`. GitHub: https://github.com/luml-ai/AGENTS.lock
Jan 2026 · github.com
- 24NT
I built a CLI tool that turns codebases and PRs into diagrams so you can quickly understand how things fit together. Originally made it because I couldn't follow my own AI-generated repos. Just shipped a big update: - Switched from D2 to Mermaid for rendering - Tree-sitter AST parsing + agentic flow instead of raw LLM calls. ~50x faster. - Works on any GitHub repo or PR, not just local - Dropped the web frontend, it's just a CLI now - Published as a pip package Still a ton to improve and I'm building fast. Feedback, issues, PRs all welcome.
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →