AI agents need continuity, not just context

Pulumi Neo redesigned recovery for long-running hosted agent tasks by treating the full working directory, rather than Git repositories or conversation history alone, as the essential unit of continuity. Its earlier Git-based reconstruction could restore commits and patches but often lost generated files, dependency state, scratch output, local commits, and non-repository files, while also failing when remotes disappeared, diffs became too large, or patches no longer applied. The new system uses Kopia to create encrypted, incremental, task-scoped workspace snapshots in object storage, separating event replay for model memory from filesystem restoration for agent-created state. The service acts as a control plane that authenticates tasks and issues short-lived, prefix-scoped credentials, while runtimes directly restore and checkpoint data, with per-task repository passwords and trusted cleanup preventing agents from deleting durable history. A staged rollout through disabled, shadow, and enabled modes retained Git reconstruction as a fallback, allowing snapshot behavior to be validated before it became authoritative. The design excludes recreatable caches where appropriate, uses retention and maintenance to control costs, and adds detailed observability for independent failures in authorization, snapshots, restores, and event replay. As Neo introduced managed workers, lease-based ordering ensured that tool results and snapshot pointers advanced together, preventing stale workers from overwriting newer recovery state. Internal testing found that snapshot restores were faster and more reliable than legacy recovery, illustrating that resilient agent systems must preserve both conversational context and the workspace in which the agent performs its work.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.