Show HN: Capn-hook for coding agents – don't grep the same mystery twice
1–8 of 8 posts
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#2[flagged]
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#3if this were localai, you could just figure out how to update the memore if the fill changes.
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#4looks cool. what is latency like? I haven't used qmd before and it looks like it runs 3 local models.
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#5if this were localai, you could just figure out how to update the memore if the fill changes.
yup, one of the reasons I built gmd to replace qmd, also that I wanted to use Typesense and incorporate llm-wiki concepts. Updating memory does depend on the nature of the change and may impact multiple memories or indexed files, and why llm-wiki concepts are needed too.
Right now, imo, the main reason to build something like this or a harness is to understand the quirks son you can evaluate production grade implementations as the space matures. We are all still very early in the curve.
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#6We use capn crunch (for cerealization)
For crypto/stock transfers we ofc use chips n dips
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#7looks cool. what is latency like? I haven't used qmd before and it looks like it runs 3 local models.
as always it depends on your hardware, the tiny models for embedding / reranking typically have low latency
qmd is focussed on local to the point of designing around single machine setups and this creates a gap where one runs agents+qmd on their laptop and LLMs on their ai box
Re: Show HN: Capn-hook for coding agents – don't grep the same mystery twice
#8if this were localai, you could just figure out how to update the memore if the fill changes.
yup, one of the reasons I built gmd to replace qmd, also that I wanted to use Typesense and incorporate llm-wiki concepts. Updating memory does depend on the nature of the change and may impact multiple memories or indexed files, and why llm-wiki concepts are needed too. Right now, imo, the main reason to build something like this or a harness is to understand the quirks son you can evaluate production grade implemen…
I build something a litle bit different check it here: https://github.com/donatienmigue/TeamBrain