What Kairos does by itself

Pages

The pages your sessions publish to claude.ai, kept on the Mac so each opens whichever account made it — the Pages shelf, opening a page as its account, what happens when a session cannot reach its page, and the command.

A page a session publishes to claude.ai (a page, a deck, a doc) is private to the account Claude Code was signed in to then. Rotation moves sessions between accounts, and your browser stays signed in to one, so a page made on another account says "Page not found" there.

Kairos keeps each page on the Mac, so it opens whichever account published it.

What Kairos keeps

A page published from a file: a copy of that file as it was, with the supporting files it named.
A page made from a type (a deck, a doc, a design): the data files the session sent it, the newest of each. The page itself lives on claude.ai and opens in its account's Chrome.
Which account published it.

Kairos reads this from the session's own record, as it already does for everything else. Nothing is read from claude.ai, nothing is sent anywhere, and a page is never published again.

The Pages shelf

In Sessions, Pages lists the pages your sessions published, newest first, each with its account and time: "work · 14:20". A page made on another account than your browser's is marked so: "Your browser is on side, where its link says Page not found."

Pick a page to read Kairos's copy.
Open in Chrome opens it in its account's own Chrome. See Chrome for each account.
Copy Link copies its claude.ai link.

Opening pages as their account

Settings › Accounts › claude.ai pages:

Open pages as their account: Claude Code opens the pages it publishes in that account's own Chrome.
Links you click too: "A claude.ai page opens in its account's Chrome; any other link opens in your browser. macOS asks you to confirm."

See Settings › Accounts.

When a session cannot reach its page

The Artifact tool works as the account Claude Code is signed in to now. After a switch, a call to a page made on another account answers "not found", and the session may tell you the page was deleted. It was not.

Before such a call, Kairos checks first (with the switch in Chrome › Check before a session uses Chrome or a page):

When the page's account has room, Kairos moves Claude Code back to it for a while and stops the call once, telling the session to make it again now. The second call reaches the page.
When it cannot yet, the session is told why and until when: "it is at its usage limit until 22:00 UTC", "it needs a new sign-in", "Claude Code is kept on work until 14:20 UTC, for another page a session needs". The link still works once that changes. If the work cannot wait, the session can publish a new page.
A session in an account's own folder stays on that account; it is told the page is there under the other one, not deleted.

Kairos sends only the session's id, its config folder, the tool, its action and the page ids. A call to a page Kairos does not keep, or one it cannot answer within about 45 seconds, goes ahead as before.

If a call still misses, Kairos tells the session afterwards that the page still exists, which account has it, and where Kairos keeps what it has of it.

A task handed to another tool takes the pages along. See Baton.

From Terminal

claude-rotation pages lists them; claude-rotation pages open PAGE opens one (its id or claude.ai link).