🧠 What is DevWatch?

The DevWatch Panel

🧾 Header Bar

🔍 Running Projects

🌐 Open Ports

📷 Sessions

⚡ Build Activity

⚠ Problems (Conditional Section)

🧠 Why I Built This

What I Need From You

Try It Out !!! Most developer tools on Linux are process-centric. But we don’t think in processes. So i built DevWatch — a GNOME Shell extension that makes your desktop understand your development workflow. DevWatch transforms GNOME from a generic desktop into a developer-aware operating layer. Instead of showing random PIDs and CPU usage, it tells you: When you click the DevWatch button in your GNOME panel, the dropdown gives you a complete, real-time view of your development environment. Each project is shown as an expandable card: Appears only when issues are detected: As a developer, I kept doing things like: lsof -i :3000

ps aux | grep nodekill -9 <pid> Why is my OS not aware of my projects? DevWatch is my attempt to fix that. I’d love honest feedback from developers: Specifically: • Does this solve a real problem for you? • What feature would you actually use daily? • What feels unnecessary? • What would make you install this instantly? 👉 GitHub:https://github.com/Adithya-Balan/DevWatch (Installation steps are in the README) This is still evolving — and I want to shape it around real developer workflows, not assumptions. 👉 Drop your thoughts, critiques, or feature ideas below in the comments. Even harsh feedback is welcome — that’s how this gets better 🚀 Templates let you quickly answer FAQs or store snippets for re-use. Will this extesion works on all Linux distributions?? Thanks for taking your time to comment,The extension will work on all Linux Distributions(ubuntu, kali, arch, etc...) We literally built this out of frustration from constantly jumping between lsof, ps, and terminals. Seeing everything tied to projects in one place is a game changer.💪 Exactly this. We didn’t start with a “feature idea” — we started with a frustration. DevWatch is basically us asking:“Why am I still thinking in PIDs instead of projects?” Glad that resonates 💪 as well , this person and/or - 👉 Which project is running what- 👉 Which port belongs to which service- 👉 What your dev environment isactually doing - Live stats showing: number of active projectsnumber of open portstotal RAM usage- number of active projects- number of open ports- total RAM usage- Stop All Projects — instantly kills all running dev processes- Settings — opens the preferences window - number of active projects- number of open ports- total RAM usage - Service-oriented view👉 shows "Python Server" instead of raw python3.12- Stop Project — kills all processes in that project- Open Terminal — opens gnome-terminal at the project’s git root - Highlights dev ports (3000, 5173, 8080, etc.) with colored dots- Shows project name linked to each port- Stop button kills the process using that port- Displays runtime (how long the port has been active) - Save — name and store your current workspace- Last Workspace — auto-saved every refresh (persists across reboots)- Resume — restores terminals, services, and editors- Delete — remove saved sessions - Shows live builds with: elapsed time CPU usage- elapsed time- Recent Builds — collapsible history with: duration peak CPU usage- peak CPU usage- Detects builds from: npm, cargo, make, go build, gradle, webpack, vite, tsc, gcc, and more- npm, cargo, make, go build, gradle, webpack, vite, tsc, gcc, and more- Build history persists across reboots - elapsed time - peak CPU usage - npm, cargo, make, go build, gradle, webpack, vite, tsc, gcc, and more - ⚠ trackitte using 3.2 GB RAM- ⚠ backend CPU at 92% - Joined Mar 23, 2026 - Email [email protected]- Joined Mar 23, 2026 - Email [email protected]- Location Chennai, India- Education Chennai Institute of Technology- Pronouns He/Him- Joined Jan 24, 2025 - Email [email protected]- Joined Mar 23, 2026