Live data from Hacker News

Viewing profile — mvyshnyvetska

mvyshnyvetska

HN member
Joined
Wed, Aug 07, 2024, 7:59 AM UTC
HN karma
2
Public activity
10 items

About mvyshnyvetska

No profile information was provided.

Recent public activity

  1. comment
  2. story
    Show HN: Breathe-Memory – Associative memory injection for LLMs (not RAG)

    LLMs forget. The standard fix is RAG — retrieve chunks, stuff them in. It works until it doesn't: irrelevant chunks waste tokens, summaries lose structure, and nothing actually mod…

  3. comment
    Comment #46792234

    Yeah, that's more process-tooling territory — keeping this dev-focused for now.

  4. comment
    Comment #46782806

    Update: just shipped --brief flag. Thanks for the push!

  5. comment
    Comment #46782297

    Fair points :). The naming is 'evolutionary' — started as 'semantic diff' because it analyzes meaning not just lines, but 'commit review' is more accurate for what it does now. You…

  6. story
    Show HN: Semantic-diff – understanding intent, risk and impact behind Git diffs

    Hi HN — I built semantic-diff for myself, and it turned out surprisingly useful. Regular git diff shows what changed. semantic-diff tries to answer: – why was this change made? – w…

  7. comment
    Comment #46175769

    Interesting approach. A few questions: How do you handle false positives from mutation strategies like Base64 or token smuggling? In my experience, a lot of "successful" jailbreaks…

  8. story
    A three-layer memory architecture for long-running agents

    Anthropic's recent piece on effective harnesses for long-running agents hit close to home. We've been wrestling with the same problems — agents that try to one-shot everything, dec…

  9. comment
    Comment #46078316

    Hit exactly this problem some time ago (preliminarily buried 5 or 6 versions of memory systems). Generic summaries or RAG results often feel useless because models optimize for "wh…

  10. comment
    Comment #46077956

    We've been solving similar problems differently. Instead of a flat progress.txt, we use three layers: semantic context (what are we building and why), structured intention tracking…