Skip to content
CodeBook

Start an overnight order and read its report

Propose supervised cloud work from Claude Code, set a spending limit and stop time, approve the plan, and read exactly why work finished or paused.

Use an overnight work order when several changes need a manager after you close your terminal. CodeBook keeps the plan, evidence and questions on one work order. You can follow it from another signed-in session.

Draft the order

In Claude Code, enter a factory name and a concrete goal. This example permits up to $25 of work at configured rates and gives an absolute stop time. Substitute a future time for your project and include the time zone.

/factory overnight Payments "Migrate the invoice exporter and verify one exported invoice" --max-usd 25 --deadline 2030-05-15T08:00:00-04:00

The command places a planning request in your prompt box. Press Enter to draft the plan. Claude asks CodeBook for the factory’s current policies and proposes numbered milestones, stories and acceptance checks. Review what each change will deliver, what will prove it, and which later steps need a person. CodeBook can also require a runner to be available before proof can finish.

Set spending and time limits

  • --max-usd is an optional whole-order ceiling. Enter USD from 0.01 to 100000.00, with up to two decimal places. It covers the order’s planner, workers, manager and checks at configured rates. CodeBook reserves capacity before metered operations. A missing price or exhausted allowance can hold the next operation.
  • --deadline is an optional future ISO date and time with Z or a numeric offset, such as 2030-05-15T12:00:00Z. At the deadline CodeBook holds new work. A pending human decision can still need attention.
  • Use either option by itself, both, or neither. “Overnight” alone supplies neither a deadline nor a dollar amount. The dedicated manager’s token ceiling covers that manager’s own calls and is shown separately.

The proposal should show the cap and time CodeBook recorded. If your server cannot enforce a requested limit, the manager leaves the proposal unconfirmed. Check the plan and recorded terms before saying proceed. Approval confirms the stories and opens or reuses the work-order manager. Keep the work-order reference (for example, WO-7), its link and the manager reference.

Read from another session

/factory report Payments WO-7

The plugin makes one read-only request. It can display outstanding questions, milestone evidence with commit or run references, and recorded cost. On a server that supplies execution limits, the report also shows the deadline, the amount available, reserved and recorded, and the last operation held. An estimate marked partial or unpriced sandbox time means some usage has no dollar amount. An older server can supply the original milestone and cost report without the additional fields.

Review a production hold

If production monitoring is enabled for this order and a matching alert follows its deployment, the report identifies the hold, the watch owner, and the alert, pull request, deployment and commit when available. Review customer impact in the linked systems. The watch owner or work-order creator decides whether to resume. A newer hold needs its own decision.

In a CodeBook version that supports rollback decisions, find Rollback decision on the held order. For each affected deployment choose Rolled back or Kept deployment. Add a Decision note (optional) of up to 1,000 characters, then select Record and resume. Carry out any actual rollback in the deployment system first.

Plugin 0.23.0 or later includes each recorded decision and note in the report. A hold acknowledged through an older client can say Decision not recorded. Plugin 0.22.0 shows who resumed earlier holds. Reading either report leaves the order’s state alone.

When progress stops

Open the work order in CodeBook. Check the last held operation, remaining funds, deadline, required proof, factory pause, and unanswered milestone questions. Close the terminal only after you have confirmed a cloud order. A local Run here story needs the Claude Code session that is working it. Local checkout and proof requirements