by automazeio
Native macOS menu bar app to use your Claude Code & ChatGPT subscriptions with AI coding tools - no API keys needed
# Add to your Claude Code skills
git clone https://github.com/automazeio/vibeproxyGuides for using cli tools skills like vibeproxy.
Last scanned: 4/23/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-23T06:08:07.790Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}See how vibeproxy compares with popular alternatives.
vibeproxy is an open-source cli tools skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by automazeio. Native macOS menu bar app to use your Claude Code & ChatGPT subscriptions with AI coding tools - no API keys needed. It has 3,382 GitHub stars.
Yes. vibeproxy passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/automazeio/vibeproxy" and add it to your Claude Code skills directory (see the Installation section above).
vibeproxy is primarily written in Swift. It is open-source under automazeio on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other CLI Tools skills you can browse and compare side by side. Open the CLI Tools category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh vibeproxy against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Based on votes and bookmarks from developers who liked this skill
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Stop paying twice for AI. VibeProxy is a beautiful native macOS menu bar app that lets you use your existing Claude Code, ChatGPT, Gemini, Kimi, Qwen, Antigravity, and Z.AI GLM subscriptions with powerful AI coding tools like Factory Droids.
Built on CLIProxyAPI, it handles OAuth authentication, token management, and API routing automatically. One click to authenticate, zero friction to code.
[!TIP] 📣 NEW: Vercel AI Gateway Integration!Route your Claude requests through Vercel's officially sanctioned AI Gateway for safer access to your Claude Max subscription. No more worrying about account risks from using OAuth tokens directly!
Latest models supported: Gemini 3 Pro (via Antigravity), GPT-5.1 / GPT-5.1 Codex, Claude Sonnet 4.5 / Opus 4.5 with extended thinking, GitHub Copilot, Z.AI GLM-4.7, and Kimi! 🚀
Setup Guides:
- Factory CLI Setup → - Use Factory Droids with your AI subscriptions
- Amp CLI Setup → - Use Amp CLI with fallback to your subscriptions
Requirements: macOS 13+ (Ventura or later)
VibeProxy-arm64.zipVibeProxy-x86_64.zip (untested - please report issues)VibeProxy.app to /ApplicationsCode Signed & Notarized ✅ - No Gatekeeper warnings, installs seamlessly on macOS.
Want to build it yourself? See INSTALLATION.md for detailed build instructions.
When you click "Connect" for an OAuth provider:
When you click "Add Account" for Z.AI GLM:
~/.cli-proxy-api/VibeProxy supports persistent CLIProxyAPI overrides in:
~/.cli-proxy-api/config.yaml
VibeProxy merges this user-owned file with its bundled defaults, writes the effective runtime configuration to ~/.cli-proxy-api/merged-config.yaml, and reloads changes automatically. Put custom settings in config.yaml; do not edit merged-config.yaml directly because VibeProxy regenerates it.
For example, supported GPT models can default to concise responses by adding an OpenAI Responses API verbosity rule:
payload:
default:
- models:
- name: "gpt-*"
protocol: "codex"
params:
"text.verbosity": "low"
default only supplies the value when the client does not already send one. Use override instead if the proxy should always enforce the configured value. Supported verbosity values are low, medium, and high.
After saving the file, VibeProxy regenerates its runtime configuration and applies the change without an application restart.
Codex reads its configuration from ~/.codex/config.toml. VibeProxy exposes an OpenAI-compatible endpoint, so there are two ways to point Codex at it.
Simple override - replace the default endpoint:
base_url = "http://127.0.0.1:8317/v1"
Explicit provider - add a named provider and select it:
model_provider = "cliproxyapi"
[model_providers.cliproxyapi]
name = "cliproxyapi"
base_url = "http://127.0.0.1:8317/v1"
wire_api = "responses"
Both route Codex agent traffic through VibeProxy, and both work for normal Codex use. They differ in one respect we know about today: Codex's native ChatGPT surfaces (Quick Chat, "More details", and Computer history) use the ChatGPT account path, and with the explicit provider block those surfaces consistently fail or become unavailable, while the simple override leaves them working. If you rely on those features, prefer the simple override.
This is reported and still under investigation in #544, so treat it as an observed difference rather than an explained one. We don't yet have log evidence showing whether a failing Quick Chat request reaches the proxy on port 8317 at all. Note that CLIProxyAPI's own documentation recommends the explicit provider shape; if you follow it and lose Quick Chat, this is why.
Port 8317 is bound to 127.0.0.1 only by default. If you enable LAN access in Settings, substitute this machine's LAN IP for 127.0.0.1.
Run the complete Swift test suite from the repository root:
make test
Pull requests run the same suite on macOS through GitHub Actions. Local test runs require a full Xcode toolchain because Command Line Tools alone do not include XCTest.
VibeProxy/
├── Sources/
│ ├── main.swift # App entry point
│ ├── AppDelegate.swift # Menu bar & window management
│ ├── ServerManager.swift # Server process control & auth
│ ├── SettingsView.swift # Main UI
│ ├── AuthStatus.swift # Auth file monitoring
│ └── Resources/
│ ├── AppIcon.iconset # App icon
│ ├── AppIcon.icns # App icon
│ ├── cli-proxy-api-plus # CLIProxyAPI binary
│ ├── config.yaml # CLIProxyAPI config
│ ├── icon-active.png # Menu bar icon (active)
│ ├── icon-inactive.png # Menu bar icon (inactive)
│ ├── icon-claude.png # Claude Code service icon
│ ├── icon-codex.png # Codex service icon
│ ├── icon-gemini.png # Gemini service icon
│ ├── icon-qwen.png # Qwen service icon
│ └── icon-zai.png # Z.AI GLM service icon
├── Package.swift # Swift Package Manager config
├── Info.plist # macOS app metadata
├── build.sh # Resource bundling script
├── create-app-bundle.sh # App bundle creation script
└── Makefile # Build automation
~/.cli-proxy-api/ for authentication filesVibeProxy is built on top of CLIProxyAPI, an excellent unified proxy server for AI services with support for third-party providers.
Special thanks to the CLIProxyAPI project for providing the core functionality that makes VibeProxy