Alternatives
Products that do what Lichen – Manage and create code licenses on the CLI and with TOML does
Hey! I'm Miles, I built this tool to be a fast and reliable solution for generating licenses on the CLI. Licensing has always been a point of stress for me, with how much is at stake. If I copy one from the wrong website, the version I download is the wrong one, or any number of mishaps, my whole code is at risk. We see this fiasco play out all the time. We shake our saddened heads and go on. No longer! Lichen is designed to generate licenses sensibly with three words on the CLI. `lic gen MIT`. Or in a `.lichen.toml` in your project root. Add authors/maintainers with --authors, date it…
- 1KA
2017 · keygen.sh
- 2
- 3LA
2018 · github.com
- 4LS
Hey HN, Lich is a worktree aware local dev stack orchestrator. Simply put, it allows you to run multiple copies of your development stack from different worktrees with different code in parallel without going insane. I built Lich because I’ve found myself increasingly using multiple parallel coding agents for development work. I wanted my coding agents to each have independent copies of my development stack to be able to test and validate their own work well. I found that trying to do this totally broke the way I have normally setup tooling for local development. Ports conflict, the UI from…
Jun 2026 · github.com
- 5IM
Hey HN, A few months ago I realized licensing my app wasn't as straightforward as I expected. There was too much setup just to create a license, and the customer experience was not great. All I wanted was for licenses to be generated automatically when I got paid, and for customers to manage their own licenses. So I built Keyforge, a simple software licensing platform for developers. It integrates with Stripe so that licenses are created automatically when someone purchases or subscribes to your product. There's also a self-serve customer portal where users can manage their licenses,…
2025 · keyforge.dev
- 6PL
Hi, I’ve been exploring Claude 3.5 code generation abilities for a while and it looks like it can generate more consistent code than other models. However it would still be unmaintainable if you ask it to write a lot of code and it still sucks at system design. So, I’ve been playing around the idea of using the code repository with a template for directory layout and infrastructure, then adding the repository information to Claude and asking it to generate code. It seems that it works, if I pass the structure of some OpenAPI based backend it can update the API definition and implementation…
2024 · github.com
- 7NT
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
- 8LA
Hello HN, I am building a devtool to understand existing codebases. The idea originates from my time at big tech as well as various attempts to get involved in open source projects. When I was in college I wanted to improve my coding skills by contributing to opensource projects. I would pickup a bug or feature request but I always found myself stuck at the very first step. I did not understood where and how to begin contributing. I once submitted a patch in firefox which was labeled "Good first issue" but that was still very handheld. The assigner told me exactly which files I need to…
2024 · lucidcode.ai
- 9CG
clify is a Claude Code plugin. Give it an API documentation URL and it generates a complete CLI repo: commands for every endpoint, smoke tests, zero npm dependencies. Try it inside Claude Code: 1. /plugin marketplace add derrickko/clify 2. /plugin install clify@derrickko-clify 3. Run /clify You'll have a working CLI in about 10 minutes. I was building agents to manage ad campaigns. Meta's Marketing API has no CLI, and no MCP server either. So I wrote one by hand. It worked, but then I looked at the next API I needed and realized the same problem is everywhere: tons of…
Apr 2026 · github.com
- 10IB
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
- 11OS
I’ve been working on Code2Docs, an open-source CLI tool that helps developers automatically generate inline documentation (docstrings + comments) for Python code using AI. It’s built to solve a common problem I’ve faced (and seen often in teams): We code by "vibe" — fast iterations, minimal docs, and then forget what the logic was months later. Code2Docs helps bridge that gap by documenting as you go — without breaking your flow. Right now it supports function-level documentation. Planned features include: - README.md generation for projects - API endpoint docs - Database schema…
2025 · code2docs-open-source.netlify.app
- 12UA
I've been using LLMs for long discovery and research chats (papers, repos, best practices), then distilling that into phased markdown (build plan + tests), then handing those phases to Codex/Claude to implement and test phase by phase. The annoying part was always the distillation and keeping docs and architecture current, so I built Unpack: a lightweight GitHub template plus docs structure and a few commands that turns conversations into phases/specs and keeps project docs up to date as the agent builds. It can also generate Mintlify-friendly end-user docs. There are other…
Feb 2026 · github.com
- 13LQ
Hi HN, I built LucidShark: a local-first, open-source CLI tool that acts as a quality & security pipeline. It can be used to increase the confidence in AI-generated (or AI-assisted) code. - Config lives as code in version-controlled lucidshark.yml - 100% local; no cloud, no SaaS - Runs 10 quality domains automatically: linting, formatting, type checking, SAST/security scanning, SCA/dependency checks, IaC validation, container scanning, unit tests, coverage thresholds, code duplication, etc. - Produces a QUALITY.md dashboard with health scores (e.g. 9.1/10), trends, and issue…
Mar 2026 · lucidshark.com
- 14IB
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
- 15JU
Author here. Got tired of checking Upwork, NoFluffJobs, eFinancialCareers, LinkedIn and HN threads separately, so I built a CLI that scrapes them into a local SQLite DB and lets me browse everything in one web UI with filters and semantic search. Details: - Scraping via real browser over CDP (your own logged-in session, no API keys) - Embeddings run locally (nomic-embed-text via fastembed), stored in Lance - Rust backend, SolidJS frontend embedded in binary, single static executable Works for my use case (Europe-based contractor). It's my first rust project, decided to do local CLI, it's…
Jul 2026 · github.com
- 16LS
2015 · github.com
- 17AC
This week we released the Kodus CLI. It took a bit longer than we expected to ship. The reason was simple: there are already many ways to run reviews locally today. IDEs, extensions, terminal commands, agents inside the editor. So building “just another AI CLI” didn’t seem like a good idea. The question that guided the project was different: how can we bring the quality of PR reviews to the moment when the code is still being written? Today the CLI does two main things. The first is running local reviews using the same context we use in PRs. The goal was to avoid that shallow review that…
Mar 2026 · github.com
- 18DC
2019 · demo-cli.dev
- 19AR
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
- 20OO
One coding agent orchestrator UI for Claude and Codex, but actually feels nice. Free, open-source, MIT licensed. Why I built it: - I wanted a lightweight UI as nice as the Codex app, but without the complexity and the custom diffs on the side - I want files and diffs open straight in my editor! - And I wanted both agents - Anthropic + OpenAI — in one place How it works: - No API keys, no OAuth, no separate billing — it just uses whatever you're already logged into. So your Claude Max and ChatGPT/Codex subscriptions both work out of the box. - Talks to Claude Code via the Claude Agent…
Apr 2026 · github.com
- 21MC
Hello, for the past couple of months, we've been developing Mify and I wanted to share it with the people here. We've been writing backends for multiple different big and small companies and noticed that backend development progresses in way too similar cycles. At first people write a small set of services or in better case a single service to do what's needed. At some point the tech debt becomes too much of a hassle to handle as company grows, engineers are starting to scale the codebase, rewriting code, splitting monolith, introducing microservices and eventually after a bunch of…
2023 · github.com
- 22KY
Hey HN! I wanted to practice "vibe coding" and see how far and fast I can go by only prompting, without actual coding. I decided to make a simple CLI app that scrapes web docs into a single md file (I was annoyed that LLM keeps writing Tailwind 3 code for a Tailwind 4 project). In just a couple of hours, the CLI app was ready! Then iterated on arguments for another couple of hours. Result: https://github.com/vladstudio/web2llm Then I decided to go further and "productize" the CLI by making a web app for it. Another half-day, and the web app is ready!…
2025 · web2llm.dev
- 23DM
I have been coding over four decades, in many languages, on many projects (including Firefox, Final Cut Pro, the Newton, and Fullwrite Professional if you can remember that far back; all these using my "dead-name"). I wrote something small and simple to scratch an itch. It's the UNIX philosophy: small "one-trick ponies", each *really* good at their one trick, then the user can hook them together to solve actual problems. I'm a CLI guy, and for almost everything, I already have this. But not for debugging. The itch I scratched was the connector that enables this philosophy for debugging. That…
Jun 2026
- 24AO
Hi It's Logan (op) and David, we are launching our first open source Python SDK generator with other languages to come :) We built this because we believe that the OpenAPI Generator project is a mess and simply doesn't work for most users (us included). Additionally, proprietary generators miss the mark for complex use cases, and restrict developers from doing what they do best: writing code. On top of all that they force you into proprietary configuration layers for many desirable features which increases vendor lock in and pulls you further away from your API spec as the source of truth.…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →