What do you want to do?
3 use cases
-
Find which project owns a stale dev server and stop it safely
Trace a listening port to its project and agent, then stop only ordinary host dev processes after confirmation.
- REPO
keith-yan/vibe-service-guardian - Software and DevOps
- Intermediate
View prompt
Using the repo keith-yan/vibe-service-guardian, run `python -m vsg --open` and inspect the service on port <port>. Report its PID, project attribution, and the stale-check evidence. Verify that you do not stop anything unless the service is an ordinary host dev process and the user has typed the stop confirmation.
- REPO
-
Check whether an open-weight model fits your machine before you download it
Compare physical load limits, practical limits, and target SLA limits for a planned user count and concurrency.
- REPO
keith-yan/vibe-service-guardian - Software and DevOps
- Intermediate
View prompt
Using keith-yan/vibe-service-guardian, open the model capacity page with `python -m vsg --open`, enter the plan for <number of users> users at <peak concurrency> concurrency, and report the physical, practical, and target SLA ceilings for <model name>. Verify that each figure lists its risk reasons and that the result is treated as an estimate until a local benchmark is run.
- REPO
-
Run the guardian as a portable Windows app from a zip file
Build a portable Windows x64 zip from the source folder and start or stop the console with included launchers.
- REPO
keith-yan/vibe-service-guardian - Software and DevOps
- Intermediate
View prompt
Using the repo keith-yte/vibe-service-guardian, run `Build-Portable.cmd` in the source folder at <source path>, then confirm the zip <zip file name> exists with a matching `.sha256` file. Verify that the console starts through `Start-VSG.cmd` and stops through `Stop-VSG.cmd`.
- REPO
Quick start with Vibe Service Guardian
- Check you have what it needs: Python 3.10 to 3.12 installed on Windows, macOS, or Linux; A local copy of the repo from https://github.com/keith-yan/vibe-service-guardian; Permission to run a local web console bound to 127.0.0.1.
- Open keith-yan/vibe-service-guardian on GitHub and read the README and license.
- Create a virtual environment with
python -m venv .venvand install the runtime fromrequirements-lockas described in the README source-run section. - Start the console with
python -m vsg --openand open the services monitor. - Open a service detail and compare its project, agent or terminal attribution, and the listed evidence.
- Record whether the service is stale, not stale, or unsure, so the decision is kept in the local operation log.
These steps come from our top use case, Find which project owns a stale dev server and stop it safely, which also has a copy-paste agent prompt.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for keith-yan/vibe-service-guardian
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forDevelopers who run many local dev servers and local AI models on Windows, macOS, or Linux and want to know what is running, why, and whether the machine can handle it.
- Why it is hot108 stars, launched 78 days ago
- LanguagePython
- Sourcegithub.com/keith-yan/vibe-service-guardian ยท Back to Hot repos
Requirements
- Python 3.10 to 3.12 installed on Windows, macOS, or Linux
- A local copy of the repo from https://github.com/keith-yan/vibe-service-guardian
- Permission to run a local web console bound to 127.0.0.1
Add this badge to your README
Maintain Vibe Service Guardian? Show readers where to find these use cases.
Markdown
[](https://dedupedai.com/use-cases/keith-yan-vibe-service-guardian/?utm_source=github&utm_medium=badge&utm_campaign=keith-yan-vibe-service-guardian)
HTML
<a href="https://dedupedai.com/use-cases/keith-yan-vibe-service-guardian/?utm_source=github&utm_medium=badge&utm_campaign=keith-yan-vibe-service-guardian"><img src="https://dedupedai.com/badge/keith-yan/vibe-service-guardian.svg" alt="Use cases on Deduped" height="20"></a>
A static image, no tracking script. About the badge
Questions about Vibe Service Guardian
What is Vibe Service Guardian?
Vibe Service Guardian is a local-first Python tool that links listening services to their project and agent, flags stale dev servers, monitors local AI runtimes, and estimates which open-weight models a machine can run. It is an open-source project on GitHub: https://github.com/keith-yan/vibe-service-guardian.
How do I use Vibe Service Guardian?
Create a virtual environment with python -m venv .venv and install the runtime from requirements-lock as described in the README source-run section; then start the console with python -m vsg --open and open the services monitor; open a service detail and compare its project, agent or terminal attribution, and the listed evidence. The use cases on this page give the full steps and a copy-paste agent prompt for each job.
Who is Vibe Service Guardian for?
Developers who run many local dev servers and local AI models on Windows, macOS, or Linux and want to know what is running, why, and whether the machine can handle it.
What can I do with Vibe Service Guardian?
3 use cases so far, for example: Find which project owns a stale dev server and stop it safely; Check whether an open-weight model fits your machine before you download it; Run the guardian as a portable Windows app from a zip file. Each has steps and a copy-paste agent prompt.
What do I need to run Vibe Service Guardian?
Python 3.10 to 3.12 installed on Windows, macOS, or Linux; A local copy of the repo from https://github.com/keith-yan/vibe-service-guardian; Permission to run a local web console bound to 127.0.0.1.
What are alternatives to Vibe Service Guardian?
Other hot AI repos in Software and DevOps: ECC, Thinkrail, Superpowers, Deep Infer, Instructor.
Is Vibe Service Guardian safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.