How to use Claude to deploy apps with RunOS
The author watched Claude Code fix a database pool type error and a bad migration through RunOS, redeploying until the application ran without intervention.
AddedBuilding, testing, debugging and maintaining software or infrastructure, with code review and checks before changes reach users.
424 use casesShowing 49–72
Preparing search…
The author watched Claude Code fix a database pool type error and a bad migration through RunOS, redeploying until the application ran without intervention.
AddedClaude helped code Uppercut on Mac OS X Tiger, with explicit prompts excluding newer Objective-C features unavailable in Xcode 2.5.
AddedA developer used Codex and Claude Sonnet 4 for nearly all of a SCUMM-like engine, with intermittent direction, manual design fixes, and a major human refactor.
AddedAn Orca experiment compared Codex and Pi teams building chess coaches. Codex finished faster, while Pi’s engine won 18 of 20 games and drew two.
AddedAn engineering leader gave Claude CI artifact access and pass-rate tooling, let it investigate and rerun flaky tests overnight, and reviewed its proposed fixes during the day.
AddedTwo Claude Code instances coordinated podcast and UI work by posting status to Discord, setting timers, checking peer updates, and choosing their next actions.
AddedAn author built separate-context research, Git, and Bash sub-agents that return condensed findings instead of full files, raw diffs, and logs, reporting a 90–95% token reduction on heavy operations.
AddedClaude Code analyzed a messy application through its invariants, prioritized remediation plans and implemented backend and frontend changes. The author reported a stable result but needed a simpler explanation of the analysis.
AddedThe InputRight founder used an architecture LLM, an engineer LLM and Gemini CLI to build an open-source voice intake MVP. Users verify transcribed data in a form by confirming or editing it.
AddedClaude worked overnight from a goal file defining a weighted metric, constraints, and an improvement loop; the author reported 12 commits and a score of 83.
AddedClaude Code split a testing backlog into non-overlapping tasks, launched 26 subagents, and helped the author review the resulting tests over several days.
AddedThe author reports a GUI library and several working media scripts produced over a weekend, validated through demos while acknowledging likely undiscovered bugs.
AddedThe author reports numerous runtime additions, expanded tests, parallel execution under two seconds, and performance improvements while reviewing every line.
AddedThe author reports that Claude resolved output differences between the C and C++ versions, including restoring original behavior where apparent fixes broke byte equivalence.
AddedThe author reports a two-month rewrite with fewer bugs, strong performance and easier feature development, while describing difficult reviews and substantial overtime.
Added FableThe author reports that test_failure_53 passed after Deebo investigated GROUPTOP-related failure hypotheses; the fix remained under review.
Added DeeboThe author reports several recent fixes passed tests and compiled on the first change set, with additional documentation, test, and configuration edits.
Added QoderThe author bought an old Dell Wyse on Grok Bot's advice, installed Ubuntu Server, and granted SSH access. The bot then set up Tailscale and installed a repository they had been working on.
AddedThe author reports 40,000 generated Rust lines and estimates 90% progress after two weeks of nightly iteration, while explicitly expecting additional fixes before the result works.
AddedThe article reports a completed Rust runtime rewrite across over 135 releases, with workload-specific performance and memory improvements and a few dozen resulting regressions.
AddedThe author estimates about 25% of issue-to-Copilot PRs are mergeable as-is and about 50% after comments, while reporting setup compliance and manual verification limitations.
AddedThe author and a coworker report fixing over 200 failing integration tests for parity with the old code in one week, followed by another code review before launch.
AddedThe author reports rebuilding the app, adding mobile clients with feature parity, and reducing monthly costs from about $20 to $0. They also describe remaining code quality issues.
AddedThe author reports a core systems-language prototype in two weeks, followed by context and supervision problems that led them back to manual coding.
Added