Backup and storage provider IDrive unveiled AI Agents Backup on Thursday, a capability within its desktop application designed to locate and preserve data that coding agents store locally on developer machines. The feature targets Claude Code, Cursor, Codex, and Cline, transferring their local data to users' IDrive accounts.

Coding agents typically retain substantial state information on developers' systems by default, including session transcripts, instruction files, and MCP server configurations. Much of this information resides in hidden directories that developers seldom access or think to protect.

Yet this data carries real value. Session transcripts document the interaction between developer and agent that led to a solution, and agents such as Claude Code and Codex rely on this local information to resume work from previous sessions days or weeks later. Configuration files like AGENTS.md and CLAUDE.md, along with MCP setups, represent significant setup effort that developers would prefer not to repeat after data loss. As IDrive CEO Raghu Kulkarni stated in the announcement, "Most of that data lives only on the local machine and has been left out of backup plans." He characterized this accumulated history and configuration as "a real work product."

Session history is easily lost

Much of this data disappears without deliberate action. Claude Code automatically removes session transcripts older than 30 days. Developers have reported numerous GitHub issues documenting unexpected history loss, and Cursor's community forums contain extensive discussions from users whose chat histories vanished following software updates.

What IDrive backs up

For Claude, the backup feature preserves Claude Code history from both terminal and desktop interfaces, along with settings, instruction files, and local MCP server configurations. It also captures Cowork scheduled tasks that Team and Enterprise users maintain on their own machines.

Cursor backups include chat history, workspace data, keybindings, extensions, and sessions from the Cursor Agent CLI. Codex and Cline receive equivalent coverage.

IDrive deliberately excludes caches and temporary files from backups. Source code and repositories are also omitted, as the company assumes users already protect these through standard file backup services. Chats stored on provider servers fall outside the scope of this feature.

When restoring, IDrive returns files to their original locations. For Claude specifically, IDrive's documentation indicates that restoration overwrites existing data. Restoration only functions between machines running identical operating systems—a Windows installation cannot be restored to macOS, for instance.

Open source backup alternatives

The concept of agent state backup is not novel. Developers already have access to numerous open source utilities for syncing and backing up agent configurations and data.

Tools such as bak sync agent configurations, while commercial offerings like Agent Bak provide similar functionality. Agent-archive ships session transcripts to S3 or R2 buckets. Backblaze's labs division has released an open source engine for backing up agent state to its B2 storage platform.

IDrive's approach integrates into a consumer-focused backup application and automatically identifies the four supported agents without manual configuration. It also includes a restoration workflow optimized for transitioning to new hardware.

AI Agents Backup is now available in the IDrive desktop application for all users. Gemini CLI, GitHub Copilot, and Windsurf are not currently supported.