Create, inspect, pause, resume, or delete recurring Office routines when work should run on a cron schedule or webhook trigger.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Routines fire on cron or webhook and create a fresh task each time, assigned to a specific agent. Use them when work needs to happen on a clock (daily standups, weekly reports, hourly health checks).
$KANDEV_CLI kandev routines list
$KANDEV_CLI kandev routines create \
--name "Daily standup" \
--task-title "What did each agent ship today?" \
--task-description "Summarise yesterday's commits and PRs across the team. Post to #engineering." \
--assignee A-ceo \
--cron "0 9 * * MON-FRI" \
--timezone "Europe/Lisbon"
This creates the routine and attaches a cron trigger in one command. The CLI does two API calls under the hood (routine + trigger); the response is the trigger row.
$KANDEV_CLI kandev routines pause --id R-1
$KANDEV_CLI kandev routines resume --id R-1
$KANDEV_CLI kandev routines delete --id R-1
--name — display name; users see this on the Routines page.--task-title — title for every task this routine creates. Supports {{name}} and {{date}} placeholders.--task-description — agent instructions for each fire.--assignee — the agent ID that receives the task. For coordinator work, this is the CEO; for distributed checks, a worker or specialist.--cron — standard 5-field cron expression.tasks create directly.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Debug an ACP agent CLI by spawning it, speaking raw JSON-RPC, and capturing every frame to a JSONL file. Use when the user asks to probe an agent's capabilities, compare agents, test a prompt against an agent, inspect raw ACP wire frames, or investigate why an agent fails to initialize.
The English summary is being prepared. Showing the original description.
Add a new third-party integration (Jira/Linear-style) — per-workspace credentials, 90s auth-health poller, settings page, link/import buttons. Use when scaffolding a new external service integration.
The English summary is being prepared. Showing the original description.
Delete local branches whose remote has been deleted ([gone]), including their worktrees. Use for branch cleanup after merging PRs.
The English summary is being prepared. Showing the original description.
Review changed code for quality, security, and architecture compliance. Use only when the user explicitly requests local review or a PR finding requires it.
The English summary is being prepared. Showing the original description.
Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says "commit", or before pushing a PR.
The English summary is being prepared. Showing the original description.
Curate the right project context before coding or debugging. Use when starting a new session, switching areas of the codebase, output quality is drifting, a task spans backend/frontend/docs, or external instructions need to be reconciled with Kandev conventions.
The English summary is being prepared. Showing the original description.