Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for deja-vu

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to deja-vu.

Most discussed

deja mcp outlives its client on Windows when another process inherited its stdin pipe handle

On Windows 11, four deja mcp processes were still running with parent PIDs that no longer existed. They sat blocked and had to be stopped by hand. Earlier the same day a Codex desktop restart had reaped ~23 servers cleanly, so most exits work; these four stayed. The machine's MCP clients (Claude Code, Codex, grok CLI) are all registered with the cmd /c deja mcp entry that deja install writes on Windows (mcpCommandArgs, cmd/deja/install.go). They also run hooks, which on Windows means a s

Read the thread · 2026-08-28 · closed · outside contributor · 1 comment

install adds a second registration when the server is already wired under another name, and doctor cannot see the pair

Found while preparing #2260, on the same setup: both ~/.claude.json and Codex's config.toml carried two MCP registrations for the same deja binary — one named deja, one named deja-vu, sha256-identical command, identical args (v0.17.0 at the time). Every session started the server twice, carried the six-tool schema twice (mcp__deja__* and mcp__deja-vu__* side by side), and got the server instructions injected twice. deja doctor reported everything wired and healthy.

How the `de

Read the thread · 2026-08-28 · closed · outside contributor · 1 comment

First-class CLI-only path: agent skill for deja search --json, without MCP or hooks

Problem

deja already has a complete local CLI (deja search, deja show, deja blame, --json, --re, --harness, --since). That is enough for the ctx-shaped workflow: install a binary, index what is already on disk, let agents search history on demand.

The documented default path is different. Getting started leads with deja install --auto / --all, marketplace plugins, and the official deja-history skill. That skill only names the six MCP tools (recall, recall_context, `b

Read the thread · 2026-08-18 · closed · external user · 1 comment

doctor: MCP wiring check misses servers registered under a name other than "deja"

Setup: Windows 11, deja built from main at 98b43e1 (v0.15.7). The MCP server has been wired into Claude Code since 0.12.x, registered manually in ~/.claude.json under the key deja-vu.

deja doctor says:

MCP wiring:
  claude-code  not wired      guidance missing     C:\Users\<user>\.claude.json

The server is running and answers recall/remember calls daily, so this is a false negative. Cause: doctorJSONWired in cmd/deja/doctor.go checks for a server literally named "deja" under t

Read the thread · 2026-07-26 · closed · outside contributor · 0 comments

recall_context returns a header-only digest for multi-word queries

What happens

MCP recall_context (and deja context <query> on the CLI) can return just the header line with no digest body:

# deja context: claude · apps\playground · b5351d10-… · updated 2026-07-19

Observed on v0.12.0 (Windows 11, real corpus): recall finds the session fine, but recall_context with the query Turso Platform API rotate token Vercel returned only the header. Re-querying the same session with a token that literally appears in one message (`filter-repo raw/tra

Read the thread · 2026-07-19 · closed · outside contributor · 0 comments

Add support for qwen-code (@qwen-code/qwen-code)

Summary

qwen-code (npm: @qwen-code/qwen-code, binary qwen) is a Claude Code–style coding agent CLI from Alibaba/Qwen. It is not in the list of 8 supported harnesses, so deja does not index its history even though it is stored locally and accumulates quickly (I have 876 sessions / 553 MB that deja currently ignores).

It should be straightforward to support because the on-disk layout and JSONL schema are very close to the existing Claude Code reader.

Where the logs live

~

[Read the thread](https://github.com/vshulcz/deja-vu/issues/117) · 2026-07-17 · closed · external user · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/vshulcz/deja-vu/issues).