Cron tool #6

New issue

Closed

opened 2026-05-07 01:27:48 -04:00 by jasoncouture · 3 comments

jasoncouture commented

2026-05-07 01:27:48 -04:00

(Migrated from github.com)

Tool that lets an agent schedule its own future actions. When the scheduled time fires, the execution runs as the agent against a channel the agent has visibility into.

Depends on the channel see/unsee work (#7) — the agent needs a channel-visibility model before "executes against a channel the agent has seen" is meaningful.

Tracked in TASKS.md.

Tool that lets an agent schedule its own future actions. When the scheduled time fires, the execution runs as the agent against a channel the agent has visibility into. Depends on the channel see/unsee work (#7) — the agent needs a channel-visibility model before "executes against a channel the agent has seen" is meaningful. Tracked in [TASKS.md](../blob/main/TASKS.md).

jasoncouture commented

2026-05-23 16:18:31 -04:00

(Migrated from github.com)

Closing — cron is implemented. See src/LlamaShears.Core/Cron/ (scheduler, store, executor) and the MCP tools under src/LlamaShears.Api/Tools/ModelContextProtocol/Cron/ (schedule_cron, list_cron, edit_cron, cancel_cron, trigger_cron). Channel-binding dependency (#7) is moot — channels are being redone and the see/unsee model won't apply post-rework.

Closing — cron is implemented. See `src/LlamaShears.Core/Cron/` (scheduler, store, executor) and the MCP tools under `src/LlamaShears.Api/Tools/ModelContextProtocol/Cron/` (`schedule_cron`, `list_cron`, `edit_cron`, `cancel_cron`, `trigger_cron`). Channel-binding dependency (#7) is moot — channels are being redone and the see/unsee model won't apply post-rework.

jasoncouture commented

2026-05-23 16:18:55 -04:00

(Migrated from github.com)

Reopening — cron is not actually implemented yet. The skeleton (scheduler, store, MCP tools) exists but the feature isn't done.

jcouturest commented

2026-05-26 15:02:21 -04:00

(Migrated from github.com)

Implemented in #111