Skip to main content
Deep Agents Code stores data in two directory hierarchies:
  • ~/.deepagents/ — Deep Agents-specific data (agent memory, skills, sessions)
  • ~/.agents/ — Tool-agnostic data (skills shared across AI CLI tools)

Directory structure

What goes where

Precedence rules

When the same item exists in multiple locations, higher precedence wins completely (no merging).

Skills

Precedence order (lowest to highest):
  1. ~/.deepagents/{agent}/skills/ — User Deep Agents Code
  2. ~/.agents/skills/ — User tool-agnostic
  3. .deepagents/skills/ — Project Deep Agents Code
  4. .agents/skills/ — Project tool-agnostic (highest)
When a skill is loaded, Deep Agents Code verifies that the resolved file path stays within one of these directories. Symlinks that resolve outside all skill roots are rejected. To allow symlink targets in additional directories, see [skills].extra_allowed_dirs.

Subagents

Precedence order (lowest to highest):
  1. ~/.deepagents/{agent}/agents/ — User-level
  2. .deepagents/agents/ — Project-level (highest)
Each subagent is an AGENTS.md file with YAML frontmatter (name, description, optional model) and a markdown body for the system prompt. See Use subagents in Deep Agents Code for the full format reference.

Instructions

All instruction sources are combined (not overridden):
  1. Package base prompt (always loaded)
  2. ~/.deepagents/{agent}/AGENTS.md (appended)
  3. .deepagents/AGENTS.md (appended)
  4. AGENTS.md at project root (appended)

.deepagents vs .agents

Use .agents/skills/ for skills that work with any AI coding assistant. Use .deepagents/skills/ for skills that rely on Deep Agents-specific tools or conventions.

Cleaning up

Deleting ~/.deepagents/.state/sessions.db will remove all conversation history and checkpoints.This cannot be undone unless you have a backup of the sessions.db file.