This is a submission for the GitHub Copilot CLI Challenge
What I Built
I used Copilot CLI and Copilot SDK to create a CLI application 🖥️ called DevScope.
DevScope is a macOS-first, privacy-focused CLI tool that helps developers understand how they actually spend their time across applications, terminal commands, and browser activity.
Demo
Github code - https://github.com/sonu0702/devscope
My Experience with GitHub Copilot CLI
😌 The Problem
Developers generate a lot of activity data:
- App usage
- Terminal commands
- Browser research
- Commits and tooling
But raw metrics do not answer higher-level questions about focus, intent, or progress. Existing tools either:
- Focus on generic screen time
- Hide logic behind opaque dashboards
- Or do not integrate with developer workflows
DevScope is designed to live in the terminal, stay transparent and explainable, and treat Copilot as a thinking partner instead of just autocomplete.
🚀 GitHub Copilot is used in two distinct ways:
During development
- Writing macOS automation scripts
- Parsing Chrome history
- Designing CLI workflows
- Refactoring collectors and reports
At runtime (Copilot SDK)
- Acting as a reasoning agent
- Summarizing and interpreting developer activity
- Providing goal-aware insights directly in the terminal
This project demonstrates how Copilot can be both a developer tool and a product feature.
Why an Agent?
Raw metrics like “time spent” or “commands used” do not answer higher-level questions such as:
- Was I actually focused today?
- Did my work align with my goals?
- What kind of development work did I do?
To solve this, DevScope is designed to integrate the GitHub Copilot SDK as a reasoning layer on top of locally collected activity data.
This application is in initial stage everyone is welcome to contribute with Idea or code.
Top comments (0)