vibeproxy

🥈Silver

VibeProxy is a native macOS menu bar app that enables developers to use their Claude Code and ChatGPT subscriptions with AI coding tools without requiring API keys. It benefits developers and operations teams by simplifying access to AI coding assistants. The app integrates with macOS and connects to AI coding tools, enhancing productivity in software development workflows.

2,414760Updated 2w ago

Intermediate30min to implementautomation

Saves ~45 min per use

Quick InstallView Source

git clone https://github.com/automazeio/vibeproxy.git

Works with:

Claude

Overview

About This Skill

https://github.com/automazeio/vibeproxy

How to Use

[{"step":"Install VibeProxy from the macOS App Store or the official website. Ensure it’s running in your menu bar (look for the VibeProxy icon).","tip":"Grant VibeProxy access to your system clipboard and local files in macOS System Settings > Privacy & Security if prompted."},{"step":"Open your terminal or IDE (e.g., VS Code) and run a command like `vibeproxy --task \"[TASK]\" --project \"/path/to/project\"`. For example: `vibeproxy --task \"Run a security audit on the /src directory\" --project \"/Users/me/acmecorp\"`.","tip":"Use `--verbose` flag to get detailed logs if VibeProxy encounters issues connecting to your AI coding tool."},{"step":"Review the AI-generated output in your terminal or save it to a file for further analysis. For example: `vibeproxy --task \"[TASK]\" --project \"/path/to/project\" > review_output.txt`.","tip":"If VibeProxy fails to connect, check your internet connection or restart the app. Ensure your Claude Code or ChatGPT subscription is active."},{"step":"Implement the suggested fixes in your codebase. Prioritize critical issues first (e.g., security vulnerabilities) and use the output as a guide for refactoring.","tip":"For large projects, break the task into smaller chunks (e.g., review one module at a time) to avoid overwhelming the AI with too much context."},{"step":"Re-run VibeProxy after implementing changes to verify fixes or identify new issues. For example: `vibeproxy --task \"Verify SQL injection fixes\" --project \"/Users/me/acmecorp\"`.","tip":"Use the `--diff` flag to compare the current state of your code with the original analysis: `vibeproxy --task \"Show diff of changes\" --project \"/path/to/project\" --diff`."}]

Use Cases

Authenticate and manage multiple AI service accounts from a single menu bar application.

Quickly switch between different AI models like Claude Code and Gemini for diverse coding tasks.

Utilize powerful AI coding tools like Factory Droids without needing to manage separate API keys.

Automatically route requests through Vercel AI Gateway for enhanced security and reliability.

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/automazeio/vibeproxy

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Use VibeProxy to [TASK] in [PROJECT_NAME] without requiring API keys. For example: 'Run a full code review of the /src directory in the AcmeCorp project, flagging potential security vulnerabilities and suggesting optimizations for the payment processing module.'

Example Output

Here’s the output from running a security-focused code review on the AcmeCorp project using VibeProxy:

**Critical Findings (3):**
1. **SQL Injection Risk** in `/src/db/queries.js` (Line 42): The `getUserOrders` function directly interpolates user input into a SQL query without parameterization. Fix: Replace with `db.query('SELECT * FROM orders WHERE user_id = ?', [userId])`.
2. **Hardcoded API Key** in `/src/config/secrets.ts` (Line 15): The Stripe API key is exposed in plaintext. Fix: Move to environment variables and use `process.env.STRIPE_KEY`.
3. **Missing Input Validation** in `/src/routes/auth.js`: The `login` endpoint accepts raw JSON without sanitization. Fix: Add schema validation using `zod` or `joi`.

**Optimizations (5):**
- **Performance:** The `/api/users` endpoint fetches all records at once. Suggest pagination with `?limit=50&offset=0`.
- **Logging:** Add structured logging with `winston` to `/src/utils/logger.js` for better debugging.
- **Dependencies:** Update `lodash` from v4.17.15 to v4.17.21 to patch prototype pollution vulnerabilities.
- **Error Handling:** Wrap the `/api/payments` endpoint in a try-catch block to avoid unhandled rejections.
- **Type Safety:** Add TypeScript types to `/src/models/User.ts` for better IDE support.

**Next Steps:**
1. Address the SQL injection risk immediately—this is a high-priority item.
2. Refactor the secrets management to use environment variables.
3. Implement pagination for the `/api/users` endpoint.
4. Add unit tests for the `/api/auth` endpoint to cover edge cases.

Total files analyzed: 42 | Critical issues: 3 | Optimizations: 5 | Estimated fix time: 4 hours.