TeleAgent session history, and what deja does with it

one OpenCode-schema SQLite store per account

TeleAgent (星辰超级智能体, the China Telecom TeleAI desktop client) keeps one SQLite database per account.

Where the sessions are

~/.local/share/TeleAgent/users/<account>/teleagent.db
${XDG_DATA_HOME}/TeleAgent/users/<account>/teleagent.db
${TELEAGENT_HOME}/users/<account>/teleagent.db

The same three tables as opencode: session / session_v2, message, and part (or session_message).

How to delete it

The client has no CLI of its own, so there is no per-session delete command to call. With the client closed, removing an account's database removes that account's entire history:

rm ~/.local/share/TeleAgent/users/<account>/teleagent.db

deja delete refuses write-back for TeleAgent for the same reason it does for MiMo-Code: the index holds none of the row ids the store needs.

Keeping it searchable instead

deja reads these stores through sqlite3 — along with the other fifty-one agents' histories on the machine — into one local index:

curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh
deja "teleagent session about the retry budget"

Where every agent keeps its history · TeleAgent sessions in deja-vu · The TeleAgent format

Found this useful? Star deja-vu on GitHub.