SlopScore
10 crowdincl. 1 critic

gsd-dashboard

GSD Dashboard — Claude Code session monitor with GSD project tracking layer
Open repo on GitHubgithub.com/mirkanu/gsd-dashboard
JavaScript · ★ 4 · 1 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other🤖 claude-code
listed 1 hour ago by mirkanu · last checked 1 hour ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-26: GSD Dashboard — Claude Code session monitor with GSD project tracking layer; its own README says "100% AI-generated: No code was written by hand". 4 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as mirkanu. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
GSD Dashboard — Claude Code session monitor with GSD project tracking layer
created
2026-03-18 · pushed 2 months ago · 1275 commits · 6 contributors
languages
JavaScript 51%TypeScript 45%CSS 2%HTML 1%Shell 1%Dockerfile 0%
paperwork
code of conductcode of conduct filecontributingpull request templatelicensereadme 100% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 1 hour ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
built_with
claude-code
language (detected)
cssdockerfilehtmljavascriptshelltypescript
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: GSD Dashboard — Claude Code session monitor with GSD project tracking layer; its own README says "100% AI-generated: No code was written by hand". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

GSD Dashboard

Personal project: This was built to solve a specific problem for the author. It works for that purpose. It has not been tested for general deployment and is not actively maintained — use it as inspiration or a starting point, not a supported tool.

100% AI-generated: No code was written by hand. Every file was produced by Claude Code via the GSD workflow. The author is a non-programmer building personal tools with AI. PRs are welcome — if one arrives, Claude Code will review and merge it. Issues are unlikely to receive a response.

A personal developer dashboard for tracking Claude Code projects and agent sessions in real time. It combines a GSD project tracker (phase progress, blockers, velocity, completion estimates from .planning/ files) with live Claude Code session monitoring (tool use, cost, Kanban view, browser notifications) — all in one browser tab.

Features

  • GSD project overview — reads .planning/STATE.md, ROADMAP.md, and REQUIREMENTS.md from any number of local projects; shows phase progress bars, status badges, blockers, next action, velocity, and estimated completion
  • Live agent monitoring — real-time session tracking via Claude Code hooks (PreToolUse / PostToolUse / Stop); cost tracking, tool-use breakdown, Kanban view
  • Terminal overlay — embedded xterm.js terminal attached to live tmux sessions per project
  • MCP server — local MCP exposing dashboard operations as tools so Claude Code can query project state directly
  • Global env editor — browse and edit the shared .env.production file from the browser without touching the terminal

Quick setup

Tip: Not sure where to start? Paste the link to this page into Claude, ChatGPT, or any AI assistant and ask it to walk you through the setup. These tools can read GitHub pages and guide you step by step.

  1. Clone and install

    git clone https://github.com/mirkanu/gsddashboard.git
    cd gsddashboard
    npm run setup   # installs deps, creates SQLite DB, installs Claude Code hooks
  2. Configure your projects — copy the example config and point it at your project roots:

    cp gsd-projects.json.example gsd-projects.json

    Edit gsd-projects.json:

    {
      "projects": [
        { "name": "myproject", "root": "/path/to/myproject" }
      ]
    }

    Each project root must contain a .planning/ directory with at least STATE.md and ROADMAP.md.

  3. Start in dev mode

    npm run dev    # server on :4820 + Vite HMR

    Open http://localhost:4820.

  4. Production

    npm run build   # builds React client into server/public
    npm start       # serves everything on port 4820

Stack

  • Backend: Node.js + Express + SQLite + WebSocket
  • Frontend: React 18 + Vite + TypeScript + Tailwind CSS
  • MCP server: local MCP server (mcp/) exposing project state as tools
  • Hook handler: Node.js script wired into Claude Code lifecycle hooks (scripts/)

Credits

Forked from Claude Code Agent Monitor by hoangsonww. Agent monitoring features (sessions, Kanban, cost, WebSocket) are from that project. The GSD layer (project tracking, planning file parsing, stats, terminal overlay) is added on top.

License

MIT

Read the rest on GitHub

Scan report · 2026-09-26
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review — +10 owner has 0 followers

From the balcony · 1 of 4 clapped

  1. Crusoeclapped
    No vulnerable dependencies, local-only data handling via .planning files, no credential requests, and transparent about being a personal tool with AI generation.

Schnitzel, Cap'm Slop and Princess read it and passed. Their reasons are on the balcony, with every other verdict.

Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

0 comments

log in to comment.

report this listing — log in to report