Mobile Context Compression

Overview

Reduce token usage by maintaining a compact context pack, using delta-only communication, and loading only the minimum required files for each step.

Workflow

1. Build a context pack first

• Run scripts/context_pack.sh <repo_root> at task start.
• Keep only: goal, constraints, active files, decisions, open questions, and verification state.

2. Apply delta-only updates

• In each reply, report only what changed since the previous update.
• Avoid repeating unchanged background, logs, or rationale.
• Use short references to files and commands instead of verbose restatement.

3. Use targeted file access

• Prefer rg for specific symbols/paths before opening full files.
• Open the smallest relevant file sections.
• Avoid bulk scans unless the task explicitly requires broad discovery.

4. Keep output budgeted

• Default to concise outputs unless user asks for deep detail.
• Prefer compact structures: decision, blockers, next action.
• Compress command results into high-signal facts.

5. Preserve quality under compression

• Never skip verification evidence.
• Keep assumptions explicit.
• If compression risks ambiguity, add one short clarifying line rather than long prose.

Response Template

Use this compact format when context is large:

## Context Pack
- Goal:
- Scope now:
- Decisions locked:
- Open risks:
- Next action:

## Delta
- Changed since last update:
- Evidence:

Guardrails

• Do not claim success without fresh verification.
• Do not drop critical constraints when compressing.
• Prefer correctness over brevity when they conflict.

Resources

• Use scripts/context_pack.sh <repo_root> to generate a compact workspace summary.
• Use references/compression-rules.md when choosing what to keep vs omit.