tuo-lei

5 ms·

1.
by tuo-lei 12d ago
Me toooo, for all my personal projects I need to pay for the tokens~ At workplace I use sol because I don't need to pay
2.
by tuo-lei 3mo ago
the taste part for me is cutting what the agent generated. 200 lines come back, i keep 80, no test for which 80.
3.
by tuo-lei 3mo ago
does the userland persist across app updates? curious what happens to my modify changes when you ship a new version of y
4.
by tuo-lei 3mo ago
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.
5.
by tuo-lei 3mo ago
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.
6.
by tuo-lei 3mo ago
how does this pull the quota data? reading from the CC process output or is there an actual API for it?
7.
by tuo-lei 3mo ago
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.
8.
by tuo-lei 3mo ago
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.
9.
by tuo-lei 3mo ago
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, but you're still paying for the round trip. better t
10.
by tuo-lei 3mo ago
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.
11.
by tuo-lei 4mo ago
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 URL the injection puts in. messaging is usually the first too
12.
by tuo-lei 4mo ago
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 screen pipe, that provide `what did
13.
by tuo-lei 4mo ago
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 trace to a config change from 3 deploys ago. if the MCP on
14.
by tuo-lei 4mo ago
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, just bad at session-level decisions like when to stop
15.
by tuo-lei 4mo ago
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.
16.
by tuo-lei 4mo ago
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 subtly wrong costs way more to fix because you can'
17.
by tuo-lei 5mo ago
is there any data on how many Actions minutes a single copilot review actually takes? the announcement doesn't mention it, and for a team doing 20+ PRs a day that number adds up fast.
18.
by tuo-lei 5mo ago
same issue from the other side. when a human is editing, the LSP fires mid-keystroke and shows bogus errors for a second, whatever. with an agent doing 5 edits in a row, the symbol DB is always behind by one edit, so the next lookup pulls s
19.
by tuo-lei 5mo ago
the scan catches surface stuff. funnier signal would be tracking when the agent reads the same file 3 times in a row, or deletes what it just wrote. you can hear the frustration in the access pattern.
20.
by tuo-lei 5mo ago
atomic commit with the business data is the selling point over separate IPC. external message passing always has the 'notification sent but transaction rolled back' problem and that gets messy. one thing i'm curious about: WA
21.
by tuo-lei 5mo ago
the async transport feels like the wrong layer to optimize. biggest issue i keep running into is agent session state being completely non-portable between tools. Claude Code dumps JSONL, Cursor splits data across SQLite and separate JSONL f
22.
by tuo-lei 5mo ago
The monthly cadence is what makes this work. I recognize the feeling of having ideas rot in a notes app because you keep waiting for the "right" version - a fixed shipping rhythm kills that problem. Favorites: VandalAds (the spray
23.
by tuo-lei 5mo ago
The single HTML file as a distribution format is really underrated. No server, no CORS issues, no CDN — just open the file. It works offline, you can email it, and it'll still work in 10 years. I ship self-contained HTML files for a di
24.
by tuo-lei 6mo ago
Claude code on the other side is much more cleaner, also made build tool on top of it really easy. I have a deep dive in Claude code local sessions as well, I believe many people have done it already
25.
I did a deep dive into cursors SQLite storages, different from Claude Code(vibe-replay.com)
1 points by tuo-lei 6mo ago|2 comments
26.
by tuo-lei 6mo ago
As everyone probably already know, cursor is not really local first, a pretty significant part of logic is in their server env, yet their local storage still can provide some information. Their data are spread between SQLite and JSONL, depe
27.
by tuo-lei 6mo ago
The missing piece for me is post-hoc review. A PR tells me what changed, but not how an AI coding session got there: which prompts changed direction, which files churned repeatedly, where context started bloating, what tools were used, and
28.
by tuo-lei 6mo ago
My main frustration with long-context coding sessions isn't just the limit itself, it's that after the fact it's hard to tell which turns actually caused the context to bloat or the session to go off track. It's painful
29.
by tuo-lei 6mo ago
do you have any suggestions for alternatives then (besides Sentry)? I do feel OTel have pretty wide support in general in term of traces.
30.
by tuo-lei 6mo ago
Human have a better taste (at least for now :D)

More ›