Cq – Stack Overflow for AI coding agents

Hi all, I'm Peter at Staff Engineer and Mozilla.ai and I want to share our idea for a standard for shared agent learning, conceptually it seemed to fit easily in my mental model as a Stack Overflow for agents.The project is trying to see if we can get agents (any agent, any model) to propose 'knowledge units' (KUs) as a standard schema based on gotchas it runs into during use, and proactively query for existing KUs in order to get insights which it can verify and confirm if they prove useful.It's currently very much a PoC with a more lofty proposal in the repo, we're trying to iterate from local use, up to team level, and ideally eventually have some kind of public commons.At the team level (see our Docker compose example) and your coding agent configured to point to the API address for the team to send KUs there instead - where they can be reviewed by a human in the loop (HITL) via a UI in the browser, before they're allowed to appear in queries by other agents in your team.We're learning a lot even from using it locally on various repos internally, not just in the kind of KUs it generates, but also from a UX perspective on trying to make it easy to get using it and approving KUs in the browser dashboard. There are bigger, complex problems to solve in the future around data privacy, governance etc. but for now we're super focussed on getting something that people can see some value from really quickly in their day-to-day.Tech stack:* Skills - markdown* Local Python MCP server (FastMCP) - managing a local SQLite knowledge store* Optional team API (FastAPI, Docker) for sharing knowledge across an org* Installs as a Claude Code plugin or OpenCode MCP server* Local-first by default; your knowledge stays on your machine unless you opt into team sync by setting the address in config* OSS (Apache 2.0 licensed)Here's an example of something which seemed straight forward, when asking Claude Code to write a GitHub action it often

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

67

out of 100

Verdict

VALIDATE

high confidence

Competition

7

competitors found, emerging market, funded players

Trend

No signal yet

A human-curated knowledge base for AI coding agents to overcome 'gotchas' and improve reliability, starting local-first for teams.

The pain

Developers struggle with AI coding agents making repetitive 'gotcha' mistakes, leading to inaccuracies, unpredictable behavior, and security concerns when sharing knowledge. This costs time and undermines trust in agent-driven development.

The gap

Existing solutions are either broad human Q&A, general model hubs, or automated agent-to-agent sharing which lacks crucial human vetting for security and trust. Cq's 'human in the loop' review of 'knowledge units' combined with a local-first/team-level approach provides a specific, trust-focused solution.

Build angle

Focus on a human-in-the-loop review process for 'knowledge units' (KUs) that captures and validates AI agent 'gotchas,' initially for specific coding agent types (e.g., GitHub action generation) within small development teams, ensuring trust and privacy by default.

Strengths

  • Addresses a significant and growing pain point in the AI agent development lifecycle (accuracy, trust, security).
  • The 'human in the loop' feature offers a strong differentiator in a crowded market.
  • Market is rapidly growing, indicating high future demand for effective AI agent solutions.
  • Clear payment signals for solutions that improve AI agent reliability and performance.
  • Initial PoC is already yielding insights, suggesting early validation.

Risks

  • Highly competitive market with several funded and direct competitors.
  • Complexity of scaling to 'any agent, any model' and managing data privacy/governance for a public commons.
  • Assumption that developers will consistently contribute and curate KUs.
  • Potential for slow adoption if integration with diverse agent ecosystems is cumbersome.
  • The scope seems larger than a typical solo-builder micro-SaaS, potentially requiring more resources.

Next steps

  1. Gather feedback from external teams using the Docker Compose example to validate the perceived value and usability of the human-in-the-loop KU review process.
  2. Conduct customer interviews to understand specific 'gotchas' and workflows for agents within target niches.
  3. Define a super narrow MVP targeting a single agent type or framework to simplify initial integration and demonstrate clear value.
  4. Explore pricing models directly with potential users to confirm willingness to pay for the human-curated knowledge base.
  5. Develop a clear roadmap for scaling from local/team to a broader ecosystem, addressing privacy and governance early.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Cq – Stack Overflow for AI coding agents”.

Open FlyBot