Admin ConsoleCollaborate
Shared sessions
Share a LatentCode session with your organization so teammates can pull it into their own sessions as context, and manage what's been shared.
How sharing works
- In LatentCode, run
/push-to-registryto share the current session with the organization it runs in. - Before it's stored, personal data, secrets and local file paths are stripped from it.
- Teammates in the same organization pull it into a session as context with
@sync:reg_<id>.
A shared session is visible only inside its organization. By default each person can share up to 20 sessions an hour, and very large sessions are rejected. See LatentCode for the commands.
Your shared sessions
Open Shared Sessions from My account to see what you've shared in the active organization. Each card shows the title and the goal from the session summary.
| Control | What it does |
|---|---|
| Hide / Unhide | Hides the share from teammates without deleting it. The card is marked Hidden by uploader. |
| Delete | Removes the share permanently after you confirm. |
If an admin hid one of your shares, it's marked Hidden by admin; you still see it, your teammates don't.
Session Registry (admins)
Session Registry in the Administration group lists every session shared to the organization, from any member, grouped by day. Search by title, summary or uploader. Your own shares carry a You badge.
- Hide makes a share invisible to everyone except the person who shared it. Unhide reverses it.
- Delete removes it permanently.
Troubleshooting
A teammate can't find my session
Check that you shared it from the same organization they're working in, and that it isn't hidden.
The page says it failed to load
Select another organization and back, or reload. The error text says what went wrong.