claude-yolo 1.7.0 → 1.9.1

package/.claude/settings.local.json

@@ -0,0 +1,6 @@
+{
+  "enabledMcpjsonServers": [
+    "tmux"
+  ],
+  "enableAllProjectMcpServers": true
+}

package/.cursor/rules/cursor-tools.mdc

@@ -0,0 +1,161 @@
+---
+description: Global Rule. This rule should ALWAYS be loaded.
+globs: *,**/*
+alwaysApply: true
+---
+cursor-tools is a CLI tool that allows you to interact with AI models and other tools.
+cursor-tools is installed on this machine and it is available to you to execute. You're encouraged to use it.
+
+<cursor-tools Integration>
+# Instructions
+Use the following commands to get AI assistance:
+
+**Direct Model Queries:**
+`cursor-tools ask "<your question>" --provider <provider> --model <model>` - Ask any model from any provider a direct question (e.g., `cursor-tools ask "What is the capital of France?" --provider openai --model o3-mini`). Note that this command is generally less useful than other commands like `repo` or `plan` because it does not include any context from your codebase or repository.
+
+**Implementation Planning:**
+`cursor-tools plan "<query>"` - Generate a focused implementation plan using AI (e.g., `cursor-tools plan "Add user authentication to the login page"`)
+The plan command uses multiple AI models to:
+1. Identify relevant files in your codebase (using Gemini by default)
+2. Extract content from those files
+3. Generate a detailed implementation plan (using OpenAI o3-mini by default)
+
+**Plan Command Options:**
+--fileProvider=<provider>: Provider for file identification (gemini, openai, anthropic, perplexity, modelbox, or openrouter)
+--thinkingProvider=<provider>: Provider for plan generation (gemini, openai, anthropic, perplexity, modelbox, or openrouter)
+--fileModel=<model>: Model to use for file identification
+--thinkingModel=<model>: Model to use for plan generation
+--debug: Show detailed error information
+
+**Web Search:**
+`cursor-tools web "<your question>"` - Get answers from the web using a provider that supports web search (e.g., Perplexity models and Gemini Models either directly or from OpenRouter or ModelBox) (e.g., `cursor-tools web "latest shadcn/ui installation instructions"`)
+when using web for complex queries suggest writing the output to a file somewhere like local-research/<query summary>.md.
+
+**Web Command Options:**
+--provider=<provider>: AI provider to use (perplexity, gemini, modelbox, or openrouter)
+--model=<model>: Model to use for web search (model name depends on provider)
+--max-tokens=<number>: Maximum tokens for response
+
+**Repository Context:**
+`cursor-tools repo "<your question>"` - Get context-aware answers about this repository using Google Gemini (e.g., `cursor-tools repo "explain authentication flow"`)
+
+**Documentation Generation:**
+`cursor-tools doc [options]` - Generate comprehensive documentation for this repository (e.g., `cursor-tools doc --output docs.md`)
+when using doc for remote repos suggest writing the output to a file somewhere like local-docs/<repo-name>.md.
+
+**GitHub Information:**
+`cursor-tools github pr [number]` - Get the last 10 PRs, or a specific PR by number (e.g., `cursor-tools github pr 123`)
+`cursor-tools github issue [number]` - Get the last 10 issues, or a specific issue by number (e.g., `cursor-tools github issue 456`)
+
+**ClickUp Information:**
+`cursor-tools clickup task <task_id>` - Get detailed information about a ClickUp task including description, comments, status, assignees, and metadata (e.g., `cursor-tools clickup task "task_id"`)
+
+**Model Context Protocol (MCP) Commands:**
+Use the following commands to interact with MCP servers and their specialized tools:
+`cursor-tools mcp search "<query>"` - Search the MCP Marketplace for available servers that match your needs (e.g., `cursor-tools mcp search "git repository management"`)
+`cursor-tools mcp run "<query>"` - Execute MCP server tools using natural language queries (e.g., `cursor-tools mcp run "list files in the current directory"`). The query must include sufficient information for cursor-tools to determine which server to use, provide plenty of context.
+
+The `search` command helps you discover servers in the MCP Marketplace based on their capabilities and your requirements. The `run` command automatically selects and executes appropriate tools from these servers based on your natural language queries. If you want to use a specific server include the server name in your query. E.g. `cursor-tools mcp run "using the mcp-server-sqlite list files in directory"
+The `run` command will automatically download, checkout or clone MCP servers and initialize them for you. You do NOT need to separately install or clone or checkout an MCP server if you're going to run it with cursor-tools, even if the README of the MCP server says that you need to.
+
+**Notes on MCP Commands:**
+- MCP commands require `ANTHROPIC_API_KEY` to be set in your environment
+- Results are streamed in real-time for immediate feedback
+- Tool calls are automatically cached to prevent redundant operations
+- Often the MCP server will not be able to run because environment variables are not set. If this happens ask the user to add the missing environment variables to the cursor tools env file at ~/.cursor-tools/.env
+
+**Stagehand Browser Automation:**
+`cursor-tools browser open <url> [options]` - Open a URL and capture page content, console logs, and network activity (e.g., `cursor-tools browser open "https://example.com" --html`)
+`cursor-tools browser act "<instruction>" --url=<url | 'current'> [options]` - Execute actions on a webpage using natural language instructions (e.g., `cursor-tools browser act "Click Login" --url=https://example.com`)
+`cursor-tools browser observe "<instruction>" --url=<url> [options]` - Observe interactive elements on a webpage and suggest possible actions (e.g., `cursor-tools browser observe "interactive elements" --url=https://example.com`)
+`cursor-tools browser extract "<instruction>" --url=<url> [options]` - Extract data from a webpage based on natural language instructions (e.g., `cursor-tools browser extract "product names" --url=https://example.com/products`)
+
+**Notes on Browser Commands:**
+- All browser commands are stateless unless --connect-to is used to connect to a long-lived interactive session. In disconnected mode each command starts with a fresh browser instance and closes it when done.
+- When using `--connect-to`, special URL values are supported:
+  - `current`: Use the existing page without reloading
+  - `reload-current`: Use the existing page and refresh it (useful in development)
+  - If working interactively with a user you should always use --url=current unless you specifically want to navigate to a different page. Setting the url to anything else will cause a page refresh loosing current state.
+- Multi step workflows involving state or combining multiple actions are supported in the `act` command using the pipe (|) separator (e.g., `cursor-tools browser act "Click Login | Type 'user@example.com' into email | Click Submit" --url=https://example.com`)
+- Video recording is available for all browser commands using the `--video=<directory>` option. This will save a video of the entire browser interaction at 1280x720 resolution. The video file will be saved in the specified directory with a timestamp.
+- DO NOT ask browser act to "wait" for anything, the wait command is currently disabled in Stagehand.
+
+**Tool Recommendations:**
+- `cursor-tools web` is best for general web information not specific to the repository. Generally call this without additional arguments.
+- `cursor-tools repo` is ideal for repository-specific questions, planning, code review and debugging. E.g. `cursor-tools repo "Review recent changes to command error handling looking for mistakes, omissions and improvements"`. Generally call this without additional arguments.
+- `cursor-tools plan` is ideal for planning tasks. E.g. `cursor-tools plan "Adding authentication with social login using Google and Github"`. Generally call this without additional arguments.
+- `cursor-tools doc` generates documentation for local or remote repositories.
+- `cursor-tools browser` is useful for testing and debugging web apps and uses Stagehand
+- `cursor-tools mcp` enables interaction with specialized tools through MCP servers (e.g., for Git operations, file system tasks, or custom tools)
+
+**Running Commands:**
+1. Use `cursor-tools <command>` to execute commands (make sure cursor-tools is installed globally using npm install -g cursor-tools so that it is in your PATH)
+
+**General Command Options (Supported by all commands):**
+--provider=<provider>: AI provider to use (openai, anthropic, perplexity, gemini, or openrouter). If provider is not specified, the default provider for that task will be used.
+--model=<model name>: Specify an alternative AI model to use. If model is not specified, the provider's default model for that task will be used.
+--max-tokens=<number>: Control response length
+--save-to=<file path>: Save command output to a file (in *addition* to displaying it)
+--help: View all available options (help is not fully implemented yet)
+
+**Repository Command Options:**
+--provider=<provider>: AI provider to use (gemini, openai, openrouter, perplexity, or modelbox)
+--model=<model>: Model to use for repository analysis
+--max-tokens=<number>: Maximum tokens for response
+
+**Documentation Command Options:**
+--from-github=<GitHub username>/<repository name>[@<branch>]: Generate documentation for a remote GitHub repository
+--provider=<provider>: AI provider to use (gemini, openai, openrouter, perplexity, or modelbox)
+--model=<model>: Model to use for documentation generation
+--max-tokens=<number>: Maximum tokens for response
+
+**GitHub Command Options:**
+--from-github=<GitHub username>/<repository name>[@<branch>]: Access PRs/issues from a specific GitHub repository
+
+**Browser Command Options (for 'open', 'act', 'observe', 'extract'):**
+--console: Capture browser console logs (enabled by default, use --no-console to disable)
+--html: Capture page HTML content (disabled by default)
+--network: Capture network activity (enabled by default, use --no-network to disable)
+--screenshot=<file path>: Save a screenshot of the page
+--timeout=<milliseconds>: Set navigation timeout (default: 120000ms for Stagehand operations, 30000ms for navigation)
+--viewport=<width>x<height>: Set viewport size (e.g., 1280x720). When using --connect-to, viewport is only changed if this option is explicitly provided
+--headless: Run browser in headless mode (default: true)
+--no-headless: Show browser UI (non-headless mode) for debugging
+--connect-to=<port>: Connect to existing Chrome instance. Special values: 'current' (use existing page), 'reload-current' (refresh existing page)
+--wait=<time:duration or selector:css-selector>: Wait after page load (e.g., 'time:5s', 'selector:#element-id')
+--video=<directory>: Save a video recording (1280x720 resolution, timestamped subdirectory). Not available when using --connect-to
+--url=<url>: Required for `act`, `observe`, and `extract` commands. Url to navigate to before the main command or one of the special values 'current' (to stay on the current page without navigating or reloading) or 'reload-current' (to reload the current page)
+--evaluate=<string>: JavaScript code to execute in the browser before the main command
+
+**Nicknames**
+Users can ask for these tools using nicknames
+Gemini is a nickname for cursor-tools repo
+Perplexity is a nickname for cursor-tools web
+Stagehand is a nickname for cursor-tools browser
+
+**Xcode Commands:**
+`cursor-tools xcode build [buildPath=<path>] [destination=<destination>]` - Build Xcode project and report errors.
+**Build Command Options:**
+--buildPath=<path>: (Optional) Specifies a custom directory for derived build data. Defaults to ./.build/DerivedData.
+--destination=<destination>: (Optional) Specifies the destination for building the app (e.g., 'platform=iOS Simulator,name=iPhone 16 Pro'). Defaults to 'platform=iOS Simulator,name=iPhone 16 Pro'.
+
+`cursor-tools xcode run [destination=<destination>]` - Build and run the Xcode project on a simulator.
+**Run Command Options:**
+--destination=<destination>: (Optional) Specifies the destination simulator (e.g., 'platform=iOS Simulator,name=iPhone 16 Pro'). Defaults to 'platform=iOS Simulator,name=iPhone 16 Pro'.
+
+`cursor-tools xcode lint` - Run static analysis on the Xcode project to find and fix issues.
+
+**Additional Notes:**
+- For detailed information, see `node_modules/cursor-tools/README.md` (if installed locally).
+- Configuration is in `cursor-tools.config.json` (or `~/.cursor-tools/config.json`).
+- API keys are loaded from `.cursor-tools.env` (or `~/.cursor-tools/.env`).
+- ClickUp commands require a `CLICKUP_API_TOKEN` to be set in your `.cursor-tools.env` file.
+- The default Stagehand model is set in `cursor-tools.config.json`, but can be overridden with the `--model` option.
+- Available models depend on your configured provider (OpenAI or Anthropic) in `cursor-tools.config.json`.
+- repo has a limit of 2M tokens of context. The context can be reduced by filtering out files in a .repomixignore file.
+- problems running browser commands may be because playwright is not installed. Recommend installing playwright globally.
+- MCP commands require `ANTHROPIC_API_KEY` to be set in your environment.
+- **Remember:** You're part of a team of superhuman expert AIs. Work together to solve complex problems.
+
+<!-- cursor-tools-version: 0.6.0-alpha.10 -->
+</cursor-tools Integration>

package/.cursorindexingignore

@@ -0,0 +1,3 @@
+
+# Don't index SpecStory auto-save files, but allow explicit context inclusion via @ references
+.specstory/**

package/.mcp.json

@@ -0,0 +1,13 @@
+{
+  "mcpServers": {
+    "tmux": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "-y",
+        "tmux-mcp"
+      ],
+      "env": {}
+    }
+  }
+}

package/.specstory/history/.what-is-this.md

@@ -0,0 +1,54 @@
+# SpecStory Artifacts Directory
+    
+This directory is automatically created and maintained by the SpecStory extension to preserve your Cursor composer and chat history.
+    
+## What's Here?
+    
+- `.specstory/history`: Contains markdown files of your AI coding sessions
+- Each file represents a separate chat or composer session
+- Files are automatically updated as you work
+
+## Valuable Uses
+    
+- Capture: Keep your context window up-to-date when starting new Chat/Composer sessions via @ references
+- Search: For previous prompts and code snippets 
+- Learn: Meta-analyze your patterns and learn from your past experiences
+    
+## Version Control
+    
+We recommend keeping this directory under version control to maintain a history of your AI interactions. However, if you prefer not to version these files, you can exclude them by adding this to your `.gitignore`:
+    
+```
+.specstory/**
+```
+    
+## Searching Your Codebase
+    
+When searching your codebase in Cursor, search results may include your previous AI coding interactions. To focus solely on your actual code files, you can exclude the AI interaction history from search results.
+    
+To exclude AI interaction history:
+    
+1. Open the "Find in Files" search in Cursor (Cmd/Ctrl + Shift + F)
+2. Navigate to the "files to exclude" section
+3. Add the following pattern:
+    
+```
+.specstory/*
+```
+    
+This will ensure your searches only return results from your working codebase files.
+
+## Notes
+
+- Auto-save only works when Cursor/sqlite flushes data to disk. This results in a small delay after the AI response is complete before SpecStory can save the history.
+- Auto-save does not yet work on remote WSL workspaces.
+
+## Settings
+    
+You can control auto-saving behavior in Cursor:
+    
+1. Open Cursor → Settings → VS Code Settings (Cmd/Ctrl + ,)
+2. Search for "SpecStory"
+3. Find "Auto Save" setting to enable/disable
+    
+Auto-save occurs when changes are detected in Cursor's sqlite database, or every 2 minutes as a safety net.

package/.specstory/history/2025-02-26_13-24-checking-recent-tweets.md

@@ -0,0 +1,124 @@
+## SpecStory
+
+## Checking Recent Tweets (26/02/2025, 14:24:22)
+
+_**User**_
+
+check my recent tweets
+
+---
+
+_**Assistant**_
+
+<think>The user wants to check their recent tweets. I need to check if I have a tool to interact with Twitter. Looking through the available function definitions, I can see there are several Twitter-related tools:
+
+- mcp__TWITTER_BOOKMARKS_BY_USER
+- mcp__TWITTER_POST_LOOKUP_BY_POST_ID
+- mcp__TWITTER_CREATE_LIST
+- mcp__TWITTER_CREATION_OF_A_POST
+- mcp__TWITTER_USER_LOOKUP_BY_ID
+- mcp__TWITTER_USER_HOME_TIMELINE_BY_USER_ID
+- mcp__TWITTER_USER_LOOKUP_BY_USERNAME
+- mcp__TWITTER_USER_LOOKUP_BY_IDS
+- mcp__TWITTER_RECENT_SEARCH
+- mcp__TWITTER_USER_LOOKUP_ME
+- mcp__TWITTER_CHECK_ACTIVE_CONNECTION
+- mcp__TWITTER_INITIATE_CONNECTION
+- mcp__TWITTER_GET_REQUIRED_PARAMETERS
+
+Before I can retrieve the user's tweets, I need to check if there's an active connection to Twitter. I'll first use the mcp__TWITTER_CHECK_ACTIVE_CONNECTION tool to check if there's an active connection.</think>I'll check if there's an active connection to Twitter first, then retrieve your recent tweets.
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+It looks like you don't have an active connection to Twitter. Let me help you set one up.
+
+First, I need to check what parameters are required to connect to Twitter:
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+Good news! Twitter has default credentials available, so we don't need to provide any additional parameters. Let's initiate a connection:
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+To connect to Twitter, you'll need to authorize access:
+
+1. Please open this URL in your browser: https://backend.composio.dev/s/T_GTWbJ_
+2. Follow the instructions to authorize the application
+3. Once you've completed the authorization, let me know and I'll check your recent tweets
+
+After you've completed the authorization process, I'll be able to retrieve your recent tweets.
+
+---
+
+_**User**_
+
+ok try now
+
+---
+
+_**Assistant**_
+
+<think>The user has indicated they've completed the Twitter authorization process. Let me check if the connection is now active, and if so, I can retrieve their recent tweets.
+
+First, I'll check if the connection is active using the connection ID from the previous response. Then if successful, I'll try to get their recent tweets.</think>I'll check if the Twitter connection is now active and then retrieve your recent tweets.
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+It seems the connection wasn't successfully established. Let's try initiating a new connection:
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+It seems we need to try the authorization process again with a new link. Please:
+
+1. Open this new URL in your browser: https://backend.composio.dev/s/A7nrot8K
+2. Complete the Twitter authorization process
+3. Let me know once you've done that
+
+After you've completed this process, I'll check again and retrieve your tweets.
+
+---
+
+
+
+---
+

package/.specstory/history/2025-03-10_15-17-sending-a-yo-to-my-server.md

@@ -0,0 +1,32 @@
+## SpecStory
+
+## Sending a Yo to My Server (10/03/2025, 16:17:24)
+
+_**User**_
+
+send a yo to my yo MCP server
+
+---
+
+_**Assistant**_
+
+I'll help you send a "yo" message using the MCP yo functionality.
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+I've sent a "yo" message to your MCP server. The message was successfully received! Let me know if you'd like to send another message or if there's anything else I can help you with.
+
+---
+
+
+
+---
+

package/.specstory/history/2025-03-10_17-20-sending-a-simple-yo-message.md

@@ -0,0 +1,104 @@
+## SpecStory
+
+## Sending a Simple "Yo" Message (10/03/2025, 18:20:37)
+
+_**User**_
+
+send a yo using mcp
+
+---
+
+_**Assistant**_
+
+Let me help you send a "yo" using MCP. First, I'll check if there are any relevant files or rules about using MCP.
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+<details>
+            <summary>Searched codebase "send a yo using mcp" • **25** results</summary>
+        
+| File | Lines |
+|------|-------|
+| `.specstory/history/sending-a-yo-to-my-server.md` | L1-33 |
+| `.specstory/history/sending-a-simple-yo-message.md` | L1-33 |
+| `bin/claude-yolo.js` | L175-207 |
+| `bin/claude-yolo.js` | L120-175 |
+| `make-yolo.sh` | L1-42 |
+| `make-yolo.sh` | L42-75 |
+| `README.md` | L1-55 |
+| `bin/claude-yolo.js` | L51-67 |
+| `postinstall.js` | L23-24 |
+| `postinstall.js` | L36-52 |
+| `bin/claude-yolo.js` | L23-51 |
+| `README.md` | L55-104 |
+| `package.json` | L1-36 |
+| `postinstall.js` | L1-18 |
+| `postinstall.js` | L19-20 |
+| `postinstall.js` | L29-31 |
+| `bin/claude-yolo.js` | L1-23 |
+| `generate-screenshot.js` | L33-35 |
+| `generate-screenshot.js` | L20-21 |
+| `bin/claude-yolo.js` | L207-216 |
+| `bin/claude-yolo.js` | L67-97 |
+| `generate-screenshot.js` | L16-17 |
+| `generate-screenshot.js` | L1-15 |
+| `generate-screenshot.js` | L26-28 |
+| `bin/claude-yolo.js` | L97-120 |
+
+</details>
+
+---
+
+_****_
+
+Let me help you send a "yo" using MCP. Based on the codebase search, I can see this is something that has been done before. Let me propose the command to send a yo message.
+
+---
+
+_****_
+
+```bash
+claude-yolo yo
+```
+
+```
+andy@Andys-MacBook-Pro claude-yolo % claude-yolo yo
+
+🔥 CLAUDE-YOLO INSTALLATION CONSENT REQUIRED 🔥
+
+----------------------------------------
+What is claude-yolo?
+This package creates a wrapper around the official Claude CLI tool that:
+  1. BYPASSES safety checks by automatically adding the --dangerously-skip-permissions flag
+  2. Automatically updates to the latest Claude CLI version
+  3. Adds colorful YOLO-themed loading messages
+
+⚠️ IMPORTANT SECURITY WARNING ⚠️
+The --dangerously-skip-permissions flag was designed for use in containers
+and bypasses important safety checks. This includes ignoring file access
+permissions that protect your system and privacy.
+
+By using claude-yolo:
+  • You acknowledge these safety checks are being bypassed
+  • You understand this may allow Claude CLI to access sensitive files
+  • You accept full responsibility for any security implications
+
+----------------------------------------
+
+Do you consent to using claude-yolo with these modifications? (yes/no):
+```
+
+---
+
+
+
+---
+

package/.specstory/history/2025-03-12_08-37-documentation-retrieval-for-repomix-repo.md

@@ -0,0 +1,32 @@
+## SpecStory
+
+## Documentation Retrieval for Repomix Repo (12/03/2025, 09:37:43)
+
+_**User**_
+
+send a yo
+
+---
+
+_**Assistant**_
+
+I'll send a "yo" message using the appropriate tool.
+
+---
+
+_****_
+
+
+
+---
+
+_****_
+
+I've sent a "yo" message. The message was successfully delivered.
+
+---
+
+
+
+---
+