When should you use it?
- Problems pile up overnight on a busy store
- You want routine fixes done before morning
- You need a record of what automation changed
Not for: Stores without staging or backups; Price or inventory changes without owner review
What do you need, and what do you get?
You need
- Store admin API access scoped per agent
- List of safe fixes
- Owner contact for approvals
You get
- Morning report of issues found
- Fixes applied with a log
- Approval requests for risky changes
How does it work, step by step?
- List the checksDecide what to watch: broken links, out-of-stock listings, failed orders, missing images.
- Classify fixesMark each fix as safe to apply or needs approval.
- Give narrow accessEach specialist gets only the permissions its checks need.
- Run overnightSchedule the scan and apply only safe fixes.
- Review the morning reportApprove or reject the queued risky changes and read the log.
The prompt
Our own prompt, inspired by Tushar Agarwal (@TusharA5649881) and written to work in Custom agent and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Run the overnight check for {store}. Checks: {checks}. Safe fixes you may apply: {safe_fixes}. For each issue, either apply a listed safe fix and log it, or add it to an approval list with the proposed change and reason. Never change prices, refunds or customer messages. Finish with a short report for the owner to read at breakfast.
Inspired by Tushar Agarwal (@TusharA5649881): Post on NightShift, an overnight agent fleet for Shopify stores. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A fix judged safe by the agent may not be; keep the safe list explicit and short.
- Without a log, you cannot undo what changed.
Our take
Tushar Agarwal (@TusharA5649881) shipped a hackathon project called NightShift: an autonomous fleet that looks after a Shopify store while the owner sleeps. Five specialist agents detect problems, apply fixes judged safe, and request permission for anything riskier. The split between safe fixes and ask-first changes is what makes this workable. Most overnight issues are dull, a broken image or a sold-out product still promoted. Auto-fix those; ask before price or inventory changes that move money. List the checks explicitly, such as broken links, out-of-stock listings, failed orders and missing images, and mark each fix as safe or needing approval. Keep the safe list short, because a fix the agent judges safe may not be. Each specialist should get only the permissions its checks need. Read the morning report, approve or reject queued changes, and keep the log so anything can be undone. Stores without staging or backups should set those up first.
Where the time goes back: Routine store problems are fixed before customers see them, and you start the day with a short list of decisions.
FAQ
What counts as risky?
Is NightShift a product?
Source and credit
Inspired by Tushar Agarwal (@TusharA5649881). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Post on NightShift, an overnight agent fleet for Shopify stores
- Creator
- Tushar Agarwal (@TusharA5649881)
- Published on
- X
- Original date
- Aug 31, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.