@oldstackjournal I log out because unauthorized SSH access to a server is illegal. If I'm granted access, I run`codex` and `claude` to check for an AI cli to do a directory, network scan and assess what's in the environment.
@StefanoGPT@theo No shot they have 5M users at $200/month. I'm not even sure if those 40M users are paying, or if they are bundling in mobile app users via chat/work toggle; my guess is 90% on the $8/20 tier, 6% on the $100 and 4% on the 200
They have over $1 Trillion in spending commitments...
@hhawk@thsottiaux This :/
I would have been fine with my rationed weekly allowance, but I sent off some bigger tasks to (astra ultra, fast) to use it up and now I'm stalled out on regular work
@skyzer4ever@AdamHoltererer@thsottiaux They might be running non-relational like Mongo, but also, it has to distribute across ledgers globally
¯\_(ツ)_/¯
@MysteryEthos@thsottiaux Don't worry, you can get the $500 plan for 25x usage
It's only 2.5x the cost and 20% more usage for the plan you used to be able to get for $200 last month
@tomiyasu16 Trying to build Jarvis as well. My current approach has been provisioning a server & use openclaw as the voice gateway to orchestrate anything on that server or talk via A2A to other 🦞 instances which themselves orchestrate codex.
Omnidirectional, from any device to any device
@bygregorr@Codex_Changelog Grok says
Preserves
• Full conversation hist.
• Drafts + queued prompts
• Clean new thread, original stays untouched
Doesn't preserve
• Guaranteed prompt-cache hits on inherited prefix, though it's been discussed
• Full live tool/shell runtime state
@ChrizBogota@MmuzTW@OpenAI@thsottiaux@sama The government actually requests that they quietly do this if they suspect distillation, which, if somebody is rotating multiple accounts on a proxy for example, could trigger that. The intentionally don't disclose it because if you tell it distiller, you give up the game
@thsottiaux@stemonte FWIW, there are a lot of traps that burn extra tokens.
If I delegate to tons of sub agents and those are reporting back to Sol, that causes a lot of polling / turns on Sol when each reports back.
I reduced polling freq & use exec -> orchestrator+reviewer -> implementers