Live data from Hacker News

Viewing profile — tuo-lei

tuo-lei

HN member
Joined
Thu, Mar 26, 2026, 6:36 AM UTC
HN karma
24
Public activity
52 items

About tuo-lei

vibe coding as a hobby, building vibe-replay at the moment. working on agent harness and platform full time.

Recent public activity

  1. comment
    Comment #48674282

    the taste part for me is cutting what the agent generated. 200 lines come back, i keep 80, no test for which 80.

  2. comment
  3. comment
    Comment #48654986

    does the userland persist across app updates? curious what happens to my modify changes when you ship a new version of y

  4. comment
    Comment #48631033

    [flagged]

  5. comment
    Comment #48599251

    nice pattern with the stored queries for writes. but who defines them? if the app author can create their own stored queries, the write restriction is basically honor system.

  6. comment
    Comment #48586328

    so the 11% miss rate - do users actually notice when the agent drops a memory? like if someone already said they tried X and the agent suggests it again.

  7. comment
    Comment #48556168

    [flagged]

  8. comment
  9. comment
    Comment #48477183

    how does this pull the quota data? reading from the CC process output or is there an actual API for it?

  10. comment
    Comment #48467386

    how are you handling errors? when an agent gets a flag wrong, cli help text is usually massive. could eat a lot of the savings on retries.

  11. comment
    Comment #48446123

    review agents have the same training biases as the one writing the code. you get 30 findings about error handling and edge cases, but wrong domain assumptions slip right through.

  12. comment
    Comment #48413274

    the bigger problem is agents defaulting to the broadest command possible. kubectl get -o yaml when a jsonpath query would give 1/50th the tokens. filtering after the fact works, bu…

  13. comment
    Comment #48399480

    the bottleneck with multi-agent setups isn't getting them to talk. it's getting a human to review what they agreed on before it ships.

  14. comment
  15. comment
  16. comment
    Comment #48280625

    allowlisting breaks once the agent has messaging tools. you can deny all outbound from the agent, but if it can post to teams or slack or email, link previews will fetch whatever U…

  17. comment
  18. comment
    Comment #48238960

    I built a vibe coding replay/inspection tool https://vibe-replay.com/ I built a co-work for cursor, I haven't publish that yet I also built something combined activity watch and sc…

  19. comment
  20. comment
    Comment #48212221

    [flagged]

  21. comment
    Comment #48197543

    investigation is the hard part, not generating patches. we've had prod issues where the fix was obvious once you knew the cause, but finding the cause meant connecting an error tra…

  22. comment
    Comment #48183801

    they say it themselves in the post - behavior dimensions "not well captured by existing benchmarks". that was the exact problem with composer 2. not dumber on individual tasks, jus…

  23. comment
  24. comment
    Comment #48125827

    i've made maybe 20 personal LLM tools this year. 3 survived past the first week. not because the rest weren't useful, just wasn't willing to debug them when something broke.

  25. comment
    Comment #48099077

    maintenance cost on AI code isn't really uniform per line. most of it follows standard patterns, maybe easier to maintain than average human code. but the 5% where something went s…