claude-code-manager
github.com/simonstrumse/claude-code-manager2025-10-09 ~ 2026-01-08 · 91 days
Hyperspeed Prototyping
Achieved PyPI publication in 2 days, then immediately succumbed to the silence of a lone developer.
“A two-day wonder, now a PyPI ghost.”
Death Type
Hyperspeed Architecture Astronaut
This project achieved PyPI publication in 2 days, installing 31 dependencies including 'textual', 'rich', and 'pyyaml' for a TUI application to manage files that didn't exist in its own repo. It built a multi-Python version CI/CD pipeline for a product whose active development period was shorter than a typical weekend. An architectural marvel for a two-day sprint, then an immediate collapse.
Cause of Death
1. The 2-day sprint to PyPI
The project was active for precisely 2 days, from 2026-01-07 to 2026-01-08, with 23 commits made by 'simonstrumse'. This hyper-accelerated development cycle culminated in PyPI publication as 'ccmanager' version 2.0.1, a feat rarely matched by projects with a longer lifespan.
2. Comprehensive CI/CD for a fleeting existence
Despite its brief 2-day life, a robust CI/CD pipeline was meticulously crafted in '.github/workflows/tests.yml'. It tested across five Python versions (3.8-3.12), ensuring quality for a project that would receive no further contributions after day two. Over-preparation for an early demise.
3. 'CLAUDE.md' management without a 'CLAUDE.md' file
The project explicitly aimed to manage 'CLAUDE.md' files, yet no such file was present in the repository's structure. A TUI was built, a scanner developed, and a manager designed, all for a file that seemingly never materialized within its own codebase.
Vibe Score
AI-assisted but human-driven
What They Did
This project, 'Claude Code Manager' (PyPI: 'ccmanager'), was an ambitious Python-based Terminal User Interface (TUI) application, launched on 2026-01-07. It aspired to centralize the management of 'Claude Code' configurations, including MCP servers, skills, and the enigmatic 'CLAUDE.md' files, using 'textual>=0.47.0' for its visual flair. Its first major act was publication to PyPI, achieving version 2.0.1 within 48 hours.
Burnout Analysis
The developer, 'simonstrumse', exhibited a flash-in-the-pan intensity, delivering all 23 commits within a 2-day window from 2026-01-07 to 2026-01-08. This included significant additions like '+2491 lines' to 'mcp_tui.py'. Following the final commit, 'Publish to PyPI', the repository entered a 90-day period of absolute silence, suggesting an immediate and complete cessation of activity post-launch.
Dependency Archaeology
The 'pyproject.toml' declared 'textual>=0.47.0', 'rich>=13.0.0', and 'pyyaml>=6.0' as core dependencies, among a total of 31 dependencies. This substantial dependency footprint was established within the project's initial 2-day lifespan, indicating a rapid embrace of a full-featured stack for a project that would only see 23 commits. The project had more dependencies (31) than its active development days (2).
Autopsy: File Structure
Eulogy Stats
- Total Commits
- 23
- Ambitious Adjectives
- 3
- Deploy Config
- Yes
- Estimated Users
- 0 (unless PyPI download statistics count as 'users')
Last Words
“Publish to PyPI”