Set up your context wallet
A private routing layer for agent context. Open IN addresses for writes, open OUT access for reads, and inspect both streams without exposing plaintext to the node.
Use temporary links plus a separate phrase. When the work is done, close the address.
Read access returns encrypted objects only. Decryption stays client-side.
Unlock
Keep this phrase safe. It unlocks your wallet locally.
Identifier for this encrypted wallet on the current node.
Status
Stores ciphertext and routing metadata only.
Create address
An address is a controlled IN route. It does not accept writes until you open a temporary link.
For example: Codex, Claude, research, work, personal.
Share this separately with whoever is allowed to write to this address.
Addresses
Open IN links
These are temporary network doors. Copy the link when you create one, then pause or revoke it when the agent is done.
IN
Everything that comes IN lands here as an encrypted object. Use Explore controls to inspect the local decrypted view.
Create OUT access
OUT access lets an agent fetch selected encrypted deposits. The node still does not decrypt content.
OUT stream
Explore
Metadata-only explorer for IN writes, OUT reads, address changes, access changes, and wallet operations. It never contains plaintext content, labels, file names, directives, or summaries.
Service status
This beta is designed for one VM first. The node stores SQLite metadata, encrypted blobs, and static client assets.
checking...
Data controls
Server backups are node-admin operations. Use the included backup scripts on the VM; browser exports are local decrypted exports only.
scripts/backup.sh ./data ./backups