TeleAgent sessions in deja-vu

星辰超级智能体's per-account SQLite stores under ~/.local/share/TeleAgent

TeleAgent (星辰超级智能体, the China Telecom TeleAI desktop client) keeps one OpenCode-schema SQLite store per account under ~/.local/share/TeleAgent/users/<account>/teleagent.db (relocated by TELEAGENT_HOME, replaced outright by DEJA_TELEAGENT_ROOT). Its tables use OpenCode's message schema unchanged, so deja reads sessions through the same SQLite reader it uses for MiMo-Code — see where history lives.

The same question put to the same agent twice: without memory it has no record of it, with deja it answers with the decision from eight months earlier

same prompt before and after deja — local BM25 recall across past sessions on disk, zero LLM calls

What deja does with it

Nothing to install: the desktop client exposes no config directory, MCP client, skill catalogue, user-definable slash commands, or CLI prompt, so there is no recall surface to wire. The stores are indexed like every other harness — sessions from every account are searchable from deja itself, from the MCP server, and from every other agent deja serves.

The part that is not about this harness

The index covers every agent's transcripts on the machine — fifty-two of them today, each in its own format — so a fix found in Claude Code or Codex answers a question asked in TeleAgent, and the reverse. Indexing and search stay local, and credentials are stripped as the index is built.

Repository memory & handoff

Share vetted project decisions and dead ends through git in .deja/memory.jsonl (deja repo candidates, deja repo add <id>). Entries are redacted on write, stored sorted with merge=union so parallel branches merge cleanly, and loaded for any teammate who clones the repository. See repo memory.

The client has no CLI prompt, so deja handoff --to teleagent prints the digest to paste into a new conversation rather than exec'ing a command.

Getting started · Switching between agents · The TeleAgent session format

Found this useful? Star deja-vu on GitHub.