sbusso

Add /compact command for manual context compaction. Solves context rot in long sessions by forwarding the SDK's built-in /compact slash command. Main-group or trusted sender only.

Add image vision to ClaudeClaw agents. Resizes and processes WhatsApp image attachments, then sends them to Claude as multimodal content blocks.

Add Ollama MCP server so the container agent can call local models for cheaper/faster tasks like summarization, translation, or general queries.

Add PDF reading to ClaudeClaw agents. Extracts text from PDFs via pdftotext CLI. Handles WhatsApp attachments, URLs, and local files.

Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

Switch from Docker to Apple Container for macOS-native container isolation. Use when the user wants Apple Container instead of Docker, or is setting up on macOS and prefers the native runtime. Triggers on "apple container", "convert to apple container",…

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.

Efficiently bring upstream ClaudeClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.

Use when the user explicitly authorizes Git or publication actions: verify repository state, then commit, push, open a pull request, tag, release, or deploy only as authorized.

Use for non-trivial unexpected behavior or reported defects that require causal investigation: reproduce the issue, trace the real path, and isolate the root cause before an authorized fix.

Use when a substantive development request has meaningful solution uncertainty: trace real flows, compare genuinely different approaches, and choose a direction. Skip when the path is already clear.

Use for substantive code changes where a structured build loop adds value. Implement the approved request or plan with proportionate verification; skip for trivial edits.

Use when complexity, risk, or multiple dependent units justify a durable implementation plan. Skip for small, already-clear changes.

Use when the user requests a review or when change risk justifies an independent verification pass: run real checks and assess correctness, security, and regressions.

Use when the user explicitly authorizes Git or publication actions: verify repository state, then commit, push, open a pull request, tag, release, or deploy only as authorized.

Use for non-trivial unexpected behavior or reported defects that require causal investigation: reproduce the issue, trace the real path, and isolate the root cause before an authorized fix.

Expert debugging methodology. Triggers on debug, investigate, fix bug, troubleshoot.

Enforces development phases. Triggers on implement, build, create, fix, refactor.

Install the Continuous Improvement system (backlog, weekly review, journal loop with hooks and skills) into a project. Use whenever the user asks to install, port, bootstrap, replicate, or hand over the improvement system, the CI loop, or the product…