The Canaanite

Engineer & Biohacker | Focusing on Geopolitics, Ancient Mysteries, Psychedelic Therapy, Tech & AI. e/acc ⏩

[The Canaanite @mysticaltech]

we're like computer threads running in a simulated environment to:

1. grow our soul, learn a lesson, purify it to see the light
2. do our mission and contribution to others

Some threads end early before even starting, some drop the job half way, others complete the job and exit cleanly.

the self is a useful illusion given to us by the real, it serves the mission.

we come from dust, we go back to dust.

what remains after us is potentially an imprint on the world around us, that can be averaged out as either signal or noise.

[The Canaanite @mysticaltech]

@sevaustinov 🤣

[🍓🍓🍓 @iruletheworldmo]

‼️looks like a few cryptic accounts are starting to hint a 5.6 release will come tomorrow.

it will 100% launch tomorrow and its a significant upgrade on anything, including mythos.

there will be no hedging, no ‘oh it was meant to launch today but ermmmm there was a power outage’

stick with the strawberry man to find out before anyone else when models release.

i got 5.5 and opus weeks before anyone else. im the undisputed king in this world chat. sit down.

[Unsloth AI @UnslothAI]

@googlegemma Thank you Google Deepmind for constantly releasing open models! 🌟

We made Dynamic GGUFs so you can run Gemma 4 12B more efficiently: https://t.co/8cL321pVDh

[The Canaanite @mysticaltech]

@googlegemma This is mega cool!

[Google Gemma @googlegemma]

Meet Gemma 4 12B!

A unified, encoder-free multimodal model designed to bring high-performance intelligence directly to your laptop, and released under an Apache 2.0 license.

Bridging the gap between edge efficiency and advanced reasoning. Here is what’s new with Gemma 4 12B: 👇

[Matthew Miller @matthewmillerai]

OpenAI has nerfed its usage limits completely.

Usage limits were cut in HALF overnight.

Claude Code usage limits are now better than Codex.

[The Canaanite @mysticaltech]

@itsandrewgao what, say that again? devin can run codex and claude code for us, with our own subs? you support ACP like what Zed does?

[The Canaanite @mysticaltech]

@levelsio So all in English there?

[The Canaanite @mysticaltech]

@SIGKITTEN 😅

[The Canaanite @mysticaltech]

@jxnlco yeah, urgent token reset count needed, please 🫣

[The Canaanite @mysticaltech]

@SIGKITTEN hell yeah, lol

[The Canaanite @mysticaltech]

@SIGKITTEN *unlimited tokens

[The Canaanite @mysticaltech]

@SIGKITTEN you just omitting to mention that you ride on gpt-5.6-preview-internal 😂

[The Canaanite @mysticaltech]

@mlech26l Damn

[Andrew Ambrosino @ajambrosino]

Universal Basic Codex (?)

[The Canaanite @mysticaltech]

@ajambrosino Now we talking!

[The Canaanite @mysticaltech]

@CyberSecurityQA @thsottiaux Check your config.toml, IMHO

[Tibo @thsottiaux]

Tons of goodies for use of codex for day to day work.

If you are on a business plan you can now host and share websites, we launched vastly improved plugins and skills for broad roles and you can give feedback to your agent through visual annotations in docs, slides, sheets and more.

[The Canaanite @mysticaltech]

@koltregaskes @thsottiaux Yes, definitely! Pro should have ALL the good stuff.

[The Canaanite @mysticaltech]

One piece of feedback from a power-user perspective: account boundaries are becoming a real workflow friction point.

I currently use both a personal Pro account and a separate Business account. In practice, work does not fit neatly into those silos. For example, I may want to use Codex from my Pro account while publishing or deploying assets into a Business workspace that I also own and manage. Today, that kind of cross-account workflow is unnecessarily difficult.

A related issue is resource sharing. If one account exhausts its usage limits while another account I own still has available capacity, there is no practical way to leverage those resources within the same Codex workflow. From the user's perspective, ownership is unified, but the tooling remains fragmented.

I realize this is a complex problem involving permissions, billing, security, and organizational boundaries. However, it feels like there should be a middle ground. For example, users could explicitly pair accounts they own, verify ownership of both accounts, and then grant specific permissions between them (deployments, workspace access, usage sharing, publishing rights, etc.).

In general, I think "account pairing" or "trusted linked accounts" would solve a growing class of problems. Modern work is messy, and many of us operate across personal, business, and organizational identities simultaneously. The tooling would feel much more natural if it could reflect that reality.