/sessions shows your Claude Code, Codex and Antigravity sessions on every machine you connect: which ones need you, which are working, what each one did, the pages it published, and the command that reopens it. Connecting a machine is part of Pro, Max and Team, with sessionpipe, the open client for session hooks. Run this once on each machine, in the folder you code in, and approve the link it prints with your passkey:
npx -y sessionpipe@latest connect spacesheep.dev --mode autoThat hooks every coding tool it finds on the machine (and installs sessionpipe globally, since a hook has to start in milliseconds) and pairs its daemon, so you can also message the sessions. The hooks send each session's state and place (machine, folder, repository, branch, model, title), with credentials redacted on your machine before anything leaves it. sessionpipe doctor checks them; sessionpipe uninstall takes them out. A machine set up earlier with spacesheep sessions install keeps reporting; npx -y spacesheep@latest machine on moves it to sessionpipe. Agents read the same sessions with list_sessions and get_session. What is kept, and for how long, is in the privacy policy.