Skip to content
Full guide · step 7 of 815 minutes

Let it run on its own

In one lineHand a big task over at bedtime with clear instructions. In the morning, read its "needs attention" section first.

You need: An AI that can already verify its own work (the verification skill from step 6)

First, make sure you can trust it

Before you let go, all four of these should hold:

  1. You know what good looks like: you did it once, or watched it done once.
  2. It has the tools you’d use: a verification skill, logs.
  3. Every step can prove itself: it stops when it falls short.
  4. Repeated mistakes now have checks: you’ve read a few transcripts.
Until all four hold, run it while you’re watching.

Write bedtime instructions

Bedtime instructions
/pstack:poteto-mode I'm going to bed. In a fresh worktree off main, migrate every caller to the new parser.
Done means: no old callers left, every parser fixture passes, and the old API is deleted.
Keep a decision log. You don't need to ask me before committing.
/loop until done. If you've been stuck for hours and truly can't go on, stop and write down why.

What each sentence does:

  • I’m going to bed: keep going, don’t ask me.
  • Done means: it checks this every round.
  • A fresh worktree: a separate working folder, away from your own work.
  • Don’t need to ask before committing: it won’t sit waiting for your OK.
  • /loop until done: it keeps checking whether it’s done (built into Cursor and Claude Code).
  • If stuck, stop and write why: stopping beats eight hours of busywork.

"Work for 4 hours" isn't a done condition

A duration can’t be checked. Give it a condition that clearly passes or fails.

What it does all night

Before bed

  • Write a done condition
  • A new worktree off main
  • Keep a decision log
  • If stuck, stop and say why

Overnight, each round

  1. Check whether it's done
  2. Make one small change
  3. Verify it
  4. Commit if it helped, drop it if not

One line in the decision log per round

In the morning

  1. /pstack:show-me-your-work
  2. Read “needs attention” first
  3. Then the lines it points to
DiagramYou don't reread the whole night's conversation. The log and “needs attention” are enough.

In the morning: read “needs attention” first

Copy this
/pstack:show-me-your-work Walk me through what you did last night

What you get: a summary. Before handing it back, a model from another family reads the log and adds a “needs attention” section. Read that section first, then the lines it points to.

The log is decisions.tsv (or .audit/<task-name>.tsv when several tasks share a folder). By default it stays on your machine.

Just want progress? Type /pstack:ketchup in that chat. It tells you what changed and what’s waiting on your call.

Several jobs in one night

Copy this
/pstack:poteto-mode Autopilot these five changes, but don't merge. I'll merge them myself in the morning.
What you have Which approach In the morning
Many unrelated PRs Autopilot-full Verified ones merged
Same, you merge Autopilot-stack A row of verified PRs
A multi-day project Orchestrate A coordinator assigning work

Stuck?

I'm not comfortable letting it commit on its own.

Leave out “you don’t need to ask me before committing”, or use Autopilot-stack so it stops once things are verified.

I woke up and it had been going in circles.

Most likely the done condition wasn’t firm enough. Use /pstack:reflect to record the lesson, and /pstack:correct to turn repeated mistakes into checks.

I want to stop it partway.

Tell it “pause” or “I’m going offline”. It wraps up the current step and writes a resume note. A new chat can pick up from there.

Before moving on, check

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.