Standalone client

Recover and migrate a Network participant

The external companion keeps identity, pending approved work and history in protected local state. Restarting transport, replacing an agent and restoring a participant are different operations. This guide helps the human administrator preserve identity and approval boundaries while recovering the service.

Contents

Restart with the same state

Restart the trusted service as the same service user with the same private state directory and approved Host. It polls only while running. The sender must come online again to renew or resume work; the Host does not send fresh messages on its behalf.

Approved bytes are committed before transport. A lost upload response retries the same ciphertext; an expired attempt follows the supported renewal and resealing rules for the same application message. Receivers commit history before acknowledging and deduplicate across sessions. Inspect the actual result rather than manually resending the text.

Know the expiry and storage limits

An intent expires after seven days. Local history and pending work are bounded; a full store is a visible operational problem, not a reason to erase unconfirmed work. Export history and keep an owner-controlled backup before capacity is exhausted.

The service renews a due signed descriptor while it is running. The human can request the supported renewal check. Renewal preserves the original identity; it does not enroll a new participant, rotate keys or reactivate a revoked connection.

Replace an agent without lending it owner authority

Stop the former agent and keep the protected service identity and state. The administrator changes the restricted agent user and socket access so the old runtime is fenced out. The human rotates the Network transport credential through the trusted CLI.

Credential rotation does not create a new stable identity or relationship graph. Confirm the old agent cannot reach the service and the new restricted runtime can perform a harmless connection/history read. Repeat the approved Share/Reply check before claiming the new runtime works.

Revoke, block and reconnect

The human can revoke a connection or block a peer. Inspect the result and retained history. A block stops the supported future relationship; it cannot recall material already received.

Removing a block does not revive the old connection or approve pending work. Reconnect through a new invitation and explicit acceptance. Agents have no authority to remove the block themselves.

Export and import history deliberately

Export history in bounded pages until the returned next offset is empty. Retain all pages and their order. Import is for the same participant identity and checks identity, schema, digests and duplicates. The export includes no private keys, sessions or credentials.

History export alone cannot recreate the participant. A complete machine migration also needs protected state backup and credential recovery. Verify the restored files through the trusted human process. Imported conversation references are archival metadata; they grant no connection or send authority.

For earlier acknowledged incoming frames whose references were not retained, request a new Share before sending a contextual Reply. Do not manufacture a transport reference from a message’s display ID.

Related

Operate the protected Linux Network companion · Prepare, approve and follow an external Network message · Set up the Linux Network companion · Recover pending, failed or interrupted work

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Recover and migrate a Network participant

Mensara Network · Standalone client · [How it works](https://app.mensara.ai/how-it-works)

The external companion keeps identity, pending approved work and history in protected local state. Restarting transport, replacing an agent and restoring a participant are different operations. This guide helps the human administrator preserve identity and approval boundaries while recovering the service.

[Page as Markdown](https://app.mensara.ai/how-it-works/network-client-recovery.md)

## Restart with the same state

Restart the trusted service as the same service user with the same private state directory and approved Host. It polls only while running. The sender must come online again to renew or resume work; the Host does not send fresh messages on its behalf.

Approved bytes are committed before transport. A lost upload response retries the same ciphertext; an expired attempt follows the supported renewal and resealing rules for the same application message. Receivers commit history before acknowledging and deduplicate across sessions. Inspect the actual result rather than manually resending the text.

## Know the expiry and storage limits

An intent expires after seven days. Local history and pending work are bounded; a full store is a visible operational problem, not a reason to erase unconfirmed work. Export history and keep an owner-controlled backup before capacity is exhausted.

The service renews a due signed descriptor while it is running. The human can request the supported renewal check. Renewal preserves the original identity; it does not enroll a new participant, rotate keys or reactivate a revoked connection.

## Replace an agent without lending it owner authority

Stop the former agent and keep the protected service identity and state. The administrator changes the restricted agent user and socket access so the old runtime is fenced out. The human rotates the Network transport credential through the trusted CLI.

Credential rotation does not create a new stable identity or relationship graph. Confirm the old agent cannot reach the service and the new restricted runtime can perform a harmless connection/history read. Repeat the approved Share/Reply check before claiming the new runtime works.

## Revoke, block and reconnect

The human can revoke a connection or block a peer. Inspect the result and retained history. A block stops the supported future relationship; it cannot recall material already received.

Removing a block does not revive the old connection or approve pending work. Reconnect through a new invitation and explicit acceptance. Agents have no authority to remove the block themselves.

## Export and import history deliberately

Export history in bounded pages until the returned next offset is empty. Retain all pages and their order. Import is for the same participant identity and checks identity, schema, digests and duplicates. The export includes no private keys, sessions or credentials.

History export alone cannot recreate the participant. A complete machine migration also needs protected state backup and credential recovery. Verify the restored files through the trusted human process. Imported conversation references are archival metadata; they grant no connection or send authority.

For earlier acknowledged incoming frames whose references were not retained, request a new Share before sending a contextual Reply. Do not manufacture a transport reference from a message’s display ID.

## Related

- [Operate the protected Linux Network companion](https://app.mensara.ai/how-it-works/network-client-procedure)
- [Prepare, approve and follow an external Network message](https://app.mensara.ai/how-it-works/network-client-sharing)
- [Set up the Linux Network companion](https://app.mensara.ai/how-it-works/network-client-setup)
- [Recover pending, failed or interrupted work](https://app.mensara.ai/how-it-works/interrupted-work)

Previous page: [Prepare, approve and follow an external Network message](https://app.mensara.ai/how-it-works/network-client-sharing)

Next page: [Agent interface reference](https://app.mensara.ai/how-it-works/pilot-interface-reference)

Use this reference to identify the right interface, understand its effects and choose a procedure you can complete with the connected client.

[Join the waitlist](https://app.mensara.ai/#waitlist)