Kucedr has two background surfaces: scheduled agent tasks and periodic health checks. Both run in-process, so Kucedr must remain open.

Health Checks

Available. HEALTH.md defines a checklist Kucedr runs in the background.

  • Intervals of Off, 1 minute, 30 minutes, or 1 hour.
  • Runs are skipped while the main or health agent is busy.
  • Optional daily time windows, or inclusive start and end dates.
  • Runs can use an isolated health session so they do not mix into your main transcript.
  • Heading-only or empty checklists are skipped.
  • A response of exactly HEALTH_OK is treated as healthy. Anything else is logged as needing attention.

The Health screen reads, edits, and saves the checklist and configuration. The agent tool can additionally update light-context, isolated-session, skip-when-busy, active-hours, and include-reasoning fields.

The runner applies the selected provider and model, interval, busy checks, active hours or dates, isolated-session behavior, and minimal context. Stored target, direct policy, light-context, and include-reasoning fields are not currently consumed.

Task Scheduler

Kucedr persists cron schedule records with:

  • A name and optional description.
  • A cron expression.
  • Enabled or paused state.
  • An agent prompt.
  • Created and updated timestamps.
  • A provider and model selection reserved for scheduled work.

Create, update, pause, resume, delete, get, list, and run-now operations work against those records. Startup reconciliation reloads and reschedules saved tasks. Scheduled prompts and Run now invoke the agent directly as background runs.

Background tasks receive the full tool catalog by default. A non-empty saved tool allowlist narrows the tools available to that schedule; an empty allowlist keeps the full catalog. Operations that require an interactive permission decision are denied because background runs cannot stop to ask.

Schedules are created and managed through conversation and the /task_list, /create_task, and /delete_task commands rather than through a creation form. The Tasks screen selects the task provider and model, lists saved schedules, and opens details for Run now, enabled state, tool allowlist, and confirmed deletion. Editing a task's prompt or cron expression remains agent-driven.