Skip to content
LumenFlow

Sidekick Pack

The Sidekick Pack adds a compact, workspace-local productivity surface to the kernel. It manages tasks, memory, named channels, routines, and status data under .sidekick/, while keeping every tool call inside the normal kernel policy, scope, and evidence pipeline.

What It Adds

Section titled “What It Adds”

Tasks

Create, update, schedule, complete, and cancel personal or team-local tasks without leaving the governed runtime.

Memory

Store, edit, and recall workspace knowledge, notes, snippets, and lightweight context that agents can reuse later.

Routines

Define reusable multi-step sequences, stop them with routine:update, and inspect the plan before anything runs.

Channels

Use named channels for lightweight communication, discovery, and local cleanup inside the workspace.

Tool Surface

Section titled “Tool Surface”

The pack currently exposes 24 tools across five groups:

| Group | Tools | | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Task | sidekick-task:create, sidekick-task:list, sidekick-task:update, sidekick-task:cancel, sidekick-task:complete, sidekick-task:schedule | | Memory | memory:store, memory:recall, memory:update, memory:forget | | Channel | channel:configure, channel:list, channel:delete, channel:send, channel:receive | | Routine | routine:create, routine:list, routine:update, routine:delete, routine:run, sidekick:routine:commit_plan | | System | sidekick:init, sidekick:status, sidekick:export |

Governance Notes

Section titled “Governance Notes”
  • routine:run is still plan-only.
  • routine:update with enabled: false is the stop flow for routines.
  • sidekick-task:cancel is the task terminal destructive action; it is distinct from sidekick-task:complete.
  • sidekick-task:cancel, memory:forget, channel:delete, and routine:delete are approval-gated destructive tools. The kernel pauses them with APPROVAL_REQUIRED until the host resolves the approval.
  • All write-capable and destructive Sidekick tools support dry_run.

Storage Model

Section titled “Storage Model”

All Sidekick state stays under .sidekick/ in the workspace root. The pack treats that directory as its owned state boundary and keeps the data model simple enough to inspect and export.

.sidekick/
  audit/
    events.jsonl
  channels/
    channels.json
    messages.json
  memory/
    memories.json
  routines/
    routines.json
  tasks/
    tasks.json
Section titled “Read Next”