FlyEnv Local Development Environment Manager
Manage local dev stacks, AI coding CLIs, and MCP natively on Windows, macOS, and Linux.
- Source repo
- xpf0000/FlyEnv
- Stars
- ★ 3.3k
- Last updated
- 1d ago
- License
- BSD-3-Clause
- Primary language
- TypeScript
- FA score
- 50/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformChatGPT · Codex · Claude Code
- Cost
- Free, no paid service needed
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- PHP/Laravel developers needing a fast Windows alternative to Laravel Herd and XAMPP, with instant PHP version switching.
- Not a fit if
- Teams that need exact Docker Compose or Kubernetes parity with production
- Developers using only one runtime who are happy with their system package manager
- Teams that need a hosted platform or production deployment system
- Source review
- 50/100 · Major gaps
What does this agent do, and when should you use it?
FlyEnv is a desktop app for managing local development environments on Windows, macOS, and Linux. It allows on-demand installation of runtimes like PHP, Node.js, Python, Java, .NET, and Flutter, as well as services like Nginx, Apache, MySQL, Redis, and more. Projects can have specific runtime versions and custom commands, and can be exposed via local domains, reverse proxies, HTTPS, and Cloudflare Tunnel. The built-in FlyEnv MCP Server lets AI clients inspect services, sites, configs, and logs, and it also manages AI coding CLIs such as Claude Code and Codex. FlyEnv uses native processes, avoiding Docker overhead, and supports cron jobs at global and site levels. The UI is multilingual, supporting 30+ languages.
FlyEnv provides a graphical interface to install runtimes (PHP, Node.js, Python, Java, .NET, Flutter, Go, Rust, Ruby, Bun, Deno), start/stop services (Nginx, Apache, MySQL, PostgreSQL, Redis, Elasticsearch), manage per-project runtime versions (auto-detecting package.json), and start project commands. It can create local domains and SSL certificates, configure reverse proxies and tunnels (e.g., Cloudflare Tunnel). Users can edit configs and logs, inspect ports, schedule cron jobs, generate certificates, test WebSocket/SSE, and work with JWTs. The FlyEnv MCP Server allows AI clients to inspect services, sites, versions, configs, and selected lifecycle actions, and it also manages AI coding CLIs (Claude Code, Codex, OpenCode, Kimi, Antigravity CLI, GitHub Copilot CLI).
- PHP/Laravel developers needing a fast Windows alternative to Laravel Herd and XAMPP, with instant PHP version switching.
- Node.js frontend developers wanting to avoid NVM, with automatic Node version detection per project and easy access to PostgreSQL or RabbitMQ.
- Full-stack developers needing to manage databases, queues, search, and object storage in one app without Docker overhead.
- AI coding workflow users who want to install Claude Code, Codex, etc., and expose their local environment to AI tools via MCP.
- Polyglot developers managing multiple runtime versions (Java, Python, .NET) while keeping the system PATH clean.
- Developers needing to configure cron jobs, reverse proxies, and HTTPS for local projects without manual config editing.
How do you install or deploy this agent?
For Windows, download the installer or portable version from the releases page: [Installer](https://github.com/xpf0000/FlyEnv/releases/download/v4.18.0/FlyEnv-Setup-4.18.0.exe) or [Portable](https://github.com/xpf0000/FlyEnv/releases/download/v4.18.0/FlyEnv-Portable-4.18.0.exe). For macOS, use Homebrew: brew install flyenv, or download the DMG for Intel or Apple Silicon. For Linux, download the .deb or .rpm packages from the releases page, with x86_64 and ARM64 support.
How do you use this agent?
After installation, open the FlyEnv app. From the available modules, install the runtimes and services you need. Configure runtime versions and custom commands per project. Use the interface to create local domains and SSL certificates. To use the MCP server, enable it in AI clients like Claude Code or Codex and connect. Use the CLI tools to manage AI coding CLIs. For detailed instructions, refer to the project documentation and video demos.
What are this agent's strengths and limitations?
- Cross-platform (Windows, macOS, Linux) with native processes, no Docker overhead.
- On-demand module installation with multi-version co-existence (PHP 5.6 to 8.x, Node, etc.).
- Built-in AI coding CLI management and MCP server for direct integration with AI tools.
- Per-project version auto-switching and configuration.
- Wide coverage: databases, queues, search, storage, reverse proxy, tunneling, cron jobs.
- Multilingual UI supporting 30+ languages.
- May be too broad, lacking depth in any single area; each feature may not be as advanced as specialized tools.
- Relies on Node.js/Electron, which may introduce performance or memory overhead for some users.
- For Docker-centric workflows, migration is not direct; adaptation is needed if you heavily rely on containers.
- Installation and configuration involve multiple steps; users may need to learn the UI.
- Learning curve may be steeper for users only using a single runtime compared to system package managers.
How does this agent compare with similar options?
Compared to Docker Desktop, FlyEnv uses native processes without containers, ideal for native development; compared to XAMPP/MAMP, FlyEnv offers wider runtime support and AI tool integration, along with version switching. Compared to Laravel Herd, FlyEnv serves as an alternative on Windows with more languages and AI capabilities.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| FlyEnv Local Development Environment Manager This agent | 50 · Major gaps | Desktop appFree | ★ 3.3k | 1d ago | TypeScript | ChatGPT · Codex · Claude Code |
| OmniGet Desktop Agents & Downloader | 71 · Some gaps | Desktop appFree + model costs | ★ 14k | 22d ago | Rust | Codex · Claude Code · OpenAI API · Claude API |
| AGF Local Coding Session Finder | 96 · Excellent | CLIFree | ★ 158 | 18d ago | Rust | Codex · Claude Code |
| mirrord: Run Local Processes Inside Your Kubernetes Cluster | 55 · Major gaps | CLIFree | ★ 5.4k | today | Rust | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows native process management, but least privilege design is not explicit; user confirmation mechanisms exist but not detailed; data flow transparency is limited, no telemetry or data collection described; sensitive data handling not specified; dependency security lacks audit or vulnerability scanning; external effects (e.g., modifying hosts, installing services) not clearly consented; rollback not mentioned; source attribution only via author info, unverified. Deductions: lack of implementation details and evidence.
Self-consistency is good, README and package.json versions match; dependency availability listed in package.json but not verified; failure messages not provided. Deductions: static review cannot verify runtime behavior.
Target audience clear, scenarios broad; capability boundaries described in README; trigger precision not detailed; environment fit supports multiple platforms but lacks detailed configuration. Deductions: trigger and boundary details insufficient.
Information architecture clear, README, LICENSE, package.json present; install notes detailed; naming stable; examples and FAQ present but not deep; known limitations not explicit; license is BSD-3-Clause but package.json license field is MIT, inconsistency; versioning and changelog not provided; maintenance responsibility via author info. Deductions: license inconsistency, missing changelog.
Output usability high, multiple installers and docs; marginal value clear, unique features; cost-benefit reasonable, open-source free. Deductions: static review cannot assess actual effectiveness.
Claim traceability moderate, some claims have links; cross-source corroboration limited; fact-inference separation not clear. Deductions: lack of independent verification and clear separation.
- License inconsistency: README and LICENSE are BSD-3-Clause, but package.json license field is MIT.
- No changelog or version history provided, making updates hard to track.
- Dependency security lacks audit or vulnerability scanning evidence.
- External effects (e.g., modifying hosts, installing services) not clearly consented.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
v4.20.1 v4.20.1: Fixed Issues
Release notes excerpt
FlyEnv v4.20.1 Update Release Notes 🛠️ Improvements & Bug Fixes 1. Fixed macOS Helper Installation Failure Resolved an issue where installing the FlyEnv helper after a DMG installation could repeatedly fail with Terminal exited with code 5 or Bootstrap failed: 5: Input/output error, preventing access to local sites and other operations that require the helper. …View on GitHub ↗ -
v4.20.0 v4.20.0: llama.cpp, OpenSearch Plugin & Windows UAC Authorization Mode
Release notes excerpt
FlyEnv v4.20.0 Update Release Notes 🚀 New Features 1. Added Windows UAC Authorization Mode FlyEnv can now perform supported Windows administrator operations through the native User Account Control (UAC) prompt, without requiring the FlyEnv helper to be installed. This gives users an alternative on devices where installing a background helper is inconvenient. The new authorization workflow provides: - Your Choice of Authorization Method: Choose UAC or the FlyEnv helper when administrator access is first needed, and change the preference later in Settings …View on GitHub ↗ -
v4.19.1 v4.19.1: Fixed Tray Popup Issues
Release notes excerpt
FlyEnv v4.19.1 Update Release Notes 🛠️ Improvements & Bug Fixes 1. Fixed Invisible Tray Window Blocking Mouse Clicks on macOS Resolved an issue where, after updating to v4.19.0, an invisible FlyEnv window could sit above all other applications and intercept mouse clicks. The affected area extended from the top-left corner of the screen down the left side, making windows, buttons, links, and desktop icons in that zone unclickable until FlyEnv was fully closed. …View on GitHub ↗