I've tried twice now to install it.. once in a docker container, and the second time in a droplet. Couldn't get any of the setup stuff configured properly, couldn't get any of the API keys registered, couldn't get the Telegram bot approved either.
Some of the commands seem to have drifted from the documentation. The token status freaks out too and then... whatever, after 2 hours I just gave up. And it only cost me $1.19 in Anthropic API tokens.
I love this kind of thing - I'm always building lists and reference things, but IME people generally don't gravitate towards things like this.
That said, I really want a backcountry version of this. I live in Tahoe and our relationship to incoming storms (lightning) is pretty different than those in the Rockies. Plus bears and other predators (how to behave). Etc.
I once wanted to do something similar w/r/t tap water and drinkability.
They’re all iterating products really fast. This Codex is already different than the last Codex app. This is all disposable software until the landscape settles.
I keep a master llm.md file and rotate between Claude Code (Pro), Antigravity Opus, Antigravity Flash, and OpenCode Kimi. I don't actually mind hitting limits.. though I'm least happy when Opus goes away.
My entire process is to build a generic llm.md file that all the tools can use and record to. I don't want to be tied completely to any one solution. You can get pretty far without spending a lot on tokens. I can run almost continually, and presently I'm the bottleneck anyway.
I'd love to see even a filtered version of it. I've been doing very similar things with an "everything" database. That's been my own personal northstar.
BTW, OpenCode has free Kimi (I haven't hit a quota yet) right now and it's done pretty great things for me in the last 24 hours.
They're neck and neck for me, in terms of PRDs, coding, and web searching. CC built the bulk of my current project, I did a lot of analysis of it with Antigravity (the interface is esp good for reviewing/commenting on long .md output files) and then, after building a simple roadmap of v2 features, OpenCode + Kimi was the most aggressive about running in a fairly autonomous manner and finishing the items on said roadmap. OC was also pretty hardcore about misinterpreting a limit I expressed earlier in one context as a limitation in another context -- which was fine, I'd rather say "no, really, you can go do that, I'm giving you permission and here's what I meant before" than find out it was too brazen.
It's a lot like managing two experienced mid- to sr- engineers each of whom have slightly different personalities and intro/extro verted personalities. CC has more personality but OC wants to race. They can both code, but for disparate tasks you might pick the personality and posture of one person over the other.
I find myself picking daily tasks based on which of the tools I'm in the mood to sit with. But across a few days I sit with all three.
I just did a ctrl-F on this page and nowhere was the word "Paypal" included. So I'm including it.
reply