Show HN: Active Source of Truth for Your Coding Agents

MLA watches your Claude Code and Codex sessions, captures decisions as work happens, detects stale or conflicting instructions, and steers each agent before it acts. You review only the changes that require human judgment.
4 points by anphamthanh 60 days ago meetless.ai 2 comments
Summary not yet generated for this article.

Original Text

Howdy! Happy Saturday everyone!

As a solo founder, I have always tried to maximize my speed by letting coding agents build as much as possible in parallel. However, as an engineer, I don't trust that AI will always make the right decisions and work with the right context. In the past, I always needed to click through my sessions to glance at the AI's output, try to understand what it was doing, and hopefully steer it or stop it in time.

As a result, the maximum number of concurrent sessions I could manage at once was only 4. I didn't want to be the bottleneck, so I built Meetless Agent (MLA). It basically does what I had to do manually before:

- Monitors the coding agent's tasks and actions to supply it with the correct, up-to-date context.

- Continuously reconciles running information (such as provided/tagged documentation, the agent's output, and the agent's decisions) to actively maintain the source of truth at all times.

- Keeps track of the current rules for the repo, and if an action triggers a registered rule, the rule is injected into the agent context.

My benchmarks show that running coding agents with the help of an active monitor improves quality and accuracy, consumes fewer tokens, and finishes faster: https://research.meetless.ai/stale-context/

Of course, the agent alone can't decide the source of truth; it requires human review and decisions for contradictions, etc. But for the most part, it can safely build a consistent ontology of the current source of truth.

From this, I want to build an AI layer to maintain the source of truth across the business, so I will release more connectors for Slack, Jira, Confluence, etc., soon. The goal is for this AI to assist in every part of the business. Eventually, the same coordination layer will understand that a decision made in Slack affects a Jira task, a document, an email conversation, and what a coding agent should do next without every tool becoming another isolated memory silo.

The coding agent connector is open source at: https://github.com/Meetless/mla

I am looking forward to your feedback!

Comments (2 of ) ⌛

Loading more comments... ⌛
Scroll down to load more comments
No comments available.
Type to search HN and engineering blog articles
Press Escape to close  |  ↑↓ to navigate  |  Enter to open