Skip to content

Command Palette Guide

Kiket’s command palette (press Cmd/Ctrl + K) provides fast access to navigation, project actions, AI quick actions, and extension commands. It aggregates capabilities from the workflow runtime, AI agents, and installed extensions into a single searchable interface.

Launching & Basic Usage

  • Open the palette with Cmd/Ctrl + K (or click the launcher in the global header).
  • Type to search: commands, navigation shortcuts, issues, or extensions appear instantly.
  • Use arrow keys/enter to execute; press Esc to close.

Command Groups

Group Description
Global Navigation Built-in shortcuts for dashboards, boards, analytics, admin panels.
Project Actions Runtime operations (refresh analytics, trigger automations, run definitions) scoped to the active project.
AI Quick Actions Commands defined by agent manifests (metadata.command_palette) that run AI workflows like generating summaries or finding risks.
Extensions Commands exposed by installed extensions or definition manifests (contributes.commands).

Built-in Project Actions

Some commands ship with the platform; availability depends on permissions and context: - release.refresh_readiness – reruns the release readiness analyzer for the active milestone. - release.generate_changelog – produces an automated changelog draft using current analytics context. - release.promote_changelog – promotes the most recent draft to the release notes. - knowledge.draft_weekly_status – drafts a weekly status knowledge document (requires Knowledge Automation). - knowledge.ingest_meeting_transcript – opens the knowledge hub to upload a meeting transcript for summarisation (requires Knowledge Automation). - analytics.refresh_dashboards (if defined) – triggers manual analytics refresh. - sla.view_breaches – summarises current imminent/breached SLA events and links directly to the underlying issues.

Extension Commands

Extensions contribute commands via their manifest contributes.commands block. Fields include: - id, title, description, group, icon, permissions - handler – typically extension_event with payload details - shortcut / keywords – help discoverability

AI Agent Commands

Agents expose palette entries when the manifest provides metadata.command_palette. Supported handler options: - agent_id – required agent key from the registry - input – default payload (merged with user input at runtime) - store_result_in – persist outputs to issue fields or comments

Permissions & Governance

  • Users see commands only if they meet the declared permissions (role-based) and have access to the project.
  • System respects organization scoping; commands do not appear for other tenants.
  • Analytics features (e.g., release readiness commands) require milestone update permissions.

Telemetry & Auditing

  • Each command execution records command_palette.execute analytics events with status + metadata.
  • Extension events run through WorkflowExtensionDispatcher; failures surface in extension logs.

Adding Custom Commands

  1. Extensions – define contributes.commands in .kiket/extensions/*/manifest.yml and sync.
  2. AI Agents – add metadata.command_palette to the agent definition (.kiket/agents/*.yml).
  3. Runtime hooks – use the platform’s project action handler to register new command handlers as needed.

Troubleshooting

  • Command missing? Check permissions, manifest sync status, and whether the handler id is unique.
  • Extension errors? Inspect ExtensionEvent logs or the admin analytics history.
  • AI command failure? Verify agent availability and that the runner supports the configured input/output.