hackernews

Show HN: Active Source of Truth for Your Coding Agents. 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!


Hire4Real – free index of 11M US labor filings, open-source (MIT).


Show HN: Faber, cost-efficient open-source coding agent that uses code graph.


Arcadedb – Open-Source Multi-Model Graph Database.


Show HN: TechSkills – Open-source skill modules for AI coding agents.


Microfolio – open-source static portfolio generator for creatives.


Ask HN: If you dislike AI, why don't you prove it?. I've seen so many people who absolutely hate AI, and want AI companies to fail, but then 2 seconds later, open up the coding tool made by frontier labs and willingly hand them money.
Just recently convinced one of them to move away from the frontier lab lock-in to OpenCode and switch between models. Not saying they need to switch to non-frontier models immediately, but this approach lets them easily switch to open source when the time is right.
Why don't more people do this? And shouldn't companies that use AI heavily also suggest this approach?
To be clear, I like AI, and use it all the time, but I use it in a way that allows me to easily switch models and not get locked-in.


Show HN: Knowl – CLAUDE.md hit 1000 lines, so I built memory that prunes itself. Using AI agents is amazing, but in long-term, I started to have more and more problems about the context of them. They keep forgetting what we are working on, opening a new chat session clears all their context, my CLAUDE.md had like 1000 lines.
So I thought to install those agent memory that are on the market. Started out great, but I noticed that those memory only append and does not fix what is stale. First day I told it to use Lemon Squeezy as our MoR but second day I tell it to change to Polar. But when I ask it again, they keeps returning both answers or cannot decide which we are using.
That's why I created Knowl. Knowl solves the problem with freshness of the knowledge. It split the knowledge into small data bits called "atom". Atoms can be of the following types: fact, decision, goal, constraint, architecture, state, skill so we can retrive atoms in categories.
When conflict happens at write-time (a new atom conflicts with an old one), Knowl retires the old one (flag it with superseded) and remove it out of main retrieval but still keeps full history.
There are many more cool features like transcript search, multi-workspace sharing, change detection impact... and Knowl Cloud for team-sync too.
We benchmarked Knowl on MemoryAgentBench - FactConsolidation single-hop @262K context and got suprising result:
- Knowl: 0.90 <- I ran this
- agentmemory: 0.79 <- and this
- Gpt-4o (full context): 0.60
- Mem0: 0.18
- Zep: 0.07
In multi-hop we scored 0.07 (ceiling of all time is 0.14)
I ran at temperature 0.7. You can find full benchmark in my repo.
This is fully open-source, connect to almost every providers through MCP (Claude Code, Codex, Cursor, Antigravity...). And it is fully local (unless you use Knowl Cloud).
I'd love to get some feedback. Cheers!


Show HN: hlquery, An open-source C++20 search engine.


Open sourcing MonsterWriter, piece by piece.


What's the best open source Wispr alternative?. Please share, I'm on iOS and feel like the in-house speech-to-text is disappointing, to say the least.


Continue coding agent is dead. Alternatives?. It was nice to use on vscode with offline Ollama but today notices it is not updated anymore. So, alternatives you use?
From github:
"Note: The continuedev/continue repository is no longer actively maintained and is read-only for all users."
From continue.dev:
"Continue has joined Cursor
Continue was acquired by Cursor. Our mission was always to ensure developers are amplified, not automated, and that commitment carries on in the work ahead.
It was an honor to build with the Continue community. Thank you to each and every one of you who helped us create a pioneering open-source coding agent.
What we built together pushed the boundaries of what AI developer tooling could be, and our open-source codebase remains freely available as a foundation for others."


CyberStrike – open-source AI harness for offensive security (AGPL).


I built an open-source FACEIT stats Browser Source for OBS.


Open-source field operations system for construction.