Cli Yes! Claude/Gemini/Cursor/Copilot/Qwen

A wrapper tool that automates interactions with various AI CLI tools by automatically handling common prompts and responses. Originally designed for Claude CLI, now supports multiple AI coding assistants.

⚠️ Important Security Warning: Only run this on trusted repositories. This tool automatically responds to prompts and can execute commands without user confirmation. Be aware of potential prompt injection attacks where malicious code or instructions could be embedded in files or user inputs to manipulate the automated responses.

Features

• Multi-CLI Support: Works with Claude, Gemini, Codex, Copilot, and Cursor CLI tools
• Auto-Response: Automatically responds to common prompts like "Yes, proceed" and "Yes"
• Continuous Operation: Keeps the AI assistant running until your task is done, waiting for your next prompt
• Interactive Control: You can still queue more prompts or cancel executing tasks with ESC or Ctrl+C
• Crash Recovery: Automatically restarts crashed processes (where supported)
• Idle Detection: Optional auto-exit when the AI becomes idle

Prerequisites

Install the AI CLI tool(s) you want to use:

Claude

npm install -g @anthropic-ai/claude-code

Learn more: https://www.anthropic.com/claude-code

Gemini

# Install Gemini CLI (if available)
# Check Google's documentation for installation instructions

Codex

# Install Codex CLI (if available)
# Check Microsoft's documentation for installation instructions

GitHub Copilot

# Install GitHub Copilot CLI
# Check GitHub's documentation for installation instructions

Cursor

# Install Cursor agent CLI
# Check Cursor's documentation for installation instructions

Grok

npm install -g @vibe-kit/grok-cli

Learn more: https://github.com/vibe-kit/grok-cli

Then install this project:

npm install cli-yes -g

Usage

Command Line Interface

claude-yes [--exit-on-idle=60s] [tool-command] [prompts]

Examples

Claude (default):

claude-yes -- run all tests and commit current changes
bunx claude-yes "Solve TODO.md"

Other AI tools:

# Use Codex directly
codex-yes -- refactor this function

# Use Grok directly
grok-yes -- help me with this code

# Use Copilot directly
copilot-yes -- generate unit tests

# Use Cursor directly
cursor-yes -- optimize performance

# Use Gemini directly
gemini-yes -- debug this code

claude-yes "help me with this code"
claude-yes "optimize performance"

Auto-exit when idle (useful for automation):

claude-yes --exit-on-idle=60s "run all tests and commit current changes"

Alternative with claude-code-execute:

claude-code-execute claude-yes "your task here"

Supported CLI Tools

The tool will:

1. Run the specified AI CLI tool
2. Automatically respond "Yes" to common yes/no prompts
3. Handle tool-specific patterns and responses
4. When using --exit-on-idle flag, automatically exit when the tool becomes idle

CLI Tools Comparison

Pros & Cons Analysis

Claude Code CLI (Anthropic)

Pros:

• Industry-leading performance on SWE-bench (72.5%) and Terminal-bench (43.2%)
• Advanced checkpointing feature for code state management
• Deep terminal integration with Unix philosophy support
• Enterprise-ready with AWS/GCP deployment options
• Excellent at complex refactoring and debugging tasks

Cons:

• Higher cost compared to alternatives ($5+ per session)
• Terminal-based interface may not suit all developers
• Closed ecosystem with limited community plugins
• Requires API subscription for full features

Gemini CLI (Google)

Pros:

• Free tier with generous limits (60 requests/min, 1,000/day)
• Fully open source (Apache 2.0 license)
• 1 million token context window
• MCP integration for extensibility
• GitHub Actions integration at no cost

Cons:

• Currently in preview with potential stability issues
• Shared quotas between CLI and Code Assist
• May produce factually incorrect outputs
• Limited to English language support

Codex CLI (OpenAI/Microsoft)

Pros:

• Cloud-based scalability for team collaboration
• Powers GitHub Copilot ecosystem
• Supports multimodal input (images, diagrams)
• Strong GitHub integration
• Flexible API for custom implementations

Cons:

• Requires more setup and technical knowledge
• Internet dependency for all operations
• Less mature/polished than competitors
• Higher computational requirements

Copilot CLI (GitHub)

Pros:

• Seamless GitHub integration
• Terminal-native development experience
• Wide language and model support
• Command explanation and suggestion features
• Enterprise policy controls available

Cons:

• Requires active subscription
• English-only support
• May struggle with complex/uncommon commands
• Organization admin approval needed for business users

Cursor CLI

Pros:

• Superior performance in setup and deployment
• Multi-model support from various providers
• Excellent context awareness with RAG system
• Enterprise features for CI/CD integration
• Can run multiple agents in parallel

Cons:

• Steeper learning curve
• UI/UX can be clunky with cramped interface
• Manual context management required
• Screen real estate limitations

Grok CLI (xAI/Vibe Kit)

Pros:

• Open source and free for basic use
• Cost-effective premium tier ($30/month)
• Real-time data access via X integration
• Strong community support
• Cross-platform compatibility

Cons:

• Requires API key for advanced features
• Internet dependency for AI features
• Additional setup and authentication needed
• Newer with less mature ecosystem

Qwen Code CLI (Alibaba)

Pros:

• Fully open source (Apache 2.0)
• Exceptional benchmark performance (87.9 on MultiPL-E)
• 256K-1M token context support
• No subscription required
• Enterprise-ready with full infrastructure control

Cons:

• Newer entrant with developing ecosystem
• Geopolitical considerations for adoption
• Less established tooling and integrations
• Regional trust and security concerns

Choosing the Right Tool

• For Solo Developers: Claude Code (complex tasks) or Grok CLI (cost-conscious)
• For Teams: Codex CLI (cloud collaboration) or Cursor CLI (parallel agents)
• For Enterprises: Claude Code (performance) or Qwen Code (self-hosted)
• For Budget-Conscious: Gemini CLI (free tier) or Qwen Code (open source)
• For GitHub Users: Copilot CLI (native integration)

Options

• --cli=<tool>: Specify which AI CLI tool to use (claude, gemini, codex, copilot, cursor). Defaults to claude.
• --exit-on-idle=<seconds>: Automatically exit when the AI tool becomes idle for the specified duration. Useful for automation scripts.

Library Usage

You can also use this as a library in your Node.js projects:

import claudeYes from 'claude-yes';

// Use Claude
await claudeYes({
  prompt: 'help me solve all todos in my codebase',
  cli: 'claude',
  cliArgs: ['--verbose'],
  exitOnIdle: 30000, // exit after 30 seconds of idle
  continueOnCrash: true,
  logFile: 'claude.log',
});

// Use other tools
await claudeYes({
  prompt: 'debug this function',
  cli: 'gemini',
  exitOnIdle: 60000,
});

Implementation

The tool uses node-pty to spawn and manage AI CLI processes, with a sophisticated pattern-matching system that:

1. Detects Ready States: Recognizes when each CLI tool is ready to accept input
2. Auto-Responds: Automatically sends "Yes" responses to common prompts
3. Handles Fatal Errors: Detects and responds to fatal error conditions
4. Manages Process Lifecycle: Handles crashes, restarts, and graceful exits

Each supported CLI has its own configuration defining:

• Ready patterns: Regex patterns that indicate the tool is ready for input
• Enter patterns: Patterns that trigger automatic "Yes" responses
• Fatal patterns: Patterns that indicate fatal errors requiring exit
• Binary mapping: Maps logical names to actual executable names
• Argument handling: Special argument processing (e.g., adding --search to Codex)

Dependencies

• node-pty or bun-pty - For spawning and managing AI CLI processes
• from-node-stream - Stream processing utilities
• sflow - Functional stream processing
• terminal-render - Terminal rendering and text processing
• phpdie - Error handling utilities

Inspiration

This project was inspired by: Claude Code full auto while I sleep : r/ClaudeAI

License

MIT