JS
JavaScript providers
Run providers through the Node.js bridge and follow the manifest and runtime contract implemented by Mornye.
Explore extensions →Extend the core
Choose what connects.
Keep control of the source.
Mornye stays deliberately small: it resolves metadata, while extensions bring the services and workflows you choose to run.
Build with Mornye
Made to connect
Extend Mornye with the providers and workflows you choose. Review every extension source before installing it.
PY
Python providers
Package a Python provider with its manifest and use the documented Mornye extension API.
Read the guide →DEV
Extension authors
Publish through a registry you control, and let users review the source before installing.
Build an extension →A clear boundary
The core does not pick sides.
No provider, registry or third-party service is configured by default. The maintainer does not review, host or control extensions that users install.
That keeps the application useful for many workflows while leaving source selection, credentials and compliance in the hands of the person running it.
# choose a registry you trust
export MORNYE_REGISTRIES="https://example.com/registry.json"
# install only what you choose
mornye URL ./out --service ext:your-extension
export MORNYE_REGISTRIES="https://example.com/registry.json"
# install only what you choose
mornye URL ./out --service ext:your-extension
Join the network
Bring something useful
There is no application process and no official provider list. Share a focused project, document its requirements, and give users enough information to make an informed choice.
Publishing an extension?
Start with the Writing a Python Extension guide (or the JS extension notes), then publish your own registry URL. Use the ext: prefix when documenting how users should select your module.