How to delete Devin CLI session history, and what you lose

one SQLite database plus a folder of summaries; deleting either is all or nothing

Devin CLI does not write a file per conversation. Every session lives in one SQLite database, and the summaries written when a session is compacted sit in a folder beside it.

Where the sessions are

${XDG_DATA_HOME:-~/.local/share}/devin/cli/sessions.db
${XDG_DATA_HOME:-~/.local/share}/devin/summaries/<session_id>.md

A session is a row of sessions plus its turns in message_nodes; prompt_history holds the shell commands run between turns. The summaries are the only record of what a compaction folded away.

How to delete it

deja delete does not take devin sessions: the database is shared by every session and is live state the client owns. With Devin closed, remove the files yourself:

rm ~/.local/share/devin/cli/sessions.db
rm -r ~/.local/share/devin/summaries

That deletes every session and every summary at once, and there is no archive. Deleting rows instead does not shrink the file, since SQLite reuses the freed pages.

Index first

If you want the history to stay searchable, run deja index before deleting. deja keeps its own copy, so the sessions remain findable with deja "query" and readable with deja show afterwards. deja forget drops a session from the index for good.

deja index
deja resume --write-back <id>

deja resume reopens an indexed session with devin --resume <id> while it is still in sessions.db. --write-back recreates a transcript for the agents that have one; deja does not yet write Devin sessions back into sessions.db, so after deleting it a session is read, not resumed.

What you lose

Devin's own session list reads the same database, so once it is gone the answer to a question you solved last month exists only in deja's index.

Where every agent keeps its history · Memory for Devin · The Devin format

Found this useful? Star deja-vu on GitHub.