HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aden-hive
hive
Python2026–2026
aden-hive / hive

hive

Multi-Agent Harness for Production AI

7Distinct people
10Mentions
0Explicit recommenders
11.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Multi-Agent Harness for Production AI

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week10 dated mentions

Observed mentions: 2026-01-22 00:34:00 UTC to 2026-02-26 20:53:50 UTC. Weeks start Monday, UTC.

012342026-01-19 00:00:00 UTC to 2026-01-26 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 192026-01-26 00:00:00 UTC to 2026-02-02 00:00:00 UTC (exclusive): 4 mentions; 4 submissions, 0 comments2026-02-02 00:00:00 UTC to 2026-02-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 22026-02-09 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2026-02-16 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 23

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 192026-01-19 00:00:00 UTC2026-01-26 00:00:00 UTC110
Jan 262026-01-26 00:00:00 UTC2026-02-02 00:00:00 UTC440
Feb 22026-02-02 00:00:00 UTC2026-02-09 00:00:00 UTC101
Feb 92026-02-09 00:00:00 UTC2026-02-16 00:00:00 UTC321
Feb 162026-02-16 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC101

What Hacker News says

3 sources

Show HN: Agent framework that generates its own topology and evolves at runtime

Hi HN, I’m Vincent from Aden. We spent 4 years building ERP automation for construction (PO/invoice reconciliation). We had real enterprise customers but hit a technical wall: Chatbots aren't for real work. Accountants don't want to chat; they want the ledger reconciled while they sleep. They want services, not tools. Existing agent frameworks (LangChain, AutoGPT) failed in production - brittle, looping, and unable to handle messy data. General Computer Use (GCU) frameworks were even worse. My reflections: 1. The "Toy App" Ceiling & GCU Trap Most frameworks assume synchronous sessions. If the tab closes, state is lost. You can't fit 2 weeks of asynchronous business state into an ephemeral chat session. The GCU hype (agents "looking" at screens) is skeuomorphic. It’s slow (screenshots), expensive (tokens), and fragile (UI changes = crash).
Read the rest
It mimics human constraints rather than leveraging machine speed. Real automation should be headless. 2. Inversion of Control: OODA > DAGs Traditional DAGs are deterministic; if a step fails, the program crashes. In the AI era, the Goal is the law, not the Code. We use an OODA loop to manage stochastic behavior: - Observe: Exceptions are observations (FileNotFound = new state), not crashes. - Orient: Adjust strategy based on Memory and - Traits. - Decide: Generate new code at runtime. - Act: Execute. The topology shouldn't be hardcoded; it should emerge from the task's entropy. 3. Reliability: The "Synthetic" SLA You can't guarantee one inference ($k=1$) is correct, but you can guarantee a System of Inference ($k=n$) converges on correctness. Reliability is now a function of compute budget. By wrapping an 80% accurate model in a "Best-of-3" verification loop, we mathematically force the error rate down—trading Latency/Tokens for Certainty. 4. Biology & Psychology in Code "Hard Logic" can't solve "Soft Problems." We map cognition to architectural primitives: Homeostasis: Solving "Perseveration" (infinite loops) via a "Stress" metric. If an action fails 3x, "neuroplasticity" drops, forcing a strategy shift. Traits: Personality as a constraint. "High Conscientiousness" increases verification; "High Risk" executes DROP TABLE without asking. For the industry, we need engineers interested in the intersection of biology, psychology, and distributed systems to help us move beyond brittle scripts. It'd be great to have you roasting my codes and sharing feedback. Repo: https://github.com/adenhq/hive
107 points · Open discussion
Here's the full story behind this project: I grew up helping my dad run his factory so I'm very familiar with ERP systems for manufacturing. A few years ago, when I decided to build a startup and I indentified the biggest problems with ERP is the fact they all just serve as data integration and system of records now - there're not enough processes automation. Therefore, I thought it'd be very meaningful to leverage AI to automate business processes such as PO, Price Requisition, and invoices, etc. 3 years in, I realized that every customer in our space (construction and contracting) want process automation, however, AI is simply not good enough - it's too slow, unpredictable, inconsistent, and overall hard to count on. For example, automating a quote by asking AI to insert dynamic variables from a relational database is hit or miss. Askin
Read the rest
g voice AI to provide training does not capture full breadth of the offline activities. Asking AI to fill out a work order creates a ton of errors. Later, we decided that though LLM and the foundation models were progressing fast, the dev tools were lacking way behind, particular behind all the hypes and promises these AI applications claimed. The agents are not reliable, consistent, intelligent, evolving, and chances are the market would demand more apps to keep the party going. Therefore, we went full open-source. The mission we have in mind is really to "generate reliable agents that can run business processes autonomously". We see all this hype about general computer use (GCUs) and can't help but making an opposing argument - that the AI agents need guardrails, more defined paths, and most importantly consistent results just like a human would need - Proactive Reasoning (anticipating future needs or consequences) - Memory & Experience (events affecting himself/herself) - Judgment (based on experience) - Tools & Skills (capabilities to execute) - Reactive Adaptiveness (handling immediate roadblocks) - Contextual Communication (articulating intent and collaborating with others) - Character & Traits (consistent behavioral biases: Risk profile, Integrity, Persistence) The project seems to have gained a bit of a traction so far and I hope that you can fork it and tell the community what's missing and what we should be working on. I deeply thank you because the it's truly painful to build and deploy these one-off agents that don't get utilized. (https://github.com/adenhq/hive).
In Show HN: Open sourcing our ERP (Sold $500k contracts, 7k stars)
AdelAden·Feb 10, 2026Submission

Show HN: Open sourcing our ERP (Sold $500k contracts, 7k stars)

We recently open-sourced Hive after using it internally to support real production workflows tied to contracts totaling over $500k. Instead of manually wiring workflows or building brittle automations, Hive is designed to let developers define a goal in natural language and generate an initial agent that can execute real tasks. Today, Hive supports goal-driven agent generation, multi-agent coordination, and production-oriented execution with observability and guardrails. We are actively building toward a system that can capture failure context, evolve agent logic, and continuously improve workflows over time - that self-improving loop is still under development. Hive is intended for teams that want: - Autonomous agents running real business workflows - Multi-agent coordination - A foundation that can evolve through execution data We cur
Read the rest
rently have nearly 100 contributors across engineering, tooling, docs, and integrations. A huge portion of the framework’s capabilities - from CI improvements to agent templates - came directly from community pull requests and issue discussions. We want to highlight and thank everyone who has contributed. Specifically out top 11 contributors @vakrahul @Samir-atra @VasuBansal7576 @Aarav-shukla07 @Amdev-5 @Hundao @Antiarin @AadiSharma49 @Emart29 @srinuk9570 @levxn
32 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.