Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Vectorized and performance-portable Quicksort(googleblog.com ↗)
    17comments
  2. Training a 4B model to produce 81% faster query plans than Postgres(rohanbansal.com ↗)
    5comments
  3. Small programming tricks(will-keleher.com ↗)
    121comments
  4. Accurate Models of AMD Matrix Cores(arxiv.org ↗)
    discuss
  5. Dream-RSI: Recursive Self-Improvement through Evolving Worlds(arxiv.org ↗)
    44comments
  6. Fed hikes rates as inflation worries push up bond yields(reuters.com ↗)
    12comments
  7. Mistral X Mozilla: Private, Multilingual AI Browsing(mistral.ai ↗)
    164comments
  8. Tell the speakers that you liked their talks(ohhelloana.blog ↗)
    51comments
  9. Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations(github.com/arnegiacomo ↗)
    229comments
  10. Learning Programming in an Age of LLMs(ploeh.dk ↗)
    149comments
  11. How big are factorials?(thegreenplace.net ↗)
    23comments
  12. The Siberian Ice Maiden and the Scythian World(patrickwyman.substack.com ↗)
    discuss
  13. ER visits for gambling disorders doubled after expanded online gambling market(utoronto.ca ↗)
    75comments
  14. Claude Cowork and chat are now one Claude(claude.com ↗)
    163comments
  15. The DeepMind Institute(deepmind.com ↗)
    23comments
  16. A coffee shop owner used AI to make a menu poster. Then came the angry DMs(businessinsider.com ↗)
    8comments
  17. Hackers Got Inside a Flock Camera(wired.com ↗)
    179comments
  18. The Google Play app review process now regularly takes longer than a week(gultsch.social ↗)
    292comments
  19. How good are frontier models at physics?(arxiv.org ↗)
    2comments
  20. GitHub is having trouble counting things(chuckgreenman.com ↗)
    29comments
  21. Can we stop with the uptime percentages?(jim-nielsen.com ↗)
    82comments
  22. Kyber (YC W23) Is Hiring a Forward Deployed Engineer(ycombinator.com ↗)
    discuss
  23. Why a fast-growing German AI startup is moving its parent company from the US(euronews.com ↗)
    2comments
  24. Show HN: How Stale Is Your AI? Release age and training cutoff for 20 models(stale.jock.pl ↗)
    39comments
  25. Salesforce Global Outage(salesforce.com ↗)
    149comments
  26. This Code Is CRAP (2011)(googleblog.com ↗)
    45comments
  27. Anatomy of a Texture(agentlien.github.io ↗)
    9comments
  28. Show HN: I made a flight simulator, except you're just a passenger(inflightsimulator.com ↗)
    197comments
  29. A warning about 'model welfare'(mustafa-suleyman.ai ↗)
    297comments
  30. Scaling Golang CI by Replacing actions/setup-go(cloudx.ai ↗)
    16comments

Show HN: Friday – Self-hosted persistent memory for AI coding agents (MCP)

6 pointsby 56m agogithub.com
1 comments
20m agoHN ↗

While the idea of improving codebase search and documentation has some merit, any modern coding agent harness does not have the problem of starting each session blankly and giving generic advice. The actual issue that I have experienced is that it will waste tokens re-reading the codebase over and over again to understand your query, although you can mitigate that by proper use of AGENTS.md and documentation.

But more importantly, is it too much effort to write the readme yourself? Or at least to ask the AI to rewrite it so that it doesn't have all the tell-tale signs of AI slop?