nowfound

Alternatives

Products that do what Angy does

Multi‑agent pipelines w/ AI‑driven scheduling + safety check

  1. 1

    Tag any agent, wherever work happens.

    28d ago · agentconnect.md

  2. 2
    Anvil175

    Run a fleet of parallel Claude Codes

    Mar 2026

  3. 3

    Pre-built agent harness on managed infrastructure

    Apr 2026

  4. 4

    One dashboard to run and organize multiple AI CLI agents

    Dec 2025

  5. 5

    Use Claude Code, Codex, and Gemini in parallel

    Mar 2026

  6. 6

    One workspace for Claude, Codex, Gemini and your stack

    May 2026

  7. 7
    Ango Hub118

    All-in-one data labeling platform for AI teams of all sizes

    2022

  8. 8

    An LLM framework for large scale code migrations

    2025

  9. 9
    Flare120

    The graph-first IDE and interactive map for agentic coding

    12d ago · github.com

  10. 10
    Firstwork139

    Agentic AI for frontline hiring and onboarding

    May 2026

  11. 11

    Your AI agents team, terminals, notes: one infinite canvas

    Jul 2026

  12. 12
    Agenty94

    Scraping, textract, ocr, sentiment analysis agents on cloud.

    2019

  13. 13
    RouKey98

    Route each task to the smartest AI for the job

    2025

  14. 14

    Run multiple AI coding agents at once, in one grid

    4d ago · panecrew.dev

  15. 15HA

    Hi HN, I am Umer. I recently built an experimental framework called HyperFlow to explore the idea of self-improving AI agents. Usually, when an agent fails a task, we developers step in to manually tweak the prompt or adjust the code logic. I wanted to see if an agent could automate its own improvement loop. Built on LangChain and LangGraph, HyperFlow uses two agents: - A TaskAgent that solves the domain problem. - A MetaAgent that acts as the improver. The MetaAgent looks at the TaskAgent's evaluation logs, rewrites the underlying Python code, tools, and prompt files, and then tests the new…

    Apr 2026

  16. 16SR

    Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…

    Jul 2026 · shikigami.dev

  17. 17CA

    I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!

    Sep 2025 · infrastructureas.ai

  18. 18AC

    Hi everyone, I've been working on a CLI tool that can help to easily run any model in claude, Codex, Gemini, Pi, and OpenCode. It's also an API keys manager, supports multiple providers or OpenAI/Claude/Gemini accounts. You can add openrouter, poe, Vercel AI gateways etc. It has a built-in provider that is free to all, which is using Deepseek-V4, no login or API key required, add your own when you're ready. After installation you can try claude instantly (No config, no login): aivo claude Hope it's useful to someone.

    Apr 2026 · getaivo.dev

  19. 19DA

    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

  20. 20IB

    Hey HN. I built an AI agent harness over the past few months and I'm open sourcing it today. Some context on why. I've been building with Claude Code daily using this harness. It orchestrates multiple AI agents as a team, with a dashboard, chat, kanban board, the works. I used it to build a full SaaS product (MyUpMonitor, https://myupmonitor.com) in about 24 hours of focused coding. Then yesterday Anthropic announced Mythos and decided to keep it behind closed doors. Meanwhile I'm paying for Claude and I can't access their best model. I don't think that is nice at all... So I'm…

    Apr 2026 · github.com

  21. 21IM

    Every time I wanted to use LLMs in my existing pipelines the integration was very bloated, complex, and too slow. This is why I created a lightweight library that works just like scikit-learn, the flow generally follows a pipeline-like structure where you “fit” (learn) a skill from sample data or an instruction set, then “predict” (apply the skill) to new data, returning structured results. High-Level Concept Flow Your Data --> Load Skill / Learn Skill --> Create Tasks --> Run Tasks --> Structured Results --> Downstream Steps And the bast part: Every step can be saved and reused as…

    2025 · github.com

  22. 22RA

    Hi HN folks, I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory. This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future? I do not think so. Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs…

    Mar 2026 · github.com

  23. 232O

    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

  24. 24PO

    Pitaya is a local, open-source orchestrator for AI coding agents (Claude Code, Codex CLI). It runs many agents in parallel, isolates each in Docker with its own git branch, supports pluggable Python strategies, and persists state so runs are resumable. Quickstart + short demo are in the README.

    2025 · github.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →