​

Shared Sessions

Shared sessions let authorized project members browse retained conversations and continue them on another device. The project must be linked to your AIUS account. New uploads also require capture to be enabled on your AIUS deployment. This is separate from project-file synchronization and from the /share command.

​

Choose whether to share

History sharing starts off on a new client profile. In your linked project:

1. Type /shared-sessions in chat, or choose Browse shared sessions in the command palette. /shared-history is an alias.
2. Select Enable history sharing for this project.
3. Read the disclosure and confirm Enable sharing only if these conversations may be shared with your project team.

The preference is stored privately on this device, separately for each API environment, organization, and project. It does not enable sharing on another device or for your other projects. You can browse existing shared sessions without enabling capture from this device. To stop, return to /shared-sessions, choose Stop sharing history from this project, and confirm. This stops new uploads from this device. It does not delete previously shared history or the original local transcript. Operators can also opt in with AIUS_SESSION_HISTORY_CAPTURE_ENABLED=true. An explicit Stop sharing preference for a project takes precedence over that environment setting. The deployment’s server-side rollout gate remains independent of either client preference.

​

Continue on another device

1. Sign in with your own account and open the same linked project.
2. Open /shared-sessions and select a retained conversation. Use Load more sessions when the list has another page.
3. AIUS imports the retained conversation into this device’s local history. Review it, then send a new message to continue.

Importing does not start an agent run. Historical tool calls and results are shown as text; they are never re-executed by import. Your next message starts a new run using the imported conversation as context, subject to the normal context limits and current permissions. Repeated imports keep the same session identity and do not duplicate saved events. They do not overwrite an original unredacted local message with its server-redacted copy. If an import stops midway, retry to continue from the pages already saved locally. aius --continue and aius --session <id> reopen sessions already present on that device. Use /shared-sessions first when the conversation exists only on the server. Existing local-session export is separate from shared-history import; there is no additional canonical-history export screen.

​

Retention and interruptions

Shared history is a retained, redacted record—not a complete backup of local files or every byte of a transcript. The default server retention is 30 days; expired or inaccessible sessions are unavailable for import. Your account must still have project membership. A read-only project-share viewer does not gain conversation-history access through that share. If a run disconnects, AIUS keeps the interrupted response and tool outcomes locally and attempts an authenticated history upload without restarting the model. If the API is unreachable, the local transcript remains available for a later run to retry. Another device cannot read content that has not reached the server yet. Uploads are chunked by event count and serialized size. An individual event whose content exceeds the transport limit is represented by an omission marker, while the original remains on the source device. Import fetches retained history in pages; it does not replay tools or download project files. If shared history is unavailable, check your login, project link, and project membership. Disabling the deployment’s capture setting stops new uploads, but authorized members can still read previously retained history until it expires or their access is removed.