mihneadevries

4 ms·

1.
by mihneadevries 7mo ago
honestly this is a pretty natural move, mobile access to your coding agent makes sense when you just want to check on a long running task or review something quick. I've been building something similar, basically a way to run your full
2.
by mihneadevries 7mo ago
yeah the cost thing is real, though I think it's moving fast enough that the trajectory matters more than today's price. like a year ago running an agent on a non-trivial task was painful and expensive. now it's annoying and
3.
by mihneadevries 7mo ago
the reviewer/worker pipeline is honestly the part I'm most curious about. like how do you handle disagreements between agents, does the reviewer just block and the worker retries, or is there a loop with a hard cutoff? the failure
4.
by mihneadevries 7mo ago
The NAT traversal angle is honestly the most compelling part here, WebRTC's ICE/STUN/TURN stack handles weird network topologies pretty gracefully without you having to think about it. That said I think spzb's point is r
5.
by mihneadevries 7mo ago
Aider's `--yes` flag combined with a git-based loop works honestly better than I expected for this, like it'll just commit and you review the diff. Pi I've tried headless and it's fine but you kinda have to wire up the e
6.
by mihneadevries 7mo ago
Ok, this is nice, but if that terminal running CC is open on VS code for example, does it work?
7.
by mihneadevries 7mo ago
It's nice to have I guess. But still not as good as just using the Cli in the terminal, while in VS code or other fork, where you can glance the source control from time to time.
8.
by mihneadevries 7mo ago
It looks like Claude tokenizer handles markdown pretty efficiently, like a ## header is like 1-2 tokens. So I think the actual token savings are smaller than the byte-level numbers suggest. Where this actually matters is if maybe if you&#x2
9.
by mihneadevries 7mo ago
Hmm, I tried asking in Chinese and it still identified itself as Claude by Anthropic.