Cette page est disponible en anglais.
Build extensions
Use the public TypeScript and React SDK to add capabilities to a Lunaris workspace. An extension can open a standalone tool, define a new resource type, or render a resource view. Start with a working standalone panel, then add only the contracts your workflow needs.
Choose what to build
| Goal | Start here |
|---|---|
| Open a standalone tool from the workspace launcher | Create your first extension |
| Save a new kind of content and give it an editor | Resources and resource views |
| Choose collaborative, key-value, or file storage | Storage and migrations |
| Add commands, search, networking, or exports | Host capabilities |
| Test the installed behavior, then distribute a release | Testing and Publishing |
A resource type defines the schema and storage slots. A resource is one saved instance. A resource view renders that instance and declares which slots it uses. A standalone view can run as a workspace tool without a resource target. External extensions run in a sandbox and request permissions for the host capabilities they need. See Extension contracts.
Version baseline
The SDK package version, manifest api range, sandbox protocol, and extension release version represent different contracts. Use the generated starter files and the target app to determine compatibility.
The SDK source supports manifest API 0.9 and 0.10 and sandbox protocols 6 and 7. A host release must support the API and protocol that your build uses. Check runtime metadata for publishing and use the TypeScript definitions shipped with your installed SDK for exact signatures.
Examples and reference
- Community starter and examples show how to scaffold, package, and use key-value or Yjs storage.
- Public SDK source defines the extension contracts.
- Built-in extension source shows Rich Text, Kanban, and File in use. Follow the public SDK entry points for external extensions.