Guide · Research
Watch a long run from your Lock Screen
Have your agent launch or watch a training run, simulation or pipeline, and keep a live card with the progress and the metric you care about.
Before you start
- Your agent connected to Startr: Claude Code, Claude, or Codex or Grok.
- The agent running somewhere it can read your job's log: your laptop, a lab machine, or over SSH.
Step 1
Keep the agent alive
- The card only moves when the agent sends an update, so the agent session has to outlive your laptop lid. Start it inside tmux or screen on the machine running the job:Then start Claude Code (or your agent) inside it. Detach with Ctrl-b then d; the session keeps running.tmux new -s run
Step 2
Launch the run through the agent
- Paste this, with your script and metric:Run python train.py and watch its log. Keep a Startr card updated each epoch with the epoch count, validation loss and an ETA. Mark it warn if validation loss rises three epochs in a row, alert if the job crashes, and end it with the best result.
- Already running? Point the agent at the log instead:My training job is already running and writing to logs/run3.log. Watch that file and keep a Startr card updated each epoch with the epoch, validation loss and an ETA. End the card when the log says training finished.
Step 3
Runs longer than eight hours
- Each card lasts up to eight hours. Add this line so the agent hands off cleanly:If the run will take longer than seven hours, end the card with the current status before seven hours and start a new card to continue.
If something doesn't work
Quick fixes
The card stopped updating
The agent session probably ended. Reattach with tmux attach -t run and ask it to continue watching. A card with no updates for two hours shows as stale.
Can it run on a cluster node?
If the agent can run commands where the log is (for example over SSH), yes. Nothing is installed inside your job.
I want two runs at once
Free includes one live card. Pro allows five.