You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,19 @@ Prefer exact matches, then workspace files, then the newest readable file. Ask f
20
20
21
21
For remote files: use `crawlberg` to download first, then pass the resulting local file to `xberg`.
22
22
23
+
# Project Memory
24
+
25
+
Use the Qdrant MCP server as durable, project-scoped memory for non-trivial work.
26
+
27
+
1. Recall: before planning or editing, call `qdrant-find` with a concise semantic query containing the current goal plus relevant errors, components, or symbols. If Qdrant is unavailable or returns no useful result, continue without blocking the task.
28
+
2. Validate: treat recalled memory as a lead, not as authority. Confirm it against the current repository, configuration, tests, and user request; current evidence wins whenever memory is stale or conflicting.
29
+
3. Persist: after successful verification, call `qdrant-find` once more to avoid duplicates, then use `qdrant-store` only for new durable knowledge such as architectural decisions, project conventions, confirmed fixes, recurring pitfalls, or reliable commands.
30
+
31
+
- Store one self-contained fact per memory, including enough rationale or evidence to make it useful in a future session.
32
+
- Add compact metadata when useful, such as `type`, `component`, and `source`; do not rely on metadata instead of clear memory text.
33
+
- Do not store transient progress, full conversation summaries, speculative conclusions, raw logs, large code blocks, generated artifacts, secrets, credentials, tokens, or personal data.
34
+
- Do not persist a memory until the relevant change or conclusion has been validated. If a previous memory is wrong, follow current repository evidence and store a clearly labeled correction only when it will prevent recurrence.
35
+
23
36
# Python Scripting
24
37
25
38
- Use `uv` for execution, dependencies, environments, and tools: `uv run`, `uv add`, `uv sync`, and `uv tool run`. Preserve another workflow only when the project explicitly standardizes on it.
0 commit comments