terminal-runner

2026-01-20 ~ 2026-02-28 · 39 days

AI-Accelerated Abandonment

An AI-fueled burst of activity on 2026-02-28, followed by 38 days of digital silence.

“Born from a bot, buried by the clock.”

Death Type

AI-Assisted Sprint to Stasis

This project exemplifies the 'AI-Assisted Sprint to Stasis' archetype, where 'copilot-swe-agent[bot]' contributed 50% of the 8 total commits, including initial planning and feature additions, all within a single day. The project quickly reached a state of 'completeness' through automated efforts, only to enter immediate and perpetual inactivity, indicating a 'ship it and forget it' mentality facilitated by AI.

Cause of Death

1. Sudden Onset, Sudden End

The entire project's active development, spanning 8 commits, commenced and concluded on a single day, 2026-02-28. This rapid burst accounted for 100% of its lifespan.

2. Bot-Driven Foundations

A full 50% (4 out of 8) of the initial commits were authored by 'copilot-swe-agent[bot]', laying down the 'Initial plan' and 'Add MIT license', suggesting foundational tasks were outsourced to an artificial assistant.

3. Configured for Eternity, Coded for a Day

Detailed game parameters in `config/game.json` (+15 lines) and visual `decoration.json` (+18 lines) were meticulously externalized, yet no further development occurred after their single-day implementation on 2026-02-28.

Vibe Score

7/ 100

Hand-coded. Respect.

What They Did

On 2026-02-28, 'terminal-runner' burst forth, a Rust-based Terminal User Interface (TUI) runner game, aspiring to provide endless horizontal-scrolling entertainment with customizable `gravity` and `jump_velocity` via `config/game.json`. It wielded `crossterm` for terminal wizardry and `rand` for procedural chaos, promising an engaging experience within its `0.1.0` version.

Rustcrossterm@0.27rand@0.8serde@1.0serde_json@1.0

Burnout Analysis

The developer, or perhaps their AI assistant, achieved maximum output on 2026-02-28, delivering 8 commits in a single day, 50% of which were attributed to 'copilot-swe-agent[bot]'. This highly concentrated burst of activity, all on a Saturday, was followed by immediate and total silence, indicating a swift sprint to completion rather than a slow decline. No human burnout was observed, only an abrupt cessation of bot-assisted productivity after 24 hours.

Dependency Archaeology

The project's `Cargo.toml` proudly declared `crossterm@0.27` for TUI interaction, `rand@0.8` for game variability, and `serde@1.0` with `serde_json@1.0` for configuration parsing. These 4 direct dependencies were established on day one, enabling a fully-fledged game. A remarkable 4 dependencies were installed for a project that saw only 1 day of development. One could say the dependencies were more committed to the project than the developer's sustained effort.

Autopsy: File Structure

├──terminal-runner/Cargo.tomlThe project's birth certificate, version `0.1.0`, and final resting place for its 4 direct dependencies.

├──terminal-runner/src/config.rsA +234 line testament to config obsession, centralizing structures for a game that lived but a day.

├──terminal-runner/src/game.rsThe +189 lines of core logic, where the character '@' could jump, for exactly one day.

├──terminal-runner/src/render.rsResponsible for +97 lines of TUI rendering, ensuring the game looked good for its short debut.

├──terminal-runner/config/game.json15 lines of configurable `gravity` and `jump_velocity` — settings that outlived the game's development.

├──config/decoration.json18 lines of character types and colors, meticulously planned by a bot, never to be seen by a vast player base.

└──README.mdUpdated with +33 lines, presumably explaining the game's grand vision that concluded on 2026-02-28.

Eulogy Stats

Total Commits: 8
Ambitious Adjectives: 0
Deploy Config: No
Estimated Users: 0 (unless 'copilot-swe-agent[bot]' counts as a user)

Last Words

“Add decoration settings for character types and colors”