Extension Development

To build modular desktop extensions, create a directory with manifest.ts, index.ts, and components, then register it with the auto-loading registry for plug-and-play integration. This ensures type-safe development with explicit IPC handlers and store slices.

An auto-loading extension registry automatically discovers and integrates isolated, manifest-driven plugins residing under the extensions/ directory. It enables plug-and-play architecture by loading modules without manual registration, ensuring consistent metadata and integration points.

Structure your manifest by defining metadata, IPC handlers, and store slices within a manifest.ts file in your extension's directory. This manifest-driven approach ensures the plugin remains isolated and integrates consistently with the core desktop app.

Yes, you can add new UI modules, app modes, and tools using this extension architecture. By creating isolated components and registering them, the architecture supports adding diverse functionalities to the desktop app in a plug-and-play fashion.

TypeScript is used for type-safe extension development, ensuring explicit IPC handlers and store slices for cross-module communication. It provides the type safety needed for consistent integration across isolated, manifest-driven plugins.

Manifest-driven desktop extensions require adherence to a standard directory layout (extensions/, scripts/, references/) and specific integration points. Extensions must remain isolated, meaning they depend on the provided registry and IPC mechanisms for cross-module communication.