Quick Start
CLI Usage
Output Formats
Human-Readable (context.txt)
JSON (context.json)
Update Frequency
| Frequency | Trigger | Use Case |
|---|---|---|
turn | After each user/assistant turn | General monitoring |
tool_call | Before/after each tool call | Debug tool output growth |
manual | Only via /context dump | On-demand inspection |
overflow | When budget exceeded | Alert-based |
Sensitive Data Redaction
By default, sensitive data is redacted in snapshots:- API keys (
sk-,api_key, etc.) - Passwords
- Tokens
- Connection strings
Multi-Agent Monitoring
Safety Features
- Opt-in by default: Monitoring is disabled unless explicitly enabled
- Redaction: Sensitive data redacted by default
- Atomic writes: Uses temp file + rename to prevent corruption
- Respects ignore rules: Honors
.praisonignorefor file content
Configuration
Environment Variables
How It Works
Best Practices
Enable only while debugging
Enable only while debugging
Context monitors add I/O overhead — disable in production unless you need audit trails.
Choose human vs JSON format deliberately
Choose human vs JSON format deliberately
Human snapshots are for local debugging; JSON suits automated diffing in CI.
Redact before sharing snapshots
Redact before sharing snapshots
Review files before attaching them to tickets — secrets should appear as
[REDACTED].Snapshot on overflow events
Snapshot on overflow events
Capture state when compaction triggers to reproduce what the model actually saw.
Related
Context Management
Overview of context management
Context Optimizer
Reduce context size automatically

