Project
Real runs: documented Nightshift shifts
Read a public Nightshift case study with original scope, dated host handoff, selected results, interruptions, verification, and human review.
Updated
What does a real Nightshift run look like?
The AdaptTable contract began in Claude Code, continued in Cursor after an owner stop, and ended in a human-reviewed merged pull request. Its 45-hour span measures contract continuity, not uninterrupted agent execution.
Scope before results
The 12–14 August 2026 AdaptTable contract covered eight top-level items across six roadmap phases. Its shared definition of done included nine adapters, 17 locales, documentation, changesets, tests, browser checks, and Sonar. One branch and local commits kept implementation reviewable.
Timeline and interruption
Claude Code armed the contract on 12 August at 17:20 UTC. When the owner's allowance ran out, the owner stopped that session on 13 August at 17:12. Cursor resumed the same branch and punch list at 17:22. All eight items were ticked by 14 August at 14:27; owner review, further fixes, and CI continued until the PR merged at 19:26.
- 45 hours 7 minutes is elapsed time from arming to final tick, including interruption and handoff.
- 50 hours 6 minutes is elapsed time to merge, including human review.
- Neither duration measures uninterrupted token processing.
Selected result and checks
The merged PR contains 67 commits and closed 57 issues across the six phases. Public case-study evidence reports the full GitHub check suite green before merge, including a Playwright showcase run, and Sonar at zero issues and hotspots. These are results of that reviewed PR, not a promise for another project.
What the owner accepted
The owner inspected the branch, ran additional checks, fixed findings, and merged. The published account does not claim that Nightshift merged itself or that a checked box proved correctness. The cited case study lists no remaining open contract item at final tick; it also records the allowance interruption and separate human review. Read the smaller runs and the bad-night template in the repository for different outcomes.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Help me inspect this run from original contract through commits, verification, interruptions, owner decisions, and open work.What this workflow does not claim
- Elapsed contract duration is not uninterrupted compute time.
- The public result is one reviewed case, not a performance guarantee.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.