Fleet Logs

Your objective is to show output logs for a CocoFleet instance.

Before proceeding, verify that .cocoplus/ exists. If not: output "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.

Parse arguments: $fleet logs [fleet-id] [instance-id] If missing: output "Usage: $fleet logs [fleet-id] [instance-id]" Then stop.

Log file: .cocoplus/fleet/[instance-id]/output.log If not found: output "No log file found for [instance-id]. The instance may not have started yet." Then stop.

Read state file to determine if instance is still running. Check if PID in state.json is alive using a cross-platform Node.js one-liner: node -e "try{process.kill([pid],0);console.log('alive')}catch(e){console.log('dead')}"

If alive (instance still running):

• Output last 50 lines of output.log
• Append: "[Instance is still running, showing last 50 lines. Re-run $fleet logs to refresh.]"

If dead (instance complete or stopped):

• Output full log content
• Append status summary from state.json (completed/failed, checkpoints satisfied)

Anti-Rationalization

Shortcut / Temptation	Why It Fails
Always show full log regardless of whether instance is running	For running instances, full log output may be many thousands of lines, tail 50 is the correct live view
Show logs without checking instance status first	Showing "complete" status for a still-running instance misleads the developer into thinking work is done

Exit Criteria

• Log content from .cocoplus/fleet/[instance-id]/output.log is displayed
• If instance is running: only last 50 lines shown with a "[still running]" notice
• If instance is complete: full log shown with status summary from state.json (checkpoints satisfied or not)