/resume
Resume previously paused schedules to restore automated executions.
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
/resume
Context preview
What this command does when you run it.
Resume previously paused schedules to restore automated executions.
Command definition
resume.mdResume Schedules
Resume previously paused schedules to restore automated executions.
Arguments
- `<agent-name>` (optional) - Only resume schedules for this agent
- `all` - Resume all disabled schedules across all agents
Instructions
Resume All Schedules for an Agent
curl -X POST "http://backend:8000/api/ops/schedules/resume?agent_name={agent-name}" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY"Resume All Schedules (Platform-wide)
curl -X POST "http://backend:8000/api/ops/schedules/resume" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY"
Response
The API returns:
{
"success": true,
"message": "Resumed X schedule(s)",
"resumed_count": X,
"agent_filter": "agent-name or null"
}Report Format
## Schedules Resumed
Timestamp: {timestamp}
Action: Resumed {resumed_count} schedule(s)
Scope: {agent_name or "All agents"}
### What This Means
- Resumed schedules will execute according to their cron patterns
- Next execution times have been recalculated
- All automation restored to normal operation
### Verification
Use `/ops/schedules/list` to confirm schedules are enabledUse Cases
1. **Post-Maintenance**: Resume schedules after system updates complete 2. **Issue Resolved**: Re-enable automation after debugging 3. **Selective Resume**: Only resume specific agent's schedules
Notes
- Only resumes schedules that were previously enabled
- Does not affect schedules that were manually disabled by users
- Agent must be running for schedules to actually execute
Read more
Resume Schedules
Resume previously paused schedules to restore automated executions.
Arguments
- `<agent-name>` (optional) - Only resume schedules for this agent
- `all` - Resume all disabled schedules across all agents
Instructions
Resume All Schedules for an Agent
curl -X POST "http://backend:8000/api/ops/schedules/resume?agent_name={agent-name}" \
-H "Authorization: Bearer $TRINITY_MCP_API_KEY"Resume All Schedules (Platform-wide)
curl -X POST "http://backend:8000/api/ops/schedules/resume" \ -H "Authorization: Bearer $TRINITY_MCP_API_KEY"
Response
The API returns:
{
"success": true,
"message": "Resumed X schedule(s)",
"resumed_count": X,
"agent_filter": "agent-name or null"
}Report Format
## Schedules Resumed
Timestamp: {timestamp}
Action: Resumed {resumed_count} schedule(s)
Scope: {agent_name or "All agents"}
### What This Means
- Resumed schedules will execute according to their cron patterns
- Next execution times have been recalculated
- All automation restored to normal operation
### Verification
Use `/ops/schedules/list` to confirm schedules are enabledUse Cases
1. **Post-Maintenance**: Resume schedules after system updates complete 2. **Issue Resolved**: Re-enable automation after debugging 3. **Selective Resume**: Only resume specific agent's schedules
Notes
- Only resumes schedules that were previously enabled
- Does not affect schedules that were manually disabled by users
- Agent must be running for schedules to actually execute
Self-hosted AI Agents Platform supporting Claude Code, Codex, Gemini agents. Apache 2.0.
Repo: Abilityai/trinity
Other commands on trinity.
- /ask
Answer a strategic question using accumulated research
Open command - /briefing
Generate daily briefing from research findings
Open command - /opportunities
List and rank all identified opportunities
Open command - /request-research
Ask the researcher to investigate a specific topic
Open command - /research
Run a research cycle on trending topics
Open command - /status
Report on recent research activity and findings count
Open command

