docs(agents): store memories in cognee proactively, route team-IT to team bucket
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BFaWee4G42cmTCCAFRTtcB
This commit is contained in:
parent
abc654d753
commit
8c7300e899
1 changed files with 15 additions and 0 deletions
|
|
@ -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
|
user meant — don't bundle the tangent into the active task as if it were
|
||||||
direction.
|
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
|
## Sandbox
|
||||||
|
|
||||||
- **Always run commands sandboxed first.** Only use `dangerouslyDisableSandbox: true` as a last resort after a sandbox-related failure — never preemptively.
|
- **Always run commands sandboxed first.** Only use `dangerouslyDisableSandbox: true` as a last resort after a sandbox-related failure — never preemptively.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue