It worksthe nightshift.
Nightshift is an AI engineer that picks up your backlog when the team logs off. By 07:00 there is a report on your desk: fixes with tests, pull requests ready to review, and an honest list of what it left for you.
One night on the Halden web repo.
Keep scrolling, the clock follows you.
- 22:00 You log off. Nightshift pulls every ticket in its queue and reads the whole thread, not just the title. 47 tickets in the queue.
- 23:10 Triage. Duplicates get linked, bugs get a reproduction, and everything gets a label and a priority. 4 duplicates, 9 repros.
- 00:30 Fixes, one branch each. Tests come first. Then the smallest change that makes them pass, and nothing it was not asked for. 11 branches.
- 03:40 Checks, twice. Full suite, type check and a review against your style guide. Anything it is unsure of is parked, not guessed. 214 of 214 green.
- 05:30 Pull requests. Readable diffs with the why in the description, assigned to whoever owns the code. 8 opened.
- 07:00 Morning report. One page on your desk: what shipped, what waits for you, and what it could not solve. 40 minutes of review.
Every morning, one receipt.
No dashboard to log into. At 07:00 Nightshift prints the night into one short report, in Slack or your inbox. Every line on it is something it did for you. Point at a line to see how.
Nightshift
halden/web
Shift 22:00 to 07:00, Thu 6 Nov
Report no. 0312
It reads before it types. The full thread, linked docs and the code paths involved, so the fix answers the ticket that was actually written.
Nothing was merged. Nothing touched production. Questions are waiting in Linear.
Sleep well. See you at 22:00.
It keeps three house rules, every shift.
Written into its sandbox, not into a promise on a slide. You can read the policy file in your repo.
Never merges.
Every pull request waits for a human. Branch protection is checked at the start of each shift, and the shift stops if it is off.
Never touches secrets.
It works in a sandbox with read-only config. Production keys and customer data never reach it.
Never guesses.
If a ticket can be read two ways, it parks the ticket with the question instead of picking one.
Pick a shift.
Billed per workspace, not per ticket. The first seven nights are free on every plan.
Solo
For one person and one repo they care about.
- 1 repository
- Report in Slack or email
- GitHub or GitLab
- Up to 30 tickets a night
Start tonight's shiftAdmit one repo
Mon to Fri nights$49a month
Team
Most teams pick this one.
- Up to 10 repositories
- Assigns pull requests by code owner
- Parks questions in Linear or Jira
- Weekends included
Start tonight's shiftAdmit ten repos
Every night$249a month
Company
When the code cannot leave your network.
- Self-hosted runner
- SSO and audit log
- Bring your own model keys
- A named engineer on call
Talk to usAdmit all repos
Every nightCustomPriced per seat
“I used to start Mondays in the issue tracker. Now I start them in code review, with coffee.”
Clock out at ten tonight.
The first seven nights are free. Connect GitHub and Linear in about four minutes, and Nightshift starts at 22:00 your time.