[GH-ISSUE #15] On macOS, when EasyCLI is minimized, the background process CLIProxyAPI gets killed by the system. #8

New issue

Open

opened 2026-02-27 16:46:45 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 16:46:45 +03:00

Owner

Originally created by @S0z1e on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/router-for-me/EasyCLI/issues/15

💻 Steps to Reproduce
1. Launch EasyCLI
2. Wait for CLIProxyAPI to initialize
3. Minimize the EasyCLI window
4. After some time, observe that CLIProxyAPI has been terminated

📋 Expected Behavior

Minimizing EasyCLI should not cause the CLIProxyAPI background process to be killed.
The process should remain active to keep CLI features functional.

🧪 Actual Behavior

After minimizing EasyCLI, the CLIProxyAPI process is terminated by macOS, causing the CLI to stop working.

🧩 Environment
• OS: macOS [14.7.1]
• EasyCLI version: [0.1.27]
• CLIProxyAPI version: [6.3.1]
• Reproducibility: 100%

Originally created by @S0z1e on GitHub (Oct 31, 2025). Original GitHub issue: https://github.com/router-for-me/EasyCLI/issues/15 💻 Steps to Reproduce 1. Launch EasyCLI 2. Wait for CLIProxyAPI to initialize 3. Minimize the EasyCLI window 4. After some time, observe that CLIProxyAPI has been terminated 📋 Expected Behavior Minimizing EasyCLI should not cause the CLIProxyAPI background process to be killed. The process should remain active to keep CLI features functional. 🧪 Actual Behavior After minimizing EasyCLI, the CLIProxyAPI process is terminated by macOS, causing the CLI to stop working. 🧩 Environment • OS: macOS [14.7.1] • EasyCLI version: [0.1.27] • CLIProxyAPI version: [6.3.1] • Reproducibility: 100%