[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73361":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":10,"pushedAt":10,"updatedAt":23,"readmeContent":24,"aiSummary":25,"trendingCount":16,"starSnapshotCount":16,"syncStatus":26,"lastSyncTime":27,"discoverSource":28},73361,"port-kill","treadiehq\u002Fport-kill","treadiehq","Port Kill helps you find and free ports and caches blocking your dev work.","https:\u002F\u002Fportkill.com",null,"Rust",2022,54,4,1,0,6,57.82,"Other",false,"main",[],"2026-06-12 04:01:09","# Port Kill\n\nPort Kill helps you find and free ports blocking your dev work, plus manage development caches and orchestrate services. It works on macOS, Linux, and Windows, locally or over SSH with a simple CLI and status bar.\n\n**Two Binaries, Full Feature Parity:**\n- `port-kill` - GUI status bar app (macOS only) + full CLI\n- `port-kill-console` - Pure CLI version (all platforms)\n\nBoth binaries support all features including smart restart, service detection, and orchestration.\n\n![Port Kill Status Bar Icon](image-short.png)\n\n## Community & Support\n\nJoin our Discord community for discussions, support, and updates:\n\n[![Discord](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDiscord-Join%20our%20community-7289DA?style=for-the-badge&logo=discord&logoColor=white)](https:\u002F\u002Fdiscord.gg\u002FKqdBcqRk5E)\n\n## Install\n\n```bash\n# macOS\u002FLinux\ncurl -fsSL portkill.com\u002Finstall | bash\n\n# Windows (PowerShell or CMD)\ncurl -fsSL portkill.com\u002Finstall-windows -o install-release.bat && install-release.bat\n```\n\n**Windows users:** After installation, you MUST restart your terminal completely for PATH changes to take effect.\n\n### Troubleshooting Windows Installation\n\nIf you get `'port-kill' is not recognized` error after installing:\n\n1. **Close and reopen your terminal completely** (required for PATH changes)\n2. **Run diagnostics** to identify the issue:\n   ```powershell\n   powershell -Command \"Invoke-WebRequest -UseBasicParsing -Uri 'https:\u002F\u002Fraw.githubusercontent.com\u002Ftreadiehq\u002Fport-kill\u002Fmain\u002Fdiagnose-installation.bat' -OutFile 'diagnose.bat'\"; .\\diagnose.bat\n   ```\n3. **Test with full path** (works without PATH):\n   ```powershell\n   \"%USERPROFILE%\\AppData\\Local\\port-kill\\port-kill.exe\" --list\n   ```\n\nSee [WINDOWS.md](WINDOWS.md) for detailed Windows-specific guidance.\n\n## Quick start\n\n```bash\n# Kill whatever is blocking a port\nport-kill 3000\n\n# Kill multiple ports\nport-kill 3000 5000\n\n# List ports in use (one-time snapshot)\nport-kill --list\n\n# Confirm before killing\nport-kill 3000 --safe\n\n# Smart Restart - Kill and automatically restart a process (NEW!)\nport-kill --restart 3000\n\n# Show what can be restarted\nport-kill --show-restart-history\n\n# Service Detection & Start (NEW!)\nport-kill --detect                    # Discover npm scripts, docker-compose, etc.\nport-kill --start npm:dev             # Start a detected service\n\n# Guard mode with auto-restart (NEW!)\nport-kill --guard 3000 --guard-auto-restart\n\n# Orchestration - Manage multiple services (NEW!)\nport-kill --init-config              # Create .port-kill.yaml config\nport-kill --up                       # Start all services from config\nport-kill --down                     # Stop all services\nport-kill --status                   # Check service status\nport-kill --restart-service frontend # Restart specific service\n\n# Cache management\nport-kill cache --list\nport-kill cache --clean --safe-delete\nport-kill cache --doctor\n\n# Check for updates\nport-kill --check-updates\n\n# Automatically update to latest version\nport-kill --self-update\n```\n\n## Smart Restart & Service Management (NEW!)\n\nPort Kill now intelligently manages your development server lifecycle:\n\n### Smart Restart\nAutomatically restarts processes using their original startup commands:\n\n```bash\n# Kill and restart a process (saves restart info automatically)\nport-kill 3000                    # Kill process on port 3000\nport-kill --restart 3000          # Restart it with saved command\n\n# View restart history\nport-kill --show-restart-history  # See all restartable ports\n\n# Clear restart info\nport-kill --clear-restart 3000    # Remove saved restart info\n```\n\n### Service Detection & Start\nAutomatically discover and start services from your project:\n\n```bash\n# Discover available services\nport-kill --detect\n\n# Found services examples:\n#   npm:dev - npm run dev (Node.js)\n#   npm:start - npm run start (Node.js)\n#   docker:web - Docker Compose service: web\n#   python:app.py - Python app: app.py\n\n# Start a discovered service\nport-kill --start npm:dev\nport-kill --start docker:web\n```\n\n**Supported project types:**\n- **npm\u002Fyarn\u002Fpnpm** - Detects package.json scripts\n- **Docker Compose** - Detects docker-compose.yml services\n- **Procfile** - Detects Procfile processes\n- **Python** - Detects app.py, manage.py, etc.\n\n### Guard Mode with Auto-Restart\nKeep your services running automatically:\n\n```bash\n# Guard a port and auto-restart if process dies\nport-kill --guard 3000 --guard-auto-restart\n\n# Works with reservations\nport-kill --guard-mode --guard-auto-restart \\\n  --reserve-port 3000 \\\n  --project-name \"my-app\" \\\n  --process-name \"npm\"\n```\n\n## Service Orchestration (NEW!)\n\nManage multiple services together with a simple YAML configuration file.\n\n### Quick Start\n\n```bash\n# 1. Create a configuration file\nport-kill --init-config\n\n# 2. Edit .port-kill.yaml to define your services\n# (see example below)\n\n# 3. Start all services\nport-kill --up\n\n# 4. Check status\nport-kill --status\n\n# 5. Stop all services\nport-kill --down\n```\n\n### Configuration Example\n\nCreate `.port-kill.yaml` in your project root:\n\n```yaml\nversion: \"1\"\n\n# Global environment variables\nenv:\n  NODE_ENV: development\n  DEBUG: \"true\"\n\nservices:\n  # Frontend service\n  frontend:\n    command: npm run dev\n    port: 3000\n    dir: .\u002Ffrontend\n    startup_delay: 2\n    env:\n      PORT: \"3000\"\n  \n  # Backend API service\n  backend:\n    command: npm run start\n    port: 8000\n    dir: .\u002Fbackend\n    depends_on:\n      - database\n    env:\n      PORT: \"8000\"\n      DATABASE_URL: postgres:\u002F\u002Flocalhost:5432\u002Fmyapp\n  \n  # Database service\n  database:\n    command: docker-compose up database\n    port: 5432\n    startup_delay: 5\n```\n\n### Orchestration Commands\n\n```bash\n# Initialize configuration\nport-kill --init-config\n\n# Start all services (respects dependencies)\nport-kill --up\n\n# Stop all running services\nport-kill --down\n\n# Restart a specific service\nport-kill --restart-service backend\n\n# Check status of all services\nport-kill --status\n\n# Use custom config file\nport-kill --config-file my-config.yaml --up\n```\n\n### Configuration Options\n\n**Service Fields:**\n- `command` - Command to run the service (required)\n- `port` - Port the service runs on (optional)\n- `dir` - Working directory for the service (optional)\n- `env` - Service-specific environment variables (optional)\n- `depends_on` - List of services to start first (optional)\n- `startup_delay` - Seconds to wait after starting (optional)\n- `healthcheck` - Command to check service health (optional)\n\n**Global Fields:**\n- `version` - Config version (optional)\n- `env` - Environment variables for all services (optional)\n- `services` - Map of service definitions (required)\n\n### Dependency Management\n\nServices start in dependency order:\n\n```yaml\nservices:\n  api:\n    command: npm start\n    depends_on:\n      - database\n      - redis\n  \n  database:\n    command: docker-compose up database\n  \n  redis:\n    command: redis-server\n```\n\nStart order: `database` → `redis` → `api`\n\n### CLI quick reference\n\n```bash\n# Positional ports imply clearPort on each\nport-kill \u003Cport> [\u003Cport> ...]\n\n# Smart Restart & Lifecycle (NEW!)\n--restart \u003Cport>              # Restart process on port using saved command\n--show-restart-history        # Show all ports that can be restarted\n--clear-restart \u003Cport>        # Clear saved restart info for port\n--detect                      # Detect available services in current dir\n--start \u003Cname>                # Start a detected service (e.g., npm:dev)\n--guard-auto-restart          # Auto-restart processes in guard mode\n\n# Service Orchestration (NEW!)\n--init-config                 # Create sample .port-kill.yaml config\n--up                          # Start all services from config\n--down                        # Stop all running services\n--restart-service \u003Cname>      # Restart specific service\n--status                      # Show status of all configured services\n--config-file \u003Cpath>          # Use custom config file (default: .port-kill.yaml)\n\n# Thin aliases\n--clear \u003Cport>          # clearPort(port)\n--guard \u003Cport>          # guardPort(port)\n--allow \u003Cname>          # allow only this process name in guard\n--kill \u003Cpid>            # kill(pid)\n--kill-file \u003Cpath>      # kill processes holding this file\n--kill-ext \u003Cext>        # kill processes holding files with this extension\n--list-file \u003Cpattern>   # list processes by file path\u002Fpattern\n--list                  # list current ports in use (one-shot)\n--safe                  # ask for confirmation before killing\n```\n\n```bash\n# See what's using common dev ports\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --console --ports 3000,8000,8080\n\n# Scan port ranges (new!)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --console --json --ports '6000-9999'\n\n# Mixed individual ports and ranges\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --console --ports '3000,6000-6002,8000'\n\n# Free up the usual suspects\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --reset\n\n# Remote over SSH\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --remote user@host --ports 3000,8000\n\n# Guard mode (watch + auto-resolve)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --guard-mode --auto-resolve\n\n# Security audit (JSON)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --audit --json\n\n# Endpoint monitoring (send data to external endpoint)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console --monitor-endpoint https:\u002F\u002Fapi.company.com\u002Fport-status\n```\n\n## Cache Management\n\nPort Kill now includes comprehensive cache management for development environments:\n\n### Cache Commands\n\n```bash\n# List all detected caches\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --list\n\n# List with JSON output\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --list --json\n\n# Clean caches safely (with backup)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --clean --safe-delete\n\n# System diagnostics\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --doctor --json\n\n# Restore last backup\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --restore-last\n```\n\n### Language-Specific Cache Management\n\n```bash\n# Rust caches (target\u002F, ~\u002F.cargo)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --list --lang rust\n\n# JavaScript\u002FTypeScript caches (node_modules, .next, .vite, etc.)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --list --lang js\n\n# Python caches (__pycache__, .venv, .pytest_cache)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --list --lang py\n\n# Java caches (.gradle, build, ~\u002F.m2)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --list --lang java\n```\n\n### NPX Package Analysis\n\n```bash\n# Analyze NPX packages with per-package details\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --npx --list --json\n\n# Clean stale NPX packages (older than 30 days)\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --npx --clean --stale-days 30\n\n# Dry run to see what would be cleaned\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --npx --dry-run --stale-days 14\n```\n\n### JavaScript Package Manager Caches\n\n```bash\n# npm, pnpm, yarn caches\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --js-pm --list --json\n\n# Clean JS package manager caches\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --js-pm --clean --safe-delete\n```\n\n### Specialized Integrations\n\n```bash\n# Hugging Face cache\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --hf --list\n\n# PyTorch cache\n.\u002Ftarget\u002Frelease\u002Fport-kill-console cache --torch --list\n\n# Vercel cache (requires VERCEL_TOKEN env var)\nVERCEL_TOKEN=your_token .\u002Ftarget\u002Frelease\u002Fport-kill-console cache --vercel --clean\n\n# Cloudflare cache (requires CLOUDFLARE_TOKEN env var)\nCLOUDFLARE_TOKEN=your_token .\u002Ftarget\u002Frelease\u002Fport-kill-console cache --cloudflare --clean\n```\n\n### Safe Operations\n\nAll cache operations are safe by default:\n- **Safe delete**: Creates timestamped backups before deletion\n- **Restore capability**: `--restore-last` to undo the last cleanup\n- **Dry run**: `--dry-run` to preview changes without executing\n- **Force override**: `--force` to skip confirmations (use with caution)\n\n## Dashboard\n\n![Port Kill Dashboard](assets\u002Fportkill-dashboard.png)\n\nThe dashboard provides real-time process monitoring, system resource tracking, history analytics, and security auditing.\n\n### Running the Dashboard Locally\n\n1. **Navigate to the dashboard directory:**\n   ```bash\n   cd dashboard\n   ```\n\n2. **Install dependencies (first time only):**\n   ```bash\n   npm install\n   ```\n\n3. **Start the dashboard:**\n   ```bash\n   npm run dev\n   ```\n\n4. **Open in your browser:**\n   ```\n   http:\u002F\u002Flocalhost:3002\n   ```\n\nThe dashboard will automatically connect to port-kill and display:\n- Real-time process monitoring on all ports\n- System resource usage (CPU, memory, disk)\n- Process history and analytics\n- Security audit information\n- Port guard status\n\n**Quick start script:**\n```bash\n# From project root - starts dashboard in one command\n.\u002Frun-dashboard.sh\n```\n\nOr on Windows:\n```powershell\n.\\run-dashboard.bat\n```\n\nFor more details, see the [dashboard README](dashboard\u002FREADME.md).\n\nCheck out the full [Kill Suite](https:\u002F\u002Ftreadie.com) for additional tools and features.\n\n## MCP (use Port Kill from Cursor, Claude etc.)\n\nAdd `npx -y 'https:\u002F\u002Fgitpkg.vercel.app\u002Ftreadiehq\u002Fport-kill\u002Fmcp?main'` to your MCP config.\n\n### Available Tools\n\n**Port Management:**\n- `list` - List processes on ports\n- `kill` - Kill processes on ports  \n- `reset` - Reset common dev ports\n- `audit` - Security audit\n- `guardStatus` - Port guard status\n\n**Cache Management (NEW!):**\n- `cacheList` - List all detected caches\n- `cacheClean` - Clean caches with safe backup\n- `cacheRestore` - Restore last cache backup\n- `cacheDoctor` - System diagnostics\n\nFor example for Cursor add to `.cursor\u002Fmcp.json`:\n```\n{\n   \"mcpServers\": {\n      \"port-kill-mcp\": {\n         \"command\": \"npx\",\n         \"args\": [\"-y\", \"https:\u002F\u002Fgitpkg.vercel.app\u002Ftreadiehq\u002Fport-kill\u002Fmcp?main\"]\n      }\n   }\n}\n```\n\nNotes:\n- The server shells out to `.\u002Ftarget\u002Frelease\u002Fport-kill-console` or `port-kill-console` if it is on the PATH. If yours lives elsewhere, set `PORT_KILL_BIN=\u002Fabsolute\u002Fpath\u002Fto\u002Fport-kill-console`. e.g.\n```\n{\n   \"mcpServers\": {\n      \"port-kill-mcp\": {\n         \"command\": \"npx\",\n         \"args\": [\"-y\", \"https:\u002F\u002Fgitpkg.vercel.app\u002Ftreadiehq\u002Fport-kill\u002Fmcp?main\"],\n         \"env\": {\n            \"PORT_KILL_BIN\": \"\u002Fabsolute\u002Fpath\u002Fto\u002Fport-kill-console\"\n         }\n      }\n   }\n}\n```\n\nSee [mcp\u002FREADME.md](mcp\u002FREADME.md) for more information on port-kill-mcp including how to install from source.\n\n## Features\n\n- Real‑time process detection on specific ports or ranges\n- One‑shot cleanup: `--reset`\n- Smart filtering and ignore lists\n- Port Guard Mode (watch\u002Freserve\u002Fauto‑resolve)\n- Security Audit Mode (suspicious ports, risk score, JSON)\n- Remote Mode over SSH\n- Works with Docker; console mode works everywhere\n\n## Presets\n\nPort Kill supports named presets so you can avoid long `--ports` lists and reuse common configurations.\n\nUsage:\n\n```bash\n# List available presets\nport-kill --list-presets\nport-kill-console --list-presets\n\n# Run with a preset\nport-kill --preset dev --console           # macOS app entry also supports console\nport-kill-console --preset dev             # pure console binary (all platforms)\n\n# Other examples\nport-kill-console --preset system --list   # one-time snapshot with the system preset\nport-kill --preset full --json             # JSON output using the full-range preset\n\n# Save a preset from current flags\nport-kill --save-preset dev-mine --preset-desc \"My dev\" --ports 3000,4321,5000,8000,8080,9000\nport-kill-console --save-preset dev-mine --preset-desc \"My dev\" --ports 3000,4321,5000,8000,8080,9000\n\n# Delete a preset\nport-kill --delete-preset dev-mine\nport-kill-console --delete-preset dev-mine\n```\n\nCustom presets:\n\n- User-defined presets live at `~\u002F.port-kill\u002Fpresets.json` and override built-ins when names match\n\n## Common flags\n\n```bash\n--ports 3000,8000,8080          # specific ports\n--ports '6000-9999'             # port ranges (new!)\n--ports '3000,6000-6002,8000'   # mixed individual ports and ranges\n--start-port 3000 --end-port 9000\n--ignore-ports 5353,5000,7000\n--ignore-processes Chrome,rapportd\n--guard-mode --auto-resolve\n--audit --json\n--remote user@server\n```\n\n\n### Manual Installation\n\n1. Clone the repository:\n```bash\ngit clone \u003Crepository-url>\ncd port-kill\n```\n\n2. Install and build (recommended):\n```bash\n.\u002Finstall.sh\n```\n\nOr manually:\n```bash\n.\u002Fbuild-macos.sh\n.\u002Frun.sh\n```\n\n### Linux Installation\n\n1. Clone the repository:\n```bash\ngit clone \u003Crepository-url>\ncd port-kill\n```\n\n2. Install required packages:\n```bash\n# Ubuntu\u002FDebian\nsudo apt-get install libatk1.0-dev libgdk-pixbuf2.0-dev libgtk-3-dev libappindicator3-dev\n\n# Fedora\u002FRHEL\nsudo dnf install atk-devel gdk-pixbuf2-devel gtk3-devel libappindicator-gtk3-devel\n\n# Arch Linux\nsudo pacman -S atk gdk-pixbuf2 gtk3 libappindicator-gtk3\n```\n\n3. Install and build (recommended):\n```bash\n.\u002Finstall.sh\n```\n\nOr manually:\n```bash\n.\u002Fbuild-linux.sh\n.\u002Frun-linux.sh\n```\n\n### Windows Installation\n\n1. Clone the repository:\n```bash\ngit clone \u003Crepository-url>\ncd port-kill\n```\n\n2. Install Rust (if not already installed):\n```bash\n# Download and run rustup-init.exe from https:\u002F\u002Frustup.rs\u002F\n```\n\n3. Install and build (recommended):\n```bash\n.\u002Finstall.sh\n```\n\nOr manually:\n```bash\nbuild-windows.bat\nrun-windows.bat\n```\n\n## Usage\n\n### Basic Usage\n\n**Platform-Specific Run Scripts:**\n- **macOS**: Use `.\u002Frun.sh` \n- **Linux**: Use `.\u002Frun-linux.sh`\n- **Windows**: Use `run-windows.bat`\n\n1. **Start the Application**: Run the appropriate script for your platform with default settings (ports 2000-9000)\n2. **Monitor Status**: Check the status bar for the process count indicator\n3. **Access Menu**: Click on the status bar icon to open the context menu\n4. **Kill Processes**: \n   - Click \"Kill All Processes\" to terminate all development processes\n   - Click individual process entries to kill specific processes\n5. **Quit**: Click \"Quit\" to exit the application\n\n### Configurable Port Monitoring\n\nThe application now supports configurable port ranges and specific port monitoring:\n\n#### Port Range Examples\n```bash\n# Monitor ports 3000-8080\n.\u002Frun.sh --start-port 3000 --end-port 8080          # macOS\n.\u002Frun-linux.sh --start-port 3000 --end-port 8080    # Linux\nrun-windows.bat --start-port 3000 --end-port 8080   # Windows\n\n# Monitor ports 8000-9000\n.\u002Frun.sh -s 8000 -e 9000                            # macOS\n.\u002Frun-linux.sh -s 8000 -e 9000                      # Linux\nrun-windows.bat -s 8000 -e 9000                     # Windows\n```\n\n#### Specific Ports Examples\n```bash\n# Monitor only specific ports (common dev ports)\n.\u002Frun.sh --ports 3000,8000,8080,5000                # macOS\n.\u002Frun-linux.sh --ports 3000,8000,8080,5000          # Linux\nrun-windows.bat --ports 3000,8000,8080,5000         # Windows\n\n# Monitor React, Node.js, and Python dev servers\n.\u002Frun.sh -p 3000,3001,8000,8080                     # macOS\n.\u002Frun-linux.sh -p 3000,3001,8000,8080               # Linux\nrun-windows.bat -p 3000,3001,8000,8080              # Windows\n```\n\n#### Console Mode\n```bash\n# Run in console mode for debugging\n.\u002Frun.sh --console --ports 3000,8000,8080\n\n# Console mode with verbose logging\n.\u002Frun.sh -c -p 3000,8000,8080 -v\n\n# Console mode with PIDs shown\n.\u002Frun.sh --console --show-pid --ports 3000,8000,8080\n\n# Console mode for full-screen mode users (recommended)\n.\u002Frun.sh --console --log-level warn --ports 3000,8000,8080\n```\n\n## Scripting\n\nPort-kill now supports **programmable port management** through scripting:\n\n```bash\n# Three Clear Commands for Different Use Cases:\n\n# 1. kill(pid) - Kill process by PID (one-time action)\n.\u002Fport-kill-console --script \"kill(1234)\"\n\n# 2. clearPort(port) - Kill all processes on a specific port (one-time action)\n.\u002Fport-kill-console --script \"clearPort(3000)\"\n\n# 3. guardPort(port) - Ongoing protection (kill any process that tries to bind to this port)\n.\u002Fport-kill-console --script \"guardPort(3000)\" --ports 3000\n.\u002Fport-kill-console --script \"guardPort(3000, 'my-dev-server')\" --ports 3000\n\n# File-Based Process Management - Kill processes with specific files open!\n.\u002Fport-kill-console --script \"killFile('package-lock.json')\"\n.\u002Fport-kill-console --script \"killFileExt('.lock')\"\n.\u002Fport-kill-console --script \"guardFile('.env')\"\n\n# Advanced example\n.\u002Fport-kill-console --script \"log('Starting'); clearPort(3000); onPort(8080, callback)\" --ports 3000,8080\n```\n\nSee [SCRIPTING.md](SCRIPTING.md) for complete documentation and examples.\n\n## More Detailed Information\n\nThis README is intentionally short. For full docs (all features, flags, API, architecture), see [DETAILED.md](DETAILED.md). Windows users: see [WINDOWS.md](WINDOWS.md).\n\n## License\n\nThis project is licensed under the FSL-1.1-MIT License. See the LICENSE file for details.\n\n## Contributing\n\n1. Fork the repository\n2. Create a feature branch\n3. Make your changes\n4. Add tests if applicable\n5. Submit a pull request\n","Port Kill 是一个帮助开发者查找并释放被占用端口的工具，同时支持管理开发缓存和服务编排。它使用 Rust 语言编写，提供了智能重启、服务检测和编排等核心功能，并通过简洁的命令行界面（CLI）及状态栏应用（仅 macOS）进行操作，适用于 macOS、Linux 和 Windows 平台，也可通过 SSH 远程使用。该工具非常适合在开发过程中遇到端口冲突或需要高效管理本地服务与缓存的场景，能够显著提高开发效率。",2,"2026-06-11 03:45:09","high_star"]