Alternatives
Products that do what Tokyo does
Open-source framework for building agent-friendly CLIs
- 1NO
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
- 2

- 3

- 4IB
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
- 5

- 6
- 7

- 8

- 9

- 10

- 11

- 12

- 13

The open-source AI workstation for coding, ops, and life
Apr 2026
- 14

- 15

- 16

- 17

- 18VP
Hi HN, I built VAEN (an open source CLI) because I kept running into a boring problem with AI coding-agent workflows: the setup becomes useful, but then it is hard to move. A good, useful agentic harness consists of more than just instructions: skills, mcp servers and more. There should be a better way to share those than just .MD files, and that is why I created VAEN. What works: create a yaml, run the CLI commands as per the repo, and get a .agent file that you can share and extract. Think of how awesome it could be if anyone could use a very useful agentic harness, and share it with one…
May 2026 · github.com
- 191D
We just open-sourced the internal system we built at Assembled for running coding agents as a team. Coding agents worked well for individual engineers, but the surrounding workflow was a bit of a mess. We generally found that many engineers had different MCP connections and context for their agents, personal automations running that other people couldn’t access, and very little introspection for what a human’s input into the coding agent looked like. So we built an internal system that converted coding agents into shared team infrastructure. The system runs Codex, Claude Code, OpenCode, and…
Jun 2026
- 20RA
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
- 21

Open-source 2D IDE for managing AI agents in native CLIs, terminal, gits, beads issues, and files across multiple projects and machines. Self-host on a single machine via localhost OR host on a cluster via Tailscale OR connect to app.49agents.com (coming soon) - alpbahadur/49-IDE
6d ago · github.com
- 22WB
Hi HN, I'm one of the creators of Nanobrowser, an open-source Chrome extension that lets you automate web tasks using AI agents. We were inspired by the potential of tools like OpenAI's Operator, but we wanted something that was: -Open-Source:You can see the code, modify it, and contribute to the project. -Browser-Based:No complex setups or server deployments. It runs directly in your browser. -Customizable:You can tailor the agent's behavior to your specific needs. -BYO LLM:Bring your own large language model API key (OpenAI, Anthropic,or even local models), No vendor lock-in. -Privacy…
2025 · github.com
- 23

- 24UA
Three months ago, we started developing an open source agent framework. We previously tried existing frameworks in our enterprise product but faced challenges in certain areas. Problems we experienced: * We risked our stateless architecture when we wanted to add an agented feature to our existing system. Current frameworks lack server-client architecture, requiring significant effort to maintain statelessness when adding an agent framework to your application. * Scaling problem - needed to write Docker configurations as existing frameworks lack official Docker support. Each agent in my…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →