Roadmap - SYasJ/StackRadar GitHub Wiki
Roadmap
Where StackRadar is today and where it's heading. Dates are targets, not promises. Ideas and votes are welcome as issues (add a π to the ones you want most).
Current version: 2.2.0 Β· Changelog Β· Download
| Version | Theme | Status | |
|---|---|---|---|
| β | 1.0 | See every project | Released 2026-09 |
| β | 2.0 | Desktop app, agents, skills, schedules, system | Released 2026-10 |
| β | 2.1 | Network Guard, rename, compressed archives | Released 2026-10 |
| β | 2.2 | Control centre: act on everything (ports, tools, caches, agents, skills, schedules, themes) | Released 2026-10 |
| π§ | 2.3 | Trust & reach: signed builds, package managers, CLI | Next, Q4 2026 |
| πΊοΈ | 2.4 | Deeper Network Guard | Q1 2027 |
| π‘ | 3.0 | StackRadar for your agents | 2027 |
β Done
1.0: see every project
- Finds every project under your home folder: purpose, run command, stack, dependencies
- Leaked secrets (masked), risk flags, open ports, last run, git status
- AI / IDE traces and Claude Code token usage
- Reclaim space (
node_modules, build output), runs with a live console, first lineage graph
2.0: the desktop app
- Installable
.dmg,.exe(installer + portable),.AppImage,.deb, built by GitHub Actions - Semantic versioning from one
VERSIONfile,bump_version.py, auto-update from GitHub Releases - System tab: CPU per core, load, memory, swap, disks, network, heaviest processes
- Agents: Claude Code, Codex, Hermes, OpenClaw, Paperclip, Gemini CLI, Cursor, Windsurf, Copilot, Aider, Ollama and more
- Skills: usage counts, never-used and duplicate skills Β· Schedules: cron everywhere, with a timeline
- Duplicates (hash-verified files, copied projects) Β· Updates (npm -g, pip, Homebrew, per project)
- Lineage v2 (force / radial / flow layouts, PNG export), hints on every panel with one off switch
- Security:
127.0.0.1only, per-launch API token, Host-header check
2.1: Network Guard
- Renamed DevRadar β StackRadar, new logo
- Live connections per app with bytes β / β, the project, the script and the source line behind each host
- Signal radar (data out / in, blocked, waiting)
- Allow / deny prompts, Low / Medium / Strict levels, per-app and global rules
- Sensitive data detection (keys, tokens, PII over plain HTTP), exfiltration alerts, static code map
- One-click OS firewall block (Windows Firewall, pf, nftables)
- Archive = verified
.tar.gz/.zipwith restore - Release notes with step-by-step install for unsigned macOS / Windows builds,
SHA256SUMS.txt, version in the window title and About box
2.2: control centre
- Fixed: only one project showing (home folder treated as a project), plain git repos missed, no ports / speeds on macOS
- Scan progress with percent and time left; "still working" indicator on every slow action
- Nested projects, project stage (ready / in progress / incomplete), unfinished folders, categories and tags, βΆ Run on every row, click any tag to see where it's used
- Hand a stalled project or session to another agent and model (Claude Code, Codex, Gemini CLI, Aider, OpenCode)
- Strict duplicates (name + size + content), renamed copies and same-name look-alikes kept apart; sortable tables everywhere
- Ports tab with stop / force kill; Network Guard per-project levels, clickable details, KB / MB totals
- Tools & packages (versions, newest, last used, unused, update / remove, what's new); Caches and Disk space explorers
- Agents: sessions with hand off / tag / archive / delete, tokens by model and by CLI / IDE / app, processes with "stop all but newest"
- Skills: delete, share, consolidate duplicates into
~/.agents/skills; Schedules: pause / resume / re-time / delete - Lineage drill-down with folder sizes; light / dark / auto themes, presets, edit every color, import / export
π§ Next: 2.3 "trust & reach" (Q4 2026)
- Signed and notarized builds: Apple Developer ID + notarization (no more Open Anyway, silent auto-update on macOS), Windows signing via Azure Trusted Signing or an OV certificate (no SmartScreen warning)
- Package managers:
brew install --cask stackradar,winget install StackRadar, Flatpak / AUR - Headless CLI:
stackradar scan --json,stackradar secrets,stackradar netfor scripts and CI - Scheduled scans + desktop notifications: new secret committed, new app talking to an unknown host, disk filling up
- A compact layout for small screens
- Cost estimates next to token counts, and alerts when an agent session runs away
- Linux
arm64builds (Raspberry Pi, ARM laptops)
πΊοΈ Planned: 2.4 "deeper Network Guard" (Q1 2027)
- Per-app bytes on Windows (ETW) so non-guarded apps show β / β like on macOS / Linux
- Per-app blocking without root on Linux (cgroup / nftables per process) and an optional macOS Network Extension
- Traffic history: daily totals per app and host, a "first time seen" timeline
- Import / export rule sets, share a team rule file in the repo (
.stackradar/rules.json) - DNS view: which app looked up which domain
π‘ Exploring: 3.0 "for your agents" (2027)
- MCP server: let Claude Code, Codex & co. ask StackRadar "what runs on port 3000?", "which repos use Stripe?"
- Vulnerability scanning of dependencies (OSV / CVE) next to "outdated"
- Agent cost tracking: tokens and $ per agent, per project, per day, with budgets
- Menu-bar / tray app with the guard prompts and a mini system meter
- VS Code / Cursor extension: open the current repo's StackRadar view in the editor
- Plugin API for custom scanners
Known limitations (today)
| Area | Limitation | Planned fix |
|---|---|---|
| Install | Builds are unsigned: one-time Open Anyway (macOS) / Run anyway (Windows); macOS updates are a manual download | 2.3 signing |
| Network Guard | Only apps started from StackRadar can be cut off per request; other apps are monitored, stopped, or blocked by IP at the OS firewall | 2.4 |
| Network Guard | HTTPS contents are never inspected (by design): sensitive-data checks see plain HTTP and your source code | by design |
| Windows | No per-app byte counts for apps not started from StackRadar | 2.4 ETW |
| Agents | Sessions and tokens are read in detail for Claude Code and Codex; other agents show counts and folders only | as their log formats settle |
| Tools | "Last used" comes from your shell history (zsh / bash / fish); tools started by apps or scripts don't show up there | β |
| Themes | The network radar and lineage graph keep a dark "screen" in light mode | by design |
How versions work
StackRadar uses Semantic Versioning: MAJOR.MINOR.PATCH.
- PATCH (2.1.1): bug fixes only, safe to auto-update.
- MINOR (2.2.0): new features, nothing removed.
- MAJOR (3.0.0): something you rely on changes (settings format, API), with migration notes in the changelog.
The VERSION file is the single source of truth; see Releasing & versioning.