A Service Manager Born from a Rant: One Afternoon, 49M Tokens, and a Tauri Desktop App That Ships
A real, non-trivial desktop app — not a toy demo — was built in an afternoon by describing a problem in plain language and letting the model loop autonomously. The 1M context window held the entire conversation, including the opening rant, through hours of iteration, making multi-turn refinement practical without losing state.
A developer tired of untraceable Java, Go, Python, and Node processes occupying ports on a single Mac described the pain to doubao-seed-evolving on Volcano Engine's Agent Plan. The model didn't start coding — it proposed three architecture options, confirmed seven feature points, then built a Tauri + Vue3 desktop manager in a single afternoon while running in /loop mode.
Three rounds of fixes followed: a white screen from a missing Vue import, unresponsive UI with no loading states, and overlapping modals. Logic bugs were self-corrected; visual glitches required human description. The final tool scans configured directories to detect project type, Node version (from .nvmrc, .node-version, and engines), and start commands, while also reverse-scanning all listening ports system-wide to surface terminal-launched services that live outside any project folder.
The codebase landed at 3,347 lines (2,004 Rust, 1,343 Vue/TS) with no file exceeding 500 lines. Token consumption hit 49 million, all within a ¥49.9/month Medium plan that never triggered a usage warning. The tool is now the developer's daily driver for project start/stop, with Windows adaptation and open-sourcing planned next.
The model's instinct to propose options and confirm requirements before coding — rather than jumping straight to implementation — mirrors what a senior engineer would do in a spec-less project, and it likely prevented significant rework.
Self-checking behavior (the eight-item checklist after fixing the white screen) suggests the model can be prompted into verification loops that catch regressions autonomously, which is more valuable than the initial code generation.
The 1M context window proved its worth not in a single prompt but across hours of iterative refinement: the model still recalled the opening complaint when asked to summarize at the end.
Visual UI bugs remain a hard boundary for LLM-based development. The model cannot see rendered output, so layout and styling issues require a human-in-the-loop who can describe what looks wrong.
The tool's pragmatic workarounds — stuffing all Node bin directories into PATH, calling OS-specific open commands instead of fighting Tauri's permission model — suggest the model internalized practical, 'just make it work' patterns from its training data rather than over-engineering abstractions.
49 million tokens sounds enormous, but the fixed-price subscription model makes the cost predictable. The developer never worried about a surprise bill, which changes the psychological calculus of letting a model run unattended.