- HEARTBEAT.md: 5,297 → 449 bytes (-92%) — current focus only, projects moved to memory/projects-active.md - AGENTS.md: 7,869 → 1,603 bytes (-80%) — core rules only, MCP playbook moved to memory/playbook-mcp.md - SOUL.md: 5,394 → 1,935 bytes (-64%) — same security, fewer words - USER.md: 2,732 → 705 bytes (-74%) — collaborators moved to memory/contacts.md - lessons-learned.md: 27,252 → 3,031 bytes (-89%) — hot universal rules only, rest in lessons-archive.md - 2026-02-15.md: 24,675 → 2,453 bytes (-90%) — compressed, full version in archive/ Total injected tokens: ~5,700 → ~2,000 (65% reduction) Research basis: Stanford 'Lost in the Middle', JetBrains context management study
1.6 KiB
1.6 KiB
AGENTS.md - Clawdbot Workspace
Identity & Profile
- Agent identity: IDENTITY.md | User profile: USER.md
- If BOOTSTRAP.md exists, follow its ritual and delete it.
Safety
- Don't exfiltrate secrets or private data.
- Don't run destructive commands unless explicitly asked.
- Be concise in chat; write longer output to files.
Memory System
- Daily log:
memory/YYYY-MM-DD.md— bullet points only, cap ~5KB/day. On session start, read today + yesterday. - Working state: Update
memory/working-state.mdwhen starting/completing tasks. Read it FIRST after any crash/compaction. - Lessons:
memory/lessons-learned.md(hot) +memory/lessons-archive.md(old). Search before repeating mistakes. - Save often: Append to daily log every ~15 messages or when Jake makes a decision. Don't wait for end of day.
- Compaction is unreliable — proactively save context. If summary fails: read working-state → daily log → channel history → memory search → ask Jake last.
Git Backup
End of day: cd ~/.clawdbot/workspace && git add -A && git commit -m "Daily backup: YYYY-MM-DD" && git push
Model Routing
- Default: Sonnet. Escalate to Opus for architecture, deep research, creative writing, complex debugging.
- Spawn sub-agents on Opus for heavy builds, long code gen, multi-file refactors.
- End replies with
· sonnetor· opus
MCP Work
All MCP work goes to mcpengine-repo/ (BusyBee3333/mcpengine). Before MCP builds, read memory/playbook-mcp.md.
Discord
If lacking context in a conversation, read recent channel messages before asking for clarification.