Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

41–50 of 57 posts

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

#41

Post by mubarakar95 »

Congrats on the launch. I built the Interactive TUI (Terminal User Interface) for Hive and want to clearly share the value it adds.

► What was the issue?

Hive agents were observable only through raw logs. That limited visibility into agent state, graph execution, and live interaction. Debugging required scrolling text and guessing progress while the agent ran.

► How did I fix it? I designed and implemented a full Interactive TUI dashboard in (Closed PR #2652).

The interface: A three pane terminal view that shows real time logs, a live execution graph, and an interactive ChatREPL in one screen.

The engineering: Thread safe event handling keeps the interface responsive during heavy agent workloads. Lazy widget loading reduces memory and startup cost.

Developer workflow: The goal was to streamline the "Run → Debug → Iterate" loop. Instead of reading logs after a failure, the TUI shows agent logic and tool calls in real time. The integrated REPL lets you test responses and adjust inputs in the same view where you monitor execution and performance.

► Why does it matter?

This changes Hive from a background process into a first class CLI tool. You get continuous visibility, faster debugging, and direct control during execution. It removes tool switching and improves daily productivity for engineers running agents locally or in production. Big thanks to the Aden team for testing, feedback, and support during review, which helped get this merged into core and shipped live.

Happy to explain the layout design or real time event handling if anyone wants deeper details.

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

#42

Post by ChenfengLiu »

mubarakar95 wrote: post #41

Congrats on the launch. I built the Interactive TUI (Terminal User Interface) for Hive and want to clearly share the value it adds. ► What was the issue? Hive agents were observable only through raw logs. That limited visibility into agent state, graph execution, and live interaction. Debugging required scrolling text and guessing progress while the agent ran. ► How did I fix it? I designed and implemented a full Int…

That TUI was clean, very much appreciated!

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

#43

Post by AdelAden »

krrish123456789 wrote: post #7

What was the issue? While Hive provides a powerful backend for autonomous agents, execution was a "black box." Debugging complex agent workflows—like when a scraper hits a 403 and needs to rotate proxies—was painful through terminal logs. There was no easy way to visualize the decision-making process, track token usage, or monitor costs in real-time. How did you fix it? I built the Web Dashboard (hive/web) using Next…

The shift from 'black box' logs to a visual timeline is a huge step toward production reliability. For the decision tracing specifically—how are you handling the data serialization between the local runtime and the Next.js dashboard to keep latency low? I am curious if we can eventually use those 'Self-Healing' event logs to automatically tune our agent guardrails

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

#45

Post by Suhas_08 »

Congrats on open-sourcing — the direction toward reliable agents really resonates.

One thing that stood out while contributing is how critical durability becomes once agents move from demos to long-running production workflows. Mutation loops, retries, or multi-step plans can be token-heavy and fragile if a process crashes midway.

I recently worked on adding optional crash-safe runtime state persistence (atomic temp+replace logic with restore on restart) so agents can resume from the last completed step instead of starting over. It’s fully opt-in, but feels like an important primitive as you build toward self-improving systems.

Excited to see where Hive goes — happy to help more on reliability and production hardening.

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

#46

Post by antiarin »

Congrats on the launch! I'm Aaryann Chandola (Antiarin on github), been contributing to Hive for the past couple of weeks. Most of my work has been on the integration side. I built the Google Calendar integration, its an MCP tool suite that lets agents create, update, delete and search calendar events, including Meet links. The idea is you can have an agent that actually manages your schedule for you. I also put together the email integration for Gmail and Outlook along similar lines. One thing that bugged me early on was that the LLM agents had zero awareness of what day or time it was, so they'd just make up dates. I added runtime Datetime injection into the system prompts which was a small fix but made a noticeable difference. I've also been involved in some of the design discussions with the core team. Proposed centralising the hardcoded prompts scattered across the framework into a proper registry, wrote an RFC for closed-loop agent evolution (basically agents learning from their own runs), and contributed to the conversation around cron-style scheduled execution. Working on Codex integration as a coding agent right now.

Honestly what got me interested in Hive in the first place is the goal-driven architecture. Agents aren't just chains of LLM calls, they have explicit goals with success criteria that get evaluated. The graph-based execution with pause/resume and checkpointing makes it feel like a real runtime managing concurrent execution streams, not just a script runner.

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

#50

Post by aiyeolaesther8 »

lfmosquera95 wrote: post #6

Hi everyone, What was the issue? While exploring Hive for real-world finance use cases, I noticed there wasn’t a clear, reusable structure for implementing credit-risk logic inside agents. This made experimentation harder and limited how easily risk-related workflows could scale across agents. How did I fix it? I contributed by working on a credit-risk–focused agent/module, improving the structure, documentation, and…

Also interested in learning about you did this please
Post reply on HN