tuo-lei

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

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

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

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.

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.

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

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.

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.

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 to teach the agent to ask narrow questions in the first place.

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.