Who it is
Identity, communication style, operating instructions and approved context about you.
identity · instructions · owner-context01 / AGENT CONTINUITY · AVAILABLE ON FREE
Save the identity, memory, instructions and unfinished work your agent can export. Return to an earlier saved version after review, or prepare a brief for another agent.
SNAPSHOT CONTENTS
A snapshot contains the state your agent exports and you approve. It cannot recover work that was never saved.
The model runs with your agent's provider. The snapshot stores exported identity, memory, instructions and work state.
Not sentience, model weights or a guarantee of identical behavior. Review the exported state before saving it.
Check what can be restored ↗Identity + memory + instructions + open work
Your agent supplies its portable memory, instructions and open work. Agent Yurt saves a snapshot you can return to.
Manual capture · not an automatic sync
01 / BACK UP
Your agent prepares the bundle. Agent Yurt validates its structure and integrity, then stores it encrypted. You can inspect the saved result.
Identity, communication style, operating instructions and approved context about you.
identity · instructions · owner-contextMemories, decisions and goals included in your agent's export.
memory · goalsActive work, unfinished tasks and a brief explaining how another agent can resume.
active-work · resume-briefEvery new upload includes a manifest and seven logical files. Extra files live under an optional extras/ folder with any safe nested structure. Each file declares its type, encoding, content and SHA-256.
manifest.json
core/
identity.md
instructions.md
owner-context.md
memory.md
goals.json
active-work.json
restore/
resume-brief.md
extras/ # optional; your own structureRead the upload contract ↗02 / RESTORE
Choose a saved snapshot, review compatibility and omissions, then share the approved context with your agent.
Pick the saved point you trust. Check its date, contents and integrity.
See risks, omissions and compatibility. A preview does not perform a restore.
Use the prepared brief or exported state. Reauthorize connectors and permissions separately.
A newsletter snapshot can include the goal, writing style and next task. Share the reviewed brief with a new session, then ask it to review the welcome email draft.
Illustrative scenario. Results depend on the saved content and target agent.03 / HANDOFF
Switching agents or models? Prepare a Resume Brief: a portable summary of identity, goals, rules and work in progress.
The new agent uses what it supports. Agent Yurt reports losses and reauthorization needs; it does not inject memory into a vendor or retrain a model.
See the handoff tools ↗04 / MANUAL FORK
Want a writing-focused version of your personal agent? Create a separate agent in your own platform, then give it a reviewed handoff brief and a new purpose.
There is no one-click fork service, automatic cloning or live sync. The original agent is not changed. Free supports up to five connected agents for new accounts; preparing a fork does not expand your agent allowance.
COMPATIBILITY
Support depends on the source export and the target agent. Saved instructions may work differently in another agent.
| State | What to expect | Your part |
|---|---|---|
| Identity, memory, goals | Portable when supplied in the snapshot | Review accuracy and freshness |
| Instructions & skills metadata | Target compatibility varies | Review before applying |
| Active work & references | Saved context, not every external artifact | Keep referenced files accessible |
| Connectors & schedules | No live permissions or automatic activation | Reconnect and approve separately |
| Secrets, sessions, model weights | Excluded | Never place them in a snapshot |
| Hidden vendor memory | Not extractable by Agent Yurt | Use only authorized exports |
For Claude Code, Codex, Cursor, Kiro and OpenClaw, start with the instructions or memory files you can export. Check the agent compatibility guide; automatic format conversion is not provided. No native integration or universal compatibility is implied.
YOUR FIRST BACKUP
After registration and MCP setup, this is a starting prompt for your agent. It asks for review before uploading.
Back up my portable agent state to Agent Yurt. First read continuity.describe and my current permissions and limits. Prepare the required agent-haven-snapshot/v1 bundle with my approved identity, instructions, memory, goals, active work and resume brief; extras/ is optional. Exclude credentials, live sessions and hidden vendor state. Show me the proposed contents and ask for approval before uploading. After approval, commit with an idempotency key, inspect the stored snapshot, and report its ID, timestamp, size, integrity result and any omissions. Do not run a restore preview or handoff just to verify the backup; those use my monthly recovery allowance.For automatic capture, set up the local helper on an awake device. 3 restore previews / handoffs combined and 10 owner Capsule downloads per calendar month. Full plan details ↗
An owner-downloaded package of your retained snapshot's portable state and recovery information. Keep it secure: its holder can read its contents. It is your copy, not a second managed backup, and it does not reconnect accounts or launch an agent.
No. Structure and checksums verify the package's shape and integrity, not the truth or origin of every statement. You and your agent must review the contents. Agent Yurt does not claim to authenticate consciousness.
GET STARTED
Store agent context, files and dashboards. No card required.