How tropicron per-job memory works
Scanned 5/27/2026
Install via CLI
Skills Directoryopenskills install pforret/TropicClaw---
name: tropicron-memory
description: How tropicron per-job memory works
user-invocable: false
---
## Per-Job Memory
Each tropicron job can have a `<job>.memory.md` sibling file for persistent context.
- When `memory: true` in frontmatter, the memory file is prepended to the prompt
- Claude is instructed to update the memory file with important findings
- Memory files are gitignored (runtime state, not config)
- Keep memory files concise (<100 lines) — summarize, don't accumulate
### Memory file location
`<job>.memory.md` lives next to `<job>.md` in `.claude/tropicron/jobs/`
### What to store in memory
- Last-seen values, counters, dates
- Recurring patterns discovered across runs
- User preferences learned from feedback
- Errors to avoid on future runs
- State that should persist (e.g., "last email checked: 2026-02-25")
No comments yet. Be the first to comment!
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
