// Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents. Use when the user wants to: schedule a recurring task for an agent, set up a one-time future task, list existing scheduled tasks, delete or remove a scheduled task, or automate periodic agent work (reports, checks, reminders, syncs).
Manage your assigned tasks on the TinyAGI kanban board — list tasks, update task status, create new tasks, and add or view comments. Use when: you receive a message with a [task:ID] tag and need to mark it done, you want to check your task queue, you want to propose new work, or you need to add a comment/update to a task. Triggers: 'update task', 'mark task done', 'list my tasks', 'create task', 'check tasks', 'comment on task', 'task comments', or any message containing [task:ID].
Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.
Search for and install skills from the skills registry to agent workspaces. Use when the agent needs to: find available skills, search for skills by keyword, install a skill to a specific agent's workspace, list skills installed on an agent, or manage skill availability across agents. Triggers: 'search skills', 'find a skill', 'install skill', 'add skill to agent', 'what skills are available', 'skill registry', 'browse skills'.
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.
Manage your persistent hierarchical memory — save, update, search, and organize knowledge as markdown files in the memory/ folder. Use when: you learn something worth remembering, the user asks you to remember something, you want to recall past knowledge, you need to reorganize or update existing memories, or you want to search through your memories. Triggers: 'remember this', 'save to memory', 'what do you remember about', 'update memory', 'search memory', 'forget', or when you decide something is worth persisting.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
| name | schedule |
| description | Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents. Use when the user wants to: schedule a recurring task for an agent, set up a one-time future task, list existing scheduled tasks, delete or remove a scheduled task, or automate periodic agent work (reports, checks, reminders, syncs). |
Manage scheduled tasks that deliver messages to agents via the tinyagi API. Schedules can be recurring (cron-based) or one-time (fire once at a specific date/time). Each schedule enqueues a routed message (@agent_id <task>) that the queue processor picks up and invokes.
Schedules are persisted to ~/.tinyagi/schedules.json and run in-process via the croner library — no system crontab required.
Schedules are managed via REST endpoints on the API server:
GET /api/schedules[?agent=ID] — list schedulesPOST /api/schedules — create a schedulePUT /api/schedules/:id — update a scheduleDELETE /api/schedules/:id — delete a scheduleUse the bundled CLI scripts/schedule.sh for shell-based operations.
scripts/schedule.sh create \
--cron "EXPR" \
--agent AGENT_ID \
--message "Task context for the agent" \
[--channel CHANNEL] \
[--sender SENDER] \
[--label LABEL]
--cron — 5-field cron expression (required for recurring). Examples: "0 9 * * *" (daily 9am), "*/30 * * * *" (every 30 min), "0 0 * * 1" (weekly Monday midnight).--agent — Target agent ID (required). Must match an agent configured in settings.json.--message — The task context / prompt sent to the agent (required).--channel — Channel name in the queue message (default: schedule).--sender — Sender name in the queue message (default: Scheduler).--label — Unique label to identify this schedule (default: auto-generated).One-time schedules are created via the REST API by passing runAt (ISO 8601 datetime) instead of cron:
curl -X POST http://localhost:3777/api/schedules \
-H "Content-Type: application/json" \
-d '{
"runAt": "2026-03-20T09:00:00.000Z",
"agentId": "coder",
"message": "Deploy the staging build",
"label": "staging-deploy"
}'
One-time schedules automatically disable themselves after firing.
scripts/schedule.sh list [--agent AGENT_ID]
Lists all tinyagi schedules. Optionally filter by --agent to show only schedules targeting a specific agent.
scripts/schedule.sh delete --label LABEL
scripts/schedule.sh delete --all
Delete a specific schedule by label, or delete all tinyagi schedules.
settings.json or ask the user)."0 9 * * *").scripts/schedule.sh create (recurring) or use the API (one-time) with the parameters.scripts/schedule.sh list.┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-7, 0 and 7 = Sunday)
│ │ │ │ │
* * * * *
| Pattern | Meaning |
|---|---|
0 9 * * * | Daily at 9:00 AM |
0 9 * * 1-5 | Weekdays at 9:00 AM |
*/15 * * * * | Every 15 minutes |
0 */2 * * * | Every 2 hours |
0 0 * * 0 | Weekly on Sunday midnight |
0 0 1 * * | Monthly on the 1st |
30 8 * * 1 | Monday at 8:30 AM |
scripts/schedule.sh create \
--cron "0 9 * * *" \
--agent analyst \
--message "Generate the daily metrics report and post a summary" \
--label daily-report
scripts/schedule.sh create \
--cron "*/30 * * * *" \
--agent devops \
--message "Run health checks on all services and report any issues" \
--label health-check
curl -X POST http://localhost:3777/api/schedules \
-H "Content-Type: application/json" \
-d '{"runAt":"2026-03-20T14:00:00.000Z","agentId":"devops","message":"Deploy v2.1 to production","label":"prod-deploy-v21"}'
# See all schedules
scripts/schedule.sh list
# See only schedules for @coder
scripts/schedule.sh list --agent coder
# Remove one
scripts/schedule.sh delete --label health-check
# Remove all
scripts/schedule.sh delete --all
~/.tinyagi/schedules.json.croner) — no system crontab needed.runAt) auto-disable after firing.Schedules can also be managed via the Schedule tab on each agent's detail page in TinyOffice. The UI provides a calendar view showing upcoming scheduled events and a form to create new schedules (recurring or one-time) without writing cron expressions.