plugins · extensions · themes
Extend it your way
Orvlet has no vendor-operated marketplace prerequisite. Bundled content ships locally, and everything else comes from sources you explicitly add.
What you can add
Plugins & skills
Plugins bundle commands, agents,
skills, hooks and MCP servers in a plugin.json manifest. Built-in plugins
are seeded locally and respect your uninstall choices across restarts. Personal
sources can be a Git repository, a URL, a local folder or an inline plugin; the
Claude Code marketplace format is supported. Being listed grants no extra trust or
capabilities.
Suggested sources
A static list of well-known licensed plugin, skill and MCP sources ships with the app as a shortcut. Nothing is fetched or added until you press Add, and being suggested does not mean Orvlet reviewed or endorses the content.
MCP servers
Add MCP servers directly, install
.mcpb bundles after review, browse the MCP Registry, and inspect a
server's tools before the agent uses them. Orvlet can also act as an MCP server for
other apps — off by default, over a private socket, with new tasks confirmed by you
in Orvlet.
Extensions
TypeScript or JavaScript extensions and
in-task scripts call the task's tools through the normal approvals. An extension
allowlist can block MCP servers and extensions outright. orvlet:// install
links always open a confirmation sheet; nothing runs on its own.
Themes
Color themes change only the semantic color tokens inside the light or dark appearance: built-ins include Default, Slate, Paper, Forest, Midnight, Dusk, Ocean and High contrast, plus your own theme file. Themes are checked for text contrast with a visible warning when text would be unreadable. Accent, contrast, reduce-motion and font preferences stay independent settings.
Lifecycle you control
Discovery, inspection, installation, configuration, enable/disable, refresh, upgrade and uninstall are separate steps with visible state. A catalog refresh never silently replaces installed content, and a failed source is reported as failed — not as empty. A plugin whose source you removed stays usable and uninstallable; it simply cannot refresh until you add the source again.
Approvals still apply
Installing is not authorizing. Plugin tools run under the same permission modes as built-in tools, folder trust gates project hooks and setup scripts, and an always-allowed MCP tool asks again when its definition changes. The agent can install plugins only with your approval.
Writing your own
Start with a skill (a folder with instructions), graduate to a plugin when you need commands, hooks or an MCP server, and use an extension when you need code in the loop. A Python SDK can also drive the agent CLI. Because Orvlet is Apache-2.0, you may distribute your plugins commercially or privately, under your own name.