Skip to content
Cove

Extension Overview

Extension overview

Section titled “Extension overview”

Cove’s extension system is meant to be broad enough for real product extensions, not just narrow one-off hooks.

What extensions can contribute

Section titled “What extensions can contribute”

Extensions can add:

  • UI pages, panels, tabs, dialogs, and settings
  • backend APIs and services
  • background jobs
  • themes and visual customization
  • installable tools such as downloaders and scrapers
  • extension-owned storage and related data surfaces

Why that matters

Section titled “Why that matters”

The extension model exists so Cove can stay local and opinionated without being closed off. Users can add capabilities, and developers can build them in a way that still feels like part of the host.

The main boundaries

Section titled “The main boundaries”

Extensions should:

  • request the minimum permissions needed
  • expose behavior clearly enough for administrators to review
  • preserve provenance when changing user-visible metadata
  • keep UI additions consistent with the rest of Cove

Where to go next

Section titled “Where to go next”