Alternatives
Products that do what legacy-use – add REST APIs to legacy software with computer-use does
Hello HN! Sebastian here from Schub. We just open-sourced a new project I've been working on, called legacy-use, and I’d love to get your thoughts. At Schub, we’ve been building agents that automate legacy Windows software (healthcare systems, finance tools, EHRs), the kind of stuff that’s mission-critical but hasn’t changed since Windows XP. These apps have zero APIs and usually require humans clicking around all day. So we built legacy-use, an agentic API layer for any desktop app. Well, technically any software. Legacy-use lets AI agents control GUI-based software by emulating mouse and…
- 1
- 2
- 3
- 4IW
Hey HN, I made Browser-Use, an open-source tool that lets (all Langchain supported) LLMs execute tasks directly in the browser just with function calling. It allows you to build agents that interact with web elements using natural language prompts. We created a layer that simplifies website interaction for LLMs by extracting xPaths and interactive elements like buttons and input fields (and other fancy things). This enables you to design custom web automation and scraping functions without manual inspection through DevTools. Hasn't this been done a lot of times? Good question, as a general…
2024 · github.com
- 5AD
I've been building computer-use tools for a while, and I quietly launched this about a month ago (122 Stars on GH). I figured it was worth sharing here. Over the last few months, a lot of computer-use agents have come out: Codex, Claude Code, CUA, and others. Most of them seem to work roughly like this: 1. Take a screenshot 2. Have the model predict pixel coordinates 3. Click x,y 4. Take another screenshot 5. Repeat That works, but it's slow, expensive in tokens, and fragile. If the UI shifts a few pixels, things break. And the model still doesn't know what any element actually is. But the…
May 2026 · github.com
- 6
- 7
- 8
- 9OS
This started off as a project to understand how to get LLMs to interface with more traditional desktop softwares. We were especially interested in tools related to schematic drafting and molecular simulation. Decided to explore COM automation for more traditional Windows softwares as a starting point! Been using it to help some friends automate simple excel workflows. Thought we'd share!
2025 · github.com
- 10MM
Hi HN! Erik here from Pig.dev, and today I'd like to share a new project we've just open sourced: Muscle Mem is an SDK that records your agent's tool-calling patterns as it solves tasks, and will deterministically replay those learned trajectories whenever the task is encountered again, falling back to agent mode if edge cases are detected. Like a JIT compiler, for behaviors. At Pig, we built computer-use agents for automating legacy Windows applications (healthcare, lending, manufacturing, etc). A recurring theme we ran into was that businesses already had RPA (pure-software scripts), and…
2025 · github.com
- 11
- 12
- 13
- 14
- 15
- 16
- 17RE
Hey HN! We built a browser-based agent that runs inside an authenticated web app, watches how the app calls its own APIs, and automatically turns those into agent tools. You can think of it as an auto-generated MCP server that self-updates as the host app changes. The result is a skilled AI assistant that actually integrates deeply with any product (not just chat and RAG) with minimal effort. Check out these short demos below that show the agent in software you're probably familiar with: - Jira: https://demo.frigade.com/hn?skill=jira - Spotify:…
Jul 2026
- 18
- 19
- 20TU
Apr 2026 · github.com
- 21FU
I'm Dan, and I built a CLI that lets AI agents design in Figma. What it does: 100 commands to create shapes, text, frames, components, modify styles, export assets. JSX importing that's ~100x faster than any plugin API import. Works with any LLM coding assistant. Why I built it: The official Figma MCP server can only read files. I wanted AI to actually design — create buttons, build layouts, generate entire component systems. Existing solutions were either read-only or required verbose JSON schemas that burn through tokens. Demo (45 sec): https://youtu.be/9eSYVZRle7o Tech…
Jan 2026 · github.com
- 22CO
We recently started to use agents to update some documentation across our codebase on a weekly basis, and everything quickly turned into cron jobs, logs, and terminal output. it worked, but was hard to tell what agents were doing, why something failed, or whether a workflow was actually progressing. We thought it would be more interesting to treat agents as long-lived workers with state and responsibilities and explicit handoffs. Something you can actually see and reason about, instead of just tailing logs. So we built Clawe, a small coordination layer on top of OpenClaw that lets agent…
Feb 2026 · github.com
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →