/schedule-logs
View execution logs for scheduled tasks
> /plugin marketplace add jshchnz/claude-code-scheduler > /plugin install scheduler@claude-scheduler
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/schedule-logs
Context preview
What this command does when you run it.
View execution logs for scheduled tasks
Command definition
schedule-logs.mddescription: View execution logs for scheduled tasks
allowed-tools: Read, Bash(tail:*), Bash(head:*), Bash(cat:*), Bash(ls:*)
View Execution Logs
Display execution history and logs for scheduled tasks.
Usage
/schedule logs [task-id-or-name] [options]
Process
1. **Determine Scope**
- If task specified: show logs for that task
- If no task: show recent logs across all tasks
2. **Load History**
- Read execution records from task config
- Read log files from `~/.claude/logs/`
3. **Format Output**
- Show execution history table
- Optionally show detailed output
Output Formats
All Tasks (default)
# Recent Executions
| Time | Task | Status | Duration | Trigger |
|-------------------|-------------------|--------|----------|-----------|
| Jan 5 9:00 AM | Daily Code Review | OK | 45s | scheduled |
| Jan 5 6:00 PM | Backup Reminder | OK | 12s | scheduled |
| Jan 4 9:00 AM | Daily Code Review | OK | 38s | scheduled |
| Jan 4 10:00 AM | Weekly Audit | FAIL | 120s | manual |
Showing last 10 executions. Use `/schedule logs --limit 50` for more.
Specific Task
/schedule logs daily-review
# Execution History: Daily Code Review
**Task ID:** a1b2c3d4-...
**Schedule:** Weekdays at 9:00 AM
**Log file:** ~/.claude/logs/a1b2c3d4.log
## Recent Executions
| Time | Status | Duration | Trigger |
|-------------------|--------|----------|-----------|
| Jan 5 9:00 AM | OK | 45s | scheduled |
| Jan 4 9:00 AM | OK | 38s | scheduled |
| Jan 3 9:00 AM | OK | 42s | scheduled |
| Jan 2 9:00 AM | FAIL | 5s | scheduled |
| Jan 1 9:00 AM | OK | 40s | manual |
## Last Execution Output
[Jan 5 9:00 AM - Success]
Reviewing commits from yesterday...
Found 3 commits to review.
...
Detailed Output
/schedule logs daily-review --full
[Shows complete output from last execution]
Options
- `--limit N` - Show last N executions (default: 10)
- `--full` - Show complete output from last execution
- `--status <ok|fail>` - Filter by status
- `--since <date>` - Show executions since date
Log File Location
Logs are stored at:
- `~/.claude/logs/<task-id>.log` - Combined stdout/stderr
- `~/.claude/logs/<task-id>.out.log` - stdout only (macOS)
- `~/.claude/logs/<task-id>.err.log` - stderr only (macOS)
Maintenance
Suggest cleanup if logs are large:
Log file is 15MB. Run `/schedule logs --cleanup` to rotate old logs.
Log retention is configured in schedules.json settings (default: 30 days).
Read more
description: View execution logs for scheduled tasks allowed-tools: Read, Bash(tail:*), Bash(head:*), Bash(cat:*), Bash(ls:*)
View Execution Logs
Display execution history and logs for scheduled tasks.
Usage
/schedule logs [task-id-or-name] [options]
Process
1. **Determine Scope**
- If task specified: show logs for that task
- If no task: show recent logs across all tasks
2. **Load History**
- Read execution records from task config
- Read log files from `~/.claude/logs/`
3. **Format Output**
- Show execution history table
- Optionally show detailed output
Output Formats
All Tasks (default)
# Recent Executions | Time | Task | Status | Duration | Trigger | |-------------------|-------------------|--------|----------|-----------| | Jan 5 9:00 AM | Daily Code Review | OK | 45s | scheduled | | Jan 5 6:00 PM | Backup Reminder | OK | 12s | scheduled | | Jan 4 9:00 AM | Daily Code Review | OK | 38s | scheduled | | Jan 4 10:00 AM | Weekly Audit | FAIL | 120s | manual | Showing last 10 executions. Use `/schedule logs --limit 50` for more.
Specific Task
/schedule logs daily-review # Execution History: Daily Code Review **Task ID:** a1b2c3d4-... **Schedule:** Weekdays at 9:00 AM **Log file:** ~/.claude/logs/a1b2c3d4.log ## Recent Executions | Time | Status | Duration | Trigger | |-------------------|--------|----------|-----------| | Jan 5 9:00 AM | OK | 45s | scheduled | | Jan 4 9:00 AM | OK | 38s | scheduled | | Jan 3 9:00 AM | OK | 42s | scheduled | | Jan 2 9:00 AM | FAIL | 5s | scheduled | | Jan 1 9:00 AM | OK | 40s | manual | ## Last Execution Output [Jan 5 9:00 AM - Success] Reviewing commits from yesterday... Found 3 commits to review. ...
Detailed Output
/schedule logs daily-review --full [Shows complete output from last execution]
Options
- `--limit N` - Show last N executions (default: 10)
- `--full` - Show complete output from last execution
- `--status <ok|fail>` - Filter by status
- `--since <date>` - Show executions since date
Log File Location
Logs are stored at:
- `~/.claude/logs/<task-id>.log` - Combined stdout/stderr
- `~/.claude/logs/<task-id>.out.log` - stdout only (macOS)
- `~/.claude/logs/<task-id>.err.log` - stderr only (macOS)
Maintenance
Suggest cleanup if logs are large:
Log file is 15MB. Run `/schedule logs --cleanup` to rotate old logs.
Log retention is configured in schedules.json settings (default: 30 days).
Put Claude on autopilot. Schedule code reviews, security audits, and anything else - Claude Code runs them automatically, even while you sleep.
Repo: jshchnz/claude-code-scheduler
Other commands on scheduler.
- /schedule-add
Create a new scheduled task for recurring Claude Code execution (project)
Open command - /schedule-history
View execution history for all scheduled tasks with interactive selection
Open command - /schedule-list
List all scheduled tasks with their status and next run times (project)
Open command - /schedule-remove
Remove a scheduled task by ID or name
Open command - /schedule-run
Manually run a scheduled task immediately
Open command - /schedule-status
Check the health and status of the scheduler system
Open command

