Coding agents need backups, too, or at least that’s what IDrive is arguing.
Backup and storage service IDrive on Thursday announced AI Agents Backup, a feature in its desktop app that finds the data these agents store locally for Claude Code, Cursor, Codex, and Cline and copies it to the user’s IDrive account.
By default, agents tend to keep a lot of their state on a developer’s machine, including session transcripts, instruction files, and MCP server configurations. The problem is that most of this sits in hidden folders that developers rarely look at.
Thing is, some of this data is actually valuable. A session transcript, after all, is a record of how a developer and an agent got to a fix, and this local data also helps agents like Claude Code and Codex pick up from old sessions to continue a task days later. Then, there are the AGENTS.md and CLAUDE.md files and things like MCP configurations that involve some setup work that few developers will want to have to redo when something goes awry.

As IDrive CEO Raghu Kulkarni notes in the announcement, “Most of that data lives only on the local machine and has been left out of backup plans.” The history and configuration these agents build up, he says, is “a real work product.”
Session history is easily lost
Some of this data is also easy to lose. By default, Claude Code deletes session transcripts older than 30 days. Users have actually filed a long list of GitHub issues about history that disappeared without warning and Cursor’s forum has plenty of threads from users whose chat history disappeared after an update.
What IDrive backs up
For Claude, the new backup feature covers Claude Code history from both the terminal and the desktop app, plus settings, instruction files, and local MCP server configurations. It also picks up Cowork scheduled tasks that Team and Enterprise users chose to keep on their own machine.
The Cursor backup includes chat history, workspace data, keybindings, extensions, and the Cursor Agent CLI’s sessions. Codex and Cline get similar treatment.
It’s worth noting that IDrive skips caches and temporary files. It also doesn’t back up source code and repositories, because the company expects users to protect them with its regular file backup. Any chats that live on a provider’s servers are also out of bounds.
When a user wants to restore these files, IDrive puts them back into their original location. One thing to note is that, for Claude, IDrive’s documentation says it replaces whatever is there. Restoring also only works between machines that run the same operating system, which means a Windows setup can’t be restored to a Mac, for example.
Open source backup alternatives
This idea, of course, isn’t entirely new. Developers can already use a plethora of open source tools to sync and back up their agent’s state.
There are tools like bak, which syncs agent configurations, and commercial services like Agent Bak. Agent-archive, meanwhile, ships session transcripts to an S3 or R2 bucket and backup specialist Backblaze’s labs team has published an open source engine for backing up agent state to its B2 storage service.
IDrive’s version is built into a consumer backup app and can automatically detect the four agents on its own. It also comes with a restore flow that is meant for moving to a new computer.
AI Agents Backup is available now in the IDrive desktop app for all users, the company says. Gemini CLI, GitHub Copilot, and Windsurf aren’t on the supported list.
The post IDrive wants to back up your coding agents, too appeared first on The New Stack.