Skip to content
groundedby
Waitlist

Cline

Where Cline stores your task history

Cline v4 and the Cline CLI keep sessions in ~/.cline/data, with older tasks in VS Code's globalStorage. Where each lives, and how to resume, export and delete them.

Updated October 29, 2026 // Markdown

Quick factsas of October 2026 (extension v4.1.26, CLI v3.0.74)
Made by
Cline (open source)
History lives in
  • v4 and CLI~/.cline/data/sessions/<id>/<id>.messages.json
  • Index~/.cline/data/db/sessions.db
  • Before v4<VS Code globalStorage>/saoudrizwan.claude-dev/tasks/<taskId>/
Format
JSON messages with a SQLite index
Kept for
No automatic deletion documented
Resume
cline --id <id> (CLI), History view (extension)
Cloud copy
Local by default; optional Cline Cloud sessions

Cline, the open-source coding agent for VS Code and the terminal, moved its storage in v4.

Where the files are

v4 extension and the Cline CLI:

~/.cline/data/
├── db/sessions.db                      # SQLite index of sessions
└── sessions/<id>/<id>.messages.json    # one folder per session

On Windows: C:\Users\<user>\.cline\data. CLINE_DATA_DIR or --data-dir moves it.

Before v4 (still readable, no longer written): VS Code's globalStorage, under saoudrizwan.claude-dev/tasks/<taskId>/, with api_conversation_history.json, ui_messages.json and task_metadata.json per task. Older files use Anthropic's message format and track tokens and cost per task.

Resume, export and delete

In the extension, the History view resumes, deletes or clears tasks (favorites are kept).

With the CLI:

cline history [--json]
cline --id <id>                          # resume
cline history export <id> -o task.html
cline history delete --session-id <id>

Privacy notes

Sessions are local unless you use Cline Cloud sessions (ids starting ses-). Enterprise prompt storage backs up to the customer's own bucket.

The groundedby evaluator does not read Cline sessions yet.

Questions

Where does Cline save tasks?+

Since v4, in ~/.cline/data - an index at db/sessions.db and one folder per session under sessions/. Tasks from before v4 stay in VS Code's globalStorage under saoudrizwan.claude-dev/tasks, and are read-only.

How do I export a Cline session?+

With the CLI, cline history export <id> -o session.html. In the extension, export opens the task's folder.

Sources

  1. Cline source, storage paths
  2. Cline docs, CLI reference

Waitlist

Your sessions, your call.

We are building an opt-in marketplace where developers license redacted sessions they pick, one by one. Join to hear first.

Your email and the side you picked. Nothing else. Privacy