In the Claude desktop app, a switch moves from Chat to Claude Code, which points Claude at a folder of files. Typing /schedule sets a job to run at a set time, in the cloud, even with the laptop closed. A fictional Clarkson SPEED team, Raquette Aerial, hands Claude its sponsor deck and build schedule and gets a project dashboard; every day at 4 pm Claude reads the 3D-printer logs and updates it. Inside that schedule a second loop checks each print job: did it finish, and if not, how long did it sit dead? After five days a pattern appears — long prints started after 5 pm fail overnight, and each failed drone arm costs a day on the critical path. At 8 am an analysis and a draft email are waiting, not sent. The team captain reads the options, picks one, and decides.