From recent ChatGPT (GPT5.6) conversations where I've seen occasional reasoning leaks into the UI, it's clear that something like this is already implemented, and I'd speculate that this is the majority of recent claims of less token usage. Not sure if they are literally prompting for cablese of course.
"Need check output vs prev. Ran script, results fine, need prep next step. Ready? Go."
I suspect you might be right. My conclusions from the digging are that this kind of compression works best with settled instructions/data for machine to machine talk. For something like OpenClaw (which I use a lot), that might mean the AGENTS.md, TOOLS.md, etc. Compression there would free up the context for the agent.
Not quite, and its addressed in the post. Caveman was cool, but hand wavy. I've measured the compression of Cablese, determined where it does the most good, and also that it is already baked in to most model family's training, which saves instruction tokens.
"Need check output vs prev. Ran script, results fine, need prep next step. Ready? Go."