---
title: "AgentDrive vs CLAUDE.md and handoff notes"
description: "CLAUDE.md and AGENTS.md hold the rules you write for every session. AgentDrive keeps what each session did, so another coding agent can resume it."
canonical: "https://agentdrive.sh/compare/claude-md-handoff-notes"
---
# AgentDrive vs CLAUDE.md and handoff notes

> For the complete documentation index, see [llms.txt](https://agentdrive.sh/llms.txt). Every docs page is also served as markdown at its URL plus `.md`, and the full docs are in one file at [llms-full.txt](https://agentdrive.sh/llms-full.txt).

> CLAUDE.md, AGENTS.md and handoff notes hold what you write down for the next session. AgentDrive keeps what each session did, so another agent can pick it up.

Source: https://agentdrive.sh/compare/claude-md-handoff-notes. Last checked 2026-11-18. All comparisons: https://agentdrive.sh/compare.md.

## When to pick which

Pick CLAUDE.md and handoff notes when: You want standing instructions every session should follow, or a short note for whoever picks up the task next.

Pick AgentDrive when: You switch agents mid-task and want the next one to see what the last session did, without writing it up first.

They cover different jobs: CLAUDE.md or AGENTS.md carries the project rules into every session, and AgentDrive carries the state of the current task from one agent to the next.

| Feature | AgentDrive | CLAUDE.md and handoff notes |
| --- | --- | --- |
| Unit of storage | Sessions and files, versioned, with provenance | Markdown instructions and notes you write |
| Where it runs | Hosted workspace plus a local CLI and MCP server | Read by the agent from disk at session start |
| Coding-agent sessions | Synced by hooks in Claude Code, Codex, OpenCode, Cursor and Antigravity; resumable from any of them | Not recorded; a handoff note is written by you, or by the agent when asked |
| Storage location | AgentDrive R2 by default; your own R2 or S3 bucket on Team | Files in your repo or home directory, shared through git |
| Availability | Free plan; Pro $20/mo, Team $30/seat/mo | CLAUDE.md is built into Claude Code; AGENTS.md is read by Codex, Cursor, OpenCode and others |

## About CLAUDE.md and handoff notes

- CLAUDE.md files are markdown files you write, and Claude Code reads them at the start of every session. Claude treats them as context, not enforced configuration.
- A project CLAUDE.md is shared with your team through version control. ~/.claude/CLAUDE.md holds personal preferences for all projects, and CLAUDE.local.md holds personal notes for one project, kept out of git.
- /init generates a starting CLAUDE.md from your codebase. The docs recommend under 200 lines per file and a periodic review to remove outdated or conflicting instructions.
- Claude Code also keeps auto memory: notes Claude writes itself, loaded at the start of each session (the first 200 lines or 25KB of MEMORY.md). Auto memory is machine-local and not shared across machines.
- Claude Code reads a repository's AGENTS.md in place of CLAUDE.md when the project has no CLAUDE.md.
- AGENTS.md is "a simple, open format for guiding coding agents", for build steps, tests and conventions. Agents read the nearest file in the directory tree, and the closest one takes precedence.
- Codex builds its instruction chain from AGENTS.md files when it starts, from its home directory and from the project root down to the current directory, up to 32 KiB by default (project_doc_max_bytes).

## Who writes it, and when it goes stale

You write CLAUDE.md and AGENTS.md, or have the agent draft one with /init. They stay right until the code or the conventions change and nobody edits them, which is why the Claude Code docs suggest reviewing them for outdated instructions.

A handoff note is written at the end of a session, by you or by the agent when you ask. It holds only what was written down at that moment, and it goes stale as soon as work continues without an update.

An AgentDrive session record is written by the sync, from the agent's own transcript, each time its hooks fire. It describes a past session, so it ages too: the resume brief tells the next agent to check the files on disk before relying on it.

## They work together

Keep rules that every session should follow in CLAUDE.md or AGENTS.md. Let AgentDrive carry the state of one task from agent to agent. The receiving agent loads its own instruction files at startup as usual, then reads the AgentDrive brief to see where the last session stopped.

If an agent writes a handoff note to a file git doesn't track, AgentDrive uploads that file with the session, so the note travels with the transcript.

## Where CLAUDE.md and handoff notes works well

- Standing rules for every session: build and test commands, conventions, architecture decisions.
- Living in the repo and getting reviewed in pull requests like any other file.
- No account and no service: the agent reads a file on disk.

## What AgentDrive does differently

- AgentDrive records what a session did from the agent's transcript: the goal, the files touched and the recent turns. Nobody has to write it up first.
- Hooks in Claude Code, Codex, OpenCode, Cursor and Antigravity sync each session in the background, so the record is as current as the last sync, not the last edit to a note.
- The brief is fetched on demand with drive_resume, one session at a time, instead of growing a file that every agent loads at startup.
- Sessions live in your workspace by project, so you can resume one on another machine signed in to the same account.

## Frequently asked questions

### What is the difference between CLAUDE.md and handoff notes and AgentDrive?

CLAUDE.md, AGENTS.md and handoff notes hold what you write down for the next session. AgentDrive keeps what each session did, so another agent can pick it up.

### When should I use CLAUDE.md and handoff notes?

You want standing instructions every session should follow, or a short note for whoever picks up the task next.

### When should I use AgentDrive instead?

You switch agents mid-task and want the next one to see what the last session did, without writing it up first.

### Can I use AgentDrive alongside CLAUDE.md and handoff notes?

Yes. They cover different jobs: CLAUDE.md or AGENTS.md carries the project rules into every session, and AgentDrive carries the state of the current task from one agent to the next.

## Sources

- https://code.claude.com/docs/en/memory
- https://agents.md/
- https://learn.chatgpt.com/docs/agent-configuration/agents-md

