add-compact

Route the /compact slash command through NauggieClaw to summarize session context.

1|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jboothomas/nauggieclaw --skill add-compact-jboothomas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-compact
Source: https://github.com/jboothomas/nauggieclaw/tree/main/.claude/skills/add-compact
Command: npx skills add https://github.com/jboothomas/nauggieclaw --skill add-compact-jboothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running Auggie sessions suffer from context rot as the conversation history grows, making the agent lose focus and recall. This skill routes the built-in /compact slash command through NauggieClaw to retain a concise memory without resetting the session.

Core Features & Use Cases

  • Manual Compaction Control: Trusted main-group or device-owner messages trigger SDK compaction without destructive resets, keeping the agent responsive in extended conversations.
  • Authorization and Safety: Session commands require admin access outside the main group, avoid untrusted container interruptions, and consume denied commands to prevent replay attacks.
  • Operational Guidance: Provides git fetch/merge, build, and restart steps plus verification scenarios so operators can validate compaction behavior from different user contexts.

Quick Start

Send /compact from your main group to trigger the SDK compaction while keeping the session alive with summarized context.

Frequently Asked Questions about add-compact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compact conversation history in long-running Auggie agent sessions?

You can compact conversation history by triggering the manual /compact slash command. This routes SDK compaction through NauggieClaw to summarize context and fight context rot while keeping the same logical session alive.

What causes context rot in extended Auggie deployments and how does session compaction help?

Context rot occurs in extended Auggie deployments as conversation history grows, causing the agent to lose focus and recall. Session compaction summarizes this history to retain concise memory without destructive session resets.

Can I trigger session compaction from outside the main group in NauggieClaw?

Session compaction requires admin access to trigger outside the main group. Authorization checks prevent untrusted container interruptions and consume denied commands to prevent replay attacks against the agent context.

How do I verify that manual compaction keeps the same logical conversation alive?

You can verify compaction behavior by running provided operational scenarios from different user contexts. The process relies on SDK newSessionId handling to ensure compaction keeps the same logical conversation active.

What are the steps to deploy manual /compact commands for container orchestration sessions?

Deployment involves git fetch/merge, build, and restart steps. Operators then validate compaction behavior using provided verification scenarios to ensure session command routing and authorization checks function correctly.

When should I avoid using a manual compaction slash command for agent context?

You should avoid manual compaction when untrusted containers could send interruptions. The system consumes denied commands to prevent replay attacks, ensuring only trusted main-group or device-owner messages trigger SDK compaction.