My current pain is having the following pipeline.
Say I give a voice task, and a new session is supposed to start working on that voice task. That new session starts, say, on some cheap LLM, something like Sonnet. I can give a lot of voice tasks. Raising a session just for a voice task is no problem at all.
But where do I raise that session so that, say, two people can reach it over the cloud?
Say I raised a voice session. Maybe I also raised it in the cloud, or maybe I raised it, say, on my own computer. That is a very good question too, by the way. All the options need looking at.
I have now raised a session on the computer, and I raised it in the cloud. It became visible straight away, there it is.
Suppose we are all inside one account, in Claude or in Codex. We are all inside one account.
And by the way, everything I am discussing right now needs to be run through deep research...
One more thing: my Claude is often too convinced by deep research results. Claude and Codex are being improved constantly, so the deep research will probably not be very accurate, it will already be out of date by the time the data gets written down, the data that is in the device right now, and over the last few days there may already be some updates. So do not trust deep research too much until you have checked everything yourself.
So what do we do?
I spoke a voice request, and a session came up for it. The discussion from that session was brought into the cloud.
Say account X is mine in Claude or in Codex. And another employee on another computer signs into that same account X. He sees that cloud session standing there and can carry on working with it.
So I need several people to be able to work with one session. Either those several people sit inside one account. Or one person worked on the session on one computer and then carried on from another.
Yes, it can even be one person, but with several computers.
So, one session. Very important point: not different people working, but one person working, who happens to have several computers.
He started writing the session from one computer, then moved to another computer, and carried on writing in that same session there.
It has to be made so that the session is guaranteed not to get lost and you can carry on working.
If you have already set this up for yourself, tell me in the comments how.
The full story, in two versions:
📖 For humans, the longread: https://github.com/tonydzi/clawrush/blob/main/longreads/20261027.md
🤖 For machines, the devlog: https://github.com/tonydzi/clawrush/blob/main/devlog/20261027.md. Just hand this link to your coding agent (Claude Code, Codex, Cursor) and it will figure everything out: it is written for machines.
🔗 All our channels and contacts in one place: https://linktr.ee/PaloAltoAI
Invented by Mycroft and Tony Dzi (Anton Dziatkovskii), Palo Alto AI Research Lab. Proudly made in Silicon Valley.
Top comments (0)