From 8c7300e899c02117d43a902d9302c4b1fcce6e59 Mon Sep 17 00:00:00 2001 From: mwiegand Date: Thu, 23 Jul 2026 17:31:13 +0200 Subject: [PATCH] docs(agents): store memories in cognee proactively, route team-IT to team bucket Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01BFaWee4G42cmTCCAFRTtcB --- agents/AGENTS.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/agents/AGENTS.md b/agents/AGENTS.md index 9281881..15d2676 100644 --- a/agents/AGENTS.md +++ b/agents/AGENTS.md @@ -50,6 +50,21 @@ Treat vague input and question-back responses critically, not as instructions. user meant — don't bundle the tangent into the active task as if it were direction. +## Team memory (cognee) + +- **Store memories in cognee aggressively and on your own** (skill `cognee`) — + announce it briefly, don't ask first. Save solved problems, decisions, + reusable infra facts, and lessons learned as soon as they emerge. +- **Routing:** anything concerning team IT (Seibert IT-Infra — ISAC/bw, + monitoring, INFRA-Board, shared services, servers, team processes) goes to + the team bucket via `remember --team`. Everything else (personal + preferences, workflow feedback, context only relevant to me) goes to the + personal dataset (plain `remember`). +- Before deep-diving a larger task or a recurring-looking problem, `recall` + relevant prior knowledge first. +- Avoid duplicates: on recurring topics `recall` before saving; never store + secrets, credentials, or customer-personal data. + ## Sandbox - **Always run commands sandboxed first.** Only use `dangerouslyDisableSandbox: true` as a last resort after a sandbox-related failure — never preemptively.