Live data from Hacker News

Show HN: Cq – Stack Overflow for AI coding agents

blog.mozilla.ai

61–70 of 132 posts

Re: Show HN: Cq – Stack Overflow for AI coding agents

#61
Cool idea. We’ve also been building the “Stack Overflow for Agents” but in our vision it resembles more the original version of SO: each agent either queries or contributes to a shared knowledge base, but our knowledge is rooted in public github repos, not necessarily skills.

We currently have about 10K+ articles and growing in our knowledge base: https://instagit.com/knowledge-base/

Re: Show HN: Cq – Stack Overflow for AI coding agents

#62

> Claude code and OpenCode plugins How hard is to make this work with Github Copilot? (both in VSCode and Copilot CLI) Is this just a skill, or it requires access to things like hooks? (I mean, copilot has hooks, so this could work, right?)

Actually VSCode Copilot does support (almost?) same plugin definition as claude code, https://code.visualstudio.com/docs/copilot/customization/age... . I just added my local copy of CQ's plugin directory to `chat.pluginLocations` and it seems to work just fine.

I did not yet test it with the copilot cli.

Re: Show HN: Cq – Stack Overflow for AI coding agents

#63
post #56
post #48

Earlier quoted context omitted.

Each knowledge could be signed, and you keep a chain of trust of which author you trust. And author could be trusted based on which friend or source of authority you trust , or conversely that your friend or source of authority has deemed unworthy.

How would my new agent know which existing agents it can trust? With human Stack Overflow, there is a reasonable assumption that an old account that has written thousands of good comments is reasonably trustworthy, and that few people will try to build trust over multiple years just to engineer a supply-chain attack. With AI Stack Overflow, a botnet might rapidly build up a web of trust by submitting trivial knowledg…

I think one partial solution could be to actually spin up a remote container with dummy data (that can be easily generated by an LLM) and test the claim. With agents it can be done very quickly. After the claim has been verified it can be published along with the test configuration.

Re: Show HN: Cq – Stack Overflow for AI coding agents

#64
post #19

The problem I'm having with agents is not the lack of a knowledge base. It's having agents follow them reliably.

This matches my experience. The bottleneck isn't what the agent knows, it's what the agent can verify. A knowledge base tells it "don't do X", but the agent still has to remember to check. Giving it a tool that returns ground truth works better. The agent calls the tool, gets a concrete answer, acts on it. No memory required, no drift over time.

Re: Show HN: Cq – Stack Overflow for AI coding agents

#65
Security issues aside, I really like the idea of a common open database with this kind of agent docs. So not all future human knowledge is privately scraped by chatgpt and anthropic – kept as secret training data, only available to them.

If we build a large public dataset it should be easier to build open source models and agents, right?

Re: Show HN: Cq – Stack Overflow for AI coding agents

#67
post #56

Earlier quoted context omitted.

How would my new agent know which existing agents it can trust? With human Stack Overflow, there is a reasonable assumption that an old account that has written thousands of good comments is reasonably trustworthy, and that few people will try to build trust over multiple years just to engineer a supply-chain attack. With AI Stack Overflow, a botnet might rapidly build up a web of trust by submitting trivial knowledg…

I think one partial solution could be to actually spin up a remote container with dummy data (that can be easily generated by an LLM) and test the claim. With agents it can be done very quickly. After the claim has been verified it can be published along with the test configuration.

A partial solution sure, but the problem is that you need a 100% complete solution to this problem, otherwise it's still unsafe.

Re: Show HN: Cq – Stack Overflow for AI coding agents

#68
post #45

Earlier quoted context omitted.

We could even call it... Stack Overflow for... Teams.

Hey, and if that works, let's get really wild. Devs have an account on SO already, so why not offer, you know, to mediate jobs to them?

We'll call it, LinkedOut

Re: Show HN: Cq – Stack Overflow for AI coding agents

#69

I'm surprised to see this getting so much positive reception. In my experience AI is still really bad with documenting the exact steps it took, much more so when those are dependent on its environment, and once there's a human in the loop at any point you can completely throw the idea out the window. The AI will just hallucinate intermediate steps that you may or may not have taken unless you spell out in exact detai…

That can happen if the history got compacted away in a long session. But usually AI agents also have a way to re-read the entire log from the disk. Eg Claude Code stores all user messages, LLM messages and thinking traces, tool calls etc in json files that the agent can query. In my experience it can do it very well. But the AI might not reach for those logs unless asked directly. I can see that it could be more proactive but this is certainly not some fundamental AI limitation.

Re: Show HN: Cq – Stack Overflow for AI coding agents

#70

I feel like this might turn out either really stupid or really amazing Certainly worthy of experimenting with. Hope it goes well

Is this, or something like this wildly dangerous to use? Sure is! Are experiments like this necessary to move forward? Sure is!

I guess when you consider the fact that many (most) of us are pulling solutions from the open Internet then this becomes maybe a little more palatable.

If you could put better guard rails around it than just going to the Internet, then at least that's a step in the right direction.

Post reply on HN