AIHype

Like yes | ai - auto-approve AI agent prompts with blacklist protection.

TL;DR

# Demo: Bash blocks on read, aihype auto-answers, proceeds
aihype bash -c 'read -p "Deploy? (y/n) " x && echo "→ $x"'
# Without aihype: hangs forever waiting for input
# With aihype: auto-answers "yes", continues execution

What It Does

AIHype wraps command-line tools that ask for approval, spawning them via PTY and automatically responding to prompts like "Do you want to proceed? (y/n)" with "yes". Dangerous prompts matching blacklist rules get "no" instead, with AI-powered evaluation.

Perfect for:

Automating interactive CLIs without modification
CI/CD pipelines with confirmation prompts
Controlling AI assistants (Claude, Gemini, etc.)
Protecting against dangerous operations

Integration Tests (Real-World Verification)

IMPORTANT: We provide real integration tests that verify aihype works with actual Claude CLI, not mocks.

Running Integration Tests

# Set your API key
export ANTHROPIC_API_KEY=sk-ant-...

# Run all integration tests (2-3 minutes, costs apply)
./samples/00-verify-all.sh

# Or run individual tests:
./samples/01-api-key-approval.sh      # Basic Claude integration
./samples/02-deployment-confirmation.sh # Multi-step workflow
./samples/03-blacklist-denial.sh       # Security (CRITICAL)
./samples/04-multi-prompt-sequence.sh  # Long output streaming

What These Tests Verify

✅ Real Claude CLI integration - Actual Claude process via API (tests 1, 2, 4) ✅ PTY process spawning and control - Full process lifecycle management ✅ Output streaming - Multi-paragraph responses flow correctly through PTY ✅ Interactive prompt handling - Mock-claude tests y/n prompts (test 3) ✅ Blacklist security - Dangerous prompts are denied, safe ones approved (CRITICAL) ✅ Claude --print mode - Non-interactive automation mode (real-world CI/CD usage)

These tests are your "gut check" - if they pass, aihype works in the real world.

Test Requirements

ANTHROPIC_API_KEY: Must be set (tests hit real API)
claude CLI: Must be installed (npm install -g @anthropic-ai/claude-code)
Reasonable timeouts: 30-60s per test (API latency)
Conservative rate limits: 5s delay between tests
Real costs: API calls cost money (minimal, but real)

Understanding Test Output

Each test shows:

✓ Prerequisites verified
Expected behavior description
Actual command output with [AIHype] logging
Success/failure with detailed diagnosis

If a test fails, it tells you exactly what went wrong:

Process spawning issues?
Output streaming problems?
Blacklist not working?
API call failed?

How It Works

Process Control via PTY:

aihype <command> [args]
  ↓
Spawns command as child process via PTY
  ↓
Reads child's output, detects prompts
  ↓
Evaluates against blacklist via AI
  ↓
Writes "yes" or "no" to child's stdin
  ↓
Child continues with response

NOT a pipe filter - aihype actually controls the child process.

Installation

bundle install

Quick Start

# Initialize configuration
./bin/aihype init

# Run any interactive tool through aihype
./bin/aihype your-tool --with-args

# Set your Anthropic API key for AI-powered blacklist matching
export ANTHROPIC_API_KEY=your_key_here

Real Examples

Control Mock Claude

# Create a test config
cat > test.yml <<'EOF'
sequence:
  - type: output
    text: "Starting deployment..."
  - type: prompt
    text: "Do you want to proceed? (y/n)"
    expect: ["y", "yes", "n", "no"]
    if_yes: "Proceeding..."
    if_no: "Cancelled."
  - type: output
    text: "Done!"
EOF

# Run with aihype
./bin/aihype ./bin/mock-claude test.yml

Output:

Starting deployment...
Do you want to proceed? (y/n)
yes                           ← Auto-answered!
Proceeding...
Done!

Security: Blacklist Protection

# Test with dangerous prompts
./bin/aihype ./bin/mock-claude test/fixtures/dangerous_prompts.yml

Output:

Do you want to enable automatic backups? (y/n)
yes                           ← APPROVED ✅

Should I charge your credit card $500? (yes/no)
no                            ← DENIED ⛔
[AIHype] WARNING: DENIED: Should I charge your credit card $500?
(matched rule: Never use the credit card)

Payment cancelled.

Control Real Claude

# AIHype controls Claude and auto-answers its prompts
export ANTHROPIC_API_KEY=your_key
./bin/aihype claude -p prompt.md

Configuration

Blacklist Rules

Edit memory/aihype.md to customize your blacklist rules:

---
version: 1.0.0
created: 2025-10-02T00:00:00Z
updated: 2025-10-02T00:00:00Z
---

# AIHype Blacklist Rules

## Default Safety Rules
- Never execute rm -rf / or similar destructive filesystem operations
- Never modify critical system files (/etc/passwd, /boot/, /etc/shadow)
- Never disable security features or firewalls

## User Rules
- Never use the credit card
- Never delete production databases
- Never install code sponsored by shopify

Environment Variables

# API Configuration
export ANTHROPIC_API_KEY=your_key_here          # Required for AI matching
export AIHYPE_MODEL=claude-3-5-sonnet-20241022  # Override model selection
export AIHYPE_MODEL_PREFERENCE=cheap            # fast, cheap, balanced, powerful
export AIHYPE_API_TIMEOUT=5                     # API timeout in seconds

# Rate Limiting
export AIHYPE_RATE_LIMIT_RPM=50                 # Requests per minute (default: 50)
export AIHYPE_RATE_LIMIT_WINDOW=60              # Window size in seconds (default: 60)

# Paths
export AIHYPE_CONFIG=memory/aihype.md           # Config file path
export AIHYPE_LOG=memory/aihype.log             # Log file path

# Logging
export AIHYPE_VERBOSE=1                         # Enable verbose logging

Commands

Spawn and Control a Command (default)

# AIHype spawns the command and controls it via PTY
./bin/aihype <command> [args...]

# Examples:
./bin/aihype mock-claude config.yml
./bin/aihype claude -p prompt.md
./bin/aihype deployment-script.sh --production

Initialize Config

# Create default memory/aihype.md configuration
./bin/aihype init

Validate Config

# Validate memory/aihype.md configuration
./bin/aihype validate

Output:

Configuration is valid
  Version: 1.0.0
  Default rules: 3
  User rules: 2
  Total enabled rules: 5

Options

./bin/aihype --help              # Show help
./bin/aihype --version           # Show version
./bin/aihype --config PATH cmd   # Custom config path
./bin/aihype --log PATH cmd      # Custom log path
./bin/aihype --verbose cmd       # Enable verbose logging

Architecture

┌──────────────────────────────────────────────┐
│ aihype <command> [args]                      │
└────────────────┬─────────────────────────────┘
                 │
                 ▼
┌────────────────────────────────────────────────┐
│ PTY.spawn(command, args)                       │
│   - Spawns child process                       │
│   - Creates pseudo-terminal                    │
│   - Controls child's stdin/stdout              │
└──────────┬─────────────────────┬───────────────┘
           │                     │
           │ stdout              │ stdin
           ▼                     ▲
┌──────────────────┐    ┌────────────────────┐
│ Read child       │    │ Write responses    │
│ output           │    │ to child           │
│ (detect prompts) │    │ ("yes" or "no")    │
└────┬─────────────┘    └─────────▲──────────┘
     │                            │
     │                            │
     ▼                            │
┌─────────────────────────────────┴──────────┐
│ Prompt detected?                           │
│  → Yes: Evaluate against blacklist         │
│     → Match: respond "no" (DENIED)         │
│     → No match: respond "yes" (APPROVED)   │
│  → No: Pass through to stdout              │
└────────────────────────────────────────────┘

Real-World Use Cases

1. Control AI assistants

# AIHype controls Claude and auto-approves safe operations
./bin/aihype claude -p "deploy to staging"

2. Automate deployment scripts

# Your deploy script asks for confirmations, aihype answers them
./bin/aihype ./deploy.sh --prod

3. CI/CD pipelines

# In your CI config:
- run: aihype ./deployment-tool.sh

4. Protect against dangerous operations

# AIHype denies prompts about:
# - Deleting production data
# - Using credit cards
# - Disabling security
# - Any custom blacklist rules
./bin/aihype dangerous-script.sh

Development

# Install dependencies
bundle install

# Run tests
bundle exec rake test

# Run specific test
ruby -Ilib -Itest test/unit/test_core.rb

# Run integration tests (requires ANTHROPIC_API_KEY)
ANTHROPIC_API_KEY=your_key ./samples/00-verify-all.sh

Testing

Unit Tests (Fast, No API)

# Run all unit tests (minitest)
bundle exec rake test

# Tests mock-claude interactions
# No API key needed, runs offline

Integration Tests (Slow, Real API)

# Run full integration suite with real Claude
export ANTHROPIC_API_KEY=your_key
./samples/00-verify-all.sh

# Takes 3-5 minutes, hits real API
# This is your "does it actually work?" test

Test coverage:

✅ PTY process spawning and control
✅ Prompt detection and pattern matching
✅ Blacklist rule evaluation with real AI
✅ Response writing to child process stdin
✅ Integration tests with mock-claude
✅ Real-world tests with actual Claude CLI
✅ Security denials

Key Features

✅ Process control via PTY - actually spawns and controls child processes ✅ Auto-answers approval prompts with "yes" ✅ AI-powered blacklist protection denies dangerous actions ✅ Real stdin/stdout control - not a pipe filter ✅ Works with ANY interactive tool - Claude, deploy scripts, installers, etc. ✅ Configurable rules via markdown file ✅ Rate limiting for API calls ✅ Dynamic model selection from Anthropic API ✅ Graceful fallback when API unavailable ✅ Real-world verification via integration tests

Mock Claude for Testing

AIHype includes mock-claude, a configurable test CLI that simulates interactive tools:

# Create a test scenario
cat > scenario.yml <<'EOF'
sequence:
  - type: output
    text: "Starting process..."
  - type: prompt
    text: "Continue? (y/n)"
    expect: ["y", "n"]
    if_yes: "Continuing..."
    if_no: "Stopped."
  - type: output
    text: "Done!"
EOF

# Test with aihype
./bin/aihype ./bin/mock-claude scenario.yml

See test/fixtures/*.yml for more examples.

Limitations

Claude AI Output Behavior: Claude AI (via claude -p) outputs text and exits - it does not generate blocking interactive prompts that wait for user input. AIHype works perfectly with Claude for process control and output streaming, but there are no prompts to auto-answer in non-interactive mode.

Interactive Prompts: To demonstrate auto-prompt-answering, use tools that actually generate blocking prompts:

bash -c 'read -p "Continue? " x' - Blocks on read
rm -i file - Interactive confirmation
mock-claude - Simulated interactive tool for testing

Real-World Value: AIHype's primary use cases are:

Wrapping deployment scripts with confirmation prompts
Automating interactive CLI tools (rm -i, apt-get, etc.)
Process control and logging for AI agents
Blacklist security for any command-line tool

Technical Documentation

PTY and Terminal Automation Analysis - Deep dive on why PTY approach is correct for Ink-based CLIs

License

See LICENSE file for details.

Author

See gemspec for author information.

aihype

Runtime

AIHype

TL;DR

What It Does

Integration Tests (Real-World Verification)

Running Integration Tests

What These Tests Verify

Test Requirements

Understanding Test Output

How It Works

Installation

Quick Start

Real Examples

Control Mock Claude

Security: Blacklist Protection

Control Real Claude

Configuration

Blacklist Rules

Environment Variables

Commands

Spawn and Control a Command (default)

Initialize Config

Validate Config

Options

Architecture

Real-World Use Cases

1. Control AI assistants

2. Automate deployment scripts

3. CI/CD pipelines

4. Protect against dangerous operations

Development

Testing

Unit Tests (Fast, No API)

Integration Tests (Slow, Real API)

Key Features

Mock Claude for Testing

Limitations

Technical Documentation

License

Author