Executable extensions
Executable extensions
Executable extensions add third-party tools and integrations while keeping their code outside the
Holaryn process. They differ from content-only plugins, which remain the simplest option for skills,
prompts, commands, schedules, policy suggestions, and MCP bundles.
Open Settings → System → Executable extensions to see:
- extension API and rollout status;
- publisher, version, compatibility range, digest, source, and signature status;
- every reviewed host permission;
- contributed tools and settings schemas;
- compatible configuration and rollback version;
- integrity, compatibility, permission, and runtime diagnostics.
An installed extension is disabled by default. Review the exact version, digest, publisher, API
range, and permissions, select the review checkbox, then enable it for new sessions.
The containment boundary has three rules:
- Direct host access is blocked. The container has no workspace, state directory, Docker socket,
host environment, or direct network. - Declared access is brokered. Holaryn checks exact file scopes, HTTPS hosts/methods, SecretRefs,
and canonical tools. - Failures are contained. Timeouts, crashes, malformed messages, and repeated faults stop the
extension without stopping Holaryn.
Use the CLI for packages and versions:
holaryn extension conformance <folder>
holaryn extension install <folder>
holaryn extension inspect <id>
holaryn extension enable <id>
holaryn extension update <id> <new-folder>
holaryn extension rollback <id>
Runtime rollout is initially off. Set HOLARYN_EXTENSIONS_ENABLED=true and restart after review.
Setting it back to false and restarting is the immediate rollback; immutable versions and
configuration remain for diagnosis.
See Build and operate Holaryn executable extensions to author, test,
package, migrate, and troubleshoot an extension.