Alternatives
Products that do what PeKG does
AI memory for coding agent: your knowledge, always available
- 1
- 2SG
2023 · stackoverflow.gg
- 3
- 4
- 5CS
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…
Mar 2026 · blog.mozilla.ai
- 6
- 7
- 8
- 9GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 10
AI-native coding assistant that helps developers in any IDE
Jun 2026 · polygram.dev
- 11
- 12CA
Jul 2026 · github.com
- 13
- 14
- 15
- 16IB
I've been using Claude Code heavily, and kept hitting the same issue: the agent would push changes, respond to reviews, wait for CI... but never really know when it was done. It would poll CI in loops. Miss actionable comments buried among 15 CodeRabbit suggestions. Or declare victory while threads were still unresolved. The core problem: no deterministic way for an agent to know a PR is ready to merge. So I built gtg (Good To Go). One command, one answer: $ gtg 123 OK PR #123: READY CI: success (5/5 passed) Threads: 3/3 resolved It aggregates CI status, classifies review comments…
Jan 2026 · dsifry.github.io
- 17PL
Jun 2026 · pmbai.dev
- 18SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 19SO
Feb 2026 · shareful.ai
- 20
- 21
- 22AA
Hi I am Aditi and I co-founded Potpie AI with my college mate Dhiren. We are building an open-source infrastructure to create custom agents for engineering use-cases like debugging, system design, integration testing, PR review etc. The agents are powered by a knowledge graph built on your code base to provide better context and memory, leading to better planning and execution. Currently we offer 6 ready-to-use agents but you can also build your custom agents. You can tune agent parameters like purpose, goals, background etc. and they are also empowered by pre-built tooling like code…
2024 · github.com
- 23GM
Hi HN, I'm Tony. I built Grov (https://grov.dev/) because I hit a wall with current AI coding assistants: they are "single-player." The moment I kill a terminal pane or close a chat session, the high-level reasoning and architectural decisions generated during that session are lost. If a teammate touches that same code an hour later, their agent has to re-derive everything from scratch or read many documentation files for basically any feature implemented or bug fixed. I wanted to stop writing a lot of docs for everything just to give context to my agents or have to re-explain…
Jan 2026 · github.com
- 24MC
Hi HN, I’ve been building AI agents and copilots, and kept running into a frustrating problem: they don’t fail loudly, they forget things quietly. Users re-explain preferences, agents contradict earlier responses, and context resets without any clear visibility into why. I built Memograph CLI as a debugging tool to analyze conversation transcripts and show: - what the agent forgot - where continuity broke - contradictions and repeated context - estimated token waste due to re-prompting It works locally and supports plain text or JSON transcripts. Example: $ memograph Output: Cognitive Drift…
Feb 2026
Ranked by how close each launch is in meaning, then by votes. Refine with a description →