mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-12 21:53:00 -06:00
docs: rewrite published docs grounded in current source (#100142)
Source-grounded rewrite of 529 published docs pages with per-unit information-loss verification: 1,713 factual corrections cited to src/**, generated surfaces regenerated, frontmatter titles preserved for i18n, release notes pages untouched. All docs gates green. Closes #100141
This commit is contained in:
Peter Steinberger
committed by
GitHub
GitHub
parent
e069cb26f7
commit
f7d7148cf0
+123
-129
@@ -13,20 +13,18 @@ Plugins extend OpenClaw with channels, model providers, agent harnesses, tools,
|
||||
skills, speech, realtime transcription, voice, media understanding, generation,
|
||||
web fetch, web search, and other runtime capabilities.
|
||||
|
||||
Use this page when you want to install a plugin, restart the Gateway, verify
|
||||
that the runtime loaded it, and route common setup failures. For command-only
|
||||
examples, see [Manage plugins](/plugins/manage-plugins). For the full generated
|
||||
inventory of bundled, official external, and source-only plugins, see
|
||||
Use this page to install a plugin, restart the Gateway, verify the runtime
|
||||
loaded it, and route common setup failures. For command-only examples, see
|
||||
[Manage plugins](/plugins/manage-plugins). For the generated inventory of
|
||||
bundled, official external, and source-only plugins, see
|
||||
[Plugin inventory](/plugins/plugin-inventory).
|
||||
|
||||
## Requirements
|
||||
|
||||
Before installing a plugin, make sure you have:
|
||||
|
||||
- an OpenClaw checkout or installation with the `openclaw` CLI available
|
||||
- network access to the selected source, such as ClawHub, npm, or a git host
|
||||
- any plugin-specific credentials, config keys, or operating-system tools named
|
||||
by that plugin's setup docs
|
||||
- network access to the selected source (ClawHub, npm, or a git host)
|
||||
- any plugin-specific credentials, config keys, or OS tools named by that
|
||||
plugin's setup docs
|
||||
- permission for the Gateway that serves your channels to reload or restart
|
||||
|
||||
## Quick start
|
||||
@@ -41,9 +39,9 @@ Before installing a plugin, make sure you have:
|
||||
|
||||
ClawHub is the primary discovery surface for community plugins. During the
|
||||
launch cutover, ordinary bare package specs still install from npm unless
|
||||
they match an official plugin id. Raw `@openclaw/*` package specs that match
|
||||
bundled plugins use the bundled copy from the current OpenClaw build. Use an
|
||||
explicit prefix when you need one source.
|
||||
they match an official plugin id. Raw `@openclaw/*` specs that match a
|
||||
bundled plugin resolve to that bundled copy. Use an explicit source prefix
|
||||
when you need one source specifically.
|
||||
|
||||
</Step>
|
||||
|
||||
@@ -63,41 +61,38 @@ Before installing a plugin, make sure you have:
|
||||
openclaw plugins install --link ./my-plugin
|
||||
```
|
||||
|
||||
Treat plugin installs like running code. Prefer pinned versions when you
|
||||
need reproducible production installs.
|
||||
Treat plugin installs like running code. Prefer pinned versions for
|
||||
reproducible production installs.
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Configure and enable it">
|
||||
Configure plugin-specific settings under `plugins.entries.<id>.config`.
|
||||
Enable the plugin when it is not already enabled:
|
||||
Enable the plugin if it is not already enabled:
|
||||
|
||||
```bash
|
||||
openclaw plugins enable <plugin-id>
|
||||
```
|
||||
|
||||
If your config uses a restrictive `plugins.allow` list, the installed plugin
|
||||
id must be present there before the plugin can load.
|
||||
`openclaw plugins install` adds the installed id to an existing
|
||||
`plugins.allow` list and removes the same id from `plugins.deny` so the
|
||||
explicit install can load after restart.
|
||||
If `plugins.allow` is set, the installed plugin id must be in that list
|
||||
before the plugin can load. `openclaw plugins install` adds the installed
|
||||
id to an existing `plugins.allow` list and removes the same id from
|
||||
`plugins.deny` so the explicit install can load after restart.
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Let the Gateway reload">
|
||||
Installing, updating, or uninstalling plugin code requires a Gateway
|
||||
restart. When a managed Gateway is already running with config reload
|
||||
enabled, OpenClaw detects the changed plugin install record and restarts the
|
||||
Gateway automatically. If the Gateway is not managed or reload is disabled,
|
||||
restart it yourself:
|
||||
restart. A managed Gateway with config reload enabled detects the changed
|
||||
plugin install record and restarts automatically. Otherwise, restart it
|
||||
yourself:
|
||||
|
||||
```bash
|
||||
openclaw gateway restart
|
||||
```
|
||||
|
||||
Enable and disable operations update config and refresh the cold registry.
|
||||
A runtime inspect is still the clearest verification path for live runtime
|
||||
surfaces.
|
||||
Enable/disable update config and the cold registry. A runtime inspect is
|
||||
still the clearest proof of live runtime surfaces.
|
||||
|
||||
</Step>
|
||||
|
||||
@@ -106,9 +101,9 @@ Before installing a plugin, make sure you have:
|
||||
openclaw plugins inspect <plugin-id> --runtime --json
|
||||
```
|
||||
|
||||
Use `--runtime` when you need to prove registered tools, hooks, services,
|
||||
Gateway methods, or plugin-owned CLI commands. Plain `inspect` is a cold
|
||||
manifest and registry check.
|
||||
Use `--runtime` to prove registered tools, hooks, services, Gateway
|
||||
methods, or plugin-owned CLI commands. Plain `inspect` is a cold manifest
|
||||
and registry check only.
|
||||
|
||||
</Step>
|
||||
</Steps>
|
||||
@@ -125,34 +120,35 @@ Before installing a plugin, make sure you have:
|
||||
| local path | You are developing or testing a plugin on the same machine | `openclaw plugins install --link ./my-plugin` |
|
||||
| marketplace | You are installing a Claude-compatible marketplace plugin | `openclaw plugins install <plugin> --marketplace <source>` |
|
||||
|
||||
Bare package specs have special compatibility behavior. If the bare name matches
|
||||
a bundled plugin id, OpenClaw uses that bundled source. If it matches an
|
||||
official external plugin id, OpenClaw uses the official package catalog. Other
|
||||
ordinary bare package specs install through npm during the launch cutover. Raw
|
||||
`@openclaw/*` package specs that match bundled plugins also resolve to the
|
||||
bundled copy before npm fallback. Use `npm:@openclaw/<plugin>@<version>` when
|
||||
you deliberately want the external npm package instead of the image-owned
|
||||
bundled copy. Use `clawhub:`, `npm:`, `git:`, or `npm-pack:` when you need
|
||||
deterministic source selection. See [`openclaw plugins`](/cli/plugins#install)
|
||||
for the full command contract.
|
||||
Bare package specs have special compatibility behavior: a bare name that
|
||||
matches a bundled plugin id uses that bundled source; a bare name that matches
|
||||
an official external plugin id uses the official package catalog; any other
|
||||
bare spec installs through npm during the launch cutover. Raw `@openclaw/*`
|
||||
specs that match bundled plugins also resolve to the bundled copy before npm
|
||||
fallback. Use `npm:@openclaw/<plugin>@<version>` to deliberately install the
|
||||
external npm package instead of the bundled copy. Use `clawhub:`, `npm:`,
|
||||
`git:`, or `npm-pack:` for deterministic source selection. See
|
||||
[`openclaw plugins`](/cli/plugins#install) for the full command contract.
|
||||
|
||||
For npm installs, unpinned package specs and `@latest` choose the newest stable
|
||||
For npm installs, unpinned specs and `@latest` choose the newest stable
|
||||
package that advertises compatibility with this OpenClaw build. If npm's
|
||||
current latest release declares a newer `openclaw.compat.pluginApi` or
|
||||
`openclaw.install.minHostVersion`, OpenClaw scans older stable package versions
|
||||
and installs the newest one that fits. Exact versions and explicit channel tags
|
||||
such as `@beta` stay pinned to the selected package and fail when incompatible.
|
||||
`openclaw.install.minHostVersion` than this build supports, OpenClaw scans
|
||||
older stable versions and installs the newest one that fits. Exact versions
|
||||
and explicit channel tags such as `@beta` stay pinned to the selected package
|
||||
and fail when incompatible.
|
||||
|
||||
### Operator install policy
|
||||
|
||||
Configure `security.installPolicy` to run a trusted local policy command before
|
||||
plugin install or update proceeds. The policy receives metadata plus the staged
|
||||
source path and can allow or block the install. It covers CLI and Gateway-backed
|
||||
plugin install/update paths. Plugin `before_install` hooks run later only in
|
||||
OpenClaw processes where plugin hooks are loaded, so use `security.installPolicy`
|
||||
for operator-owned install decisions. The deprecated
|
||||
`--dangerously-force-unsafe-install` flag is accepted for compatibility but does
|
||||
not bypass install policy or OpenClaw's built-in plugin dependency denylist.
|
||||
Configure `security.installPolicy` to run a trusted local policy command
|
||||
before a plugin install or update proceeds. The policy receives metadata plus
|
||||
the staged source path and can allow or block the install. It covers both CLI
|
||||
and Gateway-backed install/update paths. Plugin `before_install` hooks run
|
||||
later, and only in OpenClaw processes where plugin hooks are loaded, so use
|
||||
`security.installPolicy` for operator-owned install decisions instead. The
|
||||
deprecated `--dangerously-force-unsafe-install` flag is accepted for
|
||||
compatibility but is a no-op: it does not bypass install policy or OpenClaw's
|
||||
built-in plugin dependency denylist.
|
||||
|
||||
See [Skills config](/tools/skills-config#operator-install-policy-securityinstallpolicy)
|
||||
for the shared `security.installPolicy` exec schema used by both skills and
|
||||
@@ -179,49 +175,50 @@ The common plugin config shape is:
|
||||
|
||||
Key policy rules:
|
||||
|
||||
- `plugins.enabled: false` disables all plugins and skips plugin discovery/load
|
||||
work. Stale plugin references are inert while this is active; re-enable
|
||||
plugins before running doctor cleanup when you want stale ids removed.
|
||||
- `plugins.enabled: false` disables all plugins and skips discovery/load
|
||||
work. Stale plugin references stay inert while this is active; re-enable
|
||||
plugins before running doctor cleanup if you want stale ids removed.
|
||||
- `plugins.deny` wins over allow and per-plugin enablement.
|
||||
- `plugins.allow` is an exclusive allowlist. Plugin-owned tools outside the
|
||||
allowlist stay unavailable, even when `tools.allow` includes `"*"`.
|
||||
- `plugins.entries.<id>.enabled: false` disables one plugin while preserving its
|
||||
allowlist stay unavailable even when `tools.allow` includes `"*"`.
|
||||
- `plugins.entries.<id>.enabled: false` disables one plugin while keeping its
|
||||
config.
|
||||
- `plugins.load.paths` adds explicit local plugin files or directories. Managed
|
||||
`plugins install` local paths must be plugin directories or archives; use
|
||||
`plugins.load.paths` for standalone plugin files.
|
||||
- `plugins.load.paths` adds explicit local plugin files or directories.
|
||||
Managed `plugins install` local paths must be plugin directories or
|
||||
archives; use `plugins.load.paths` for standalone plugin files.
|
||||
- Workspace-origin plugins are disabled by default; explicitly enable or
|
||||
allowlist them before using local workspace code.
|
||||
- Bundled plugins follow their built-in default-on/default-off metadata unless
|
||||
config explicitly overrides them.
|
||||
- `plugins.slots.<slot>` chooses one plugin for exclusive categories such as
|
||||
memory and context engines. Slot selection force-enables the selected plugin
|
||||
for that slot by counting as explicit activation; it can load even when it
|
||||
would otherwise be opt-in. `plugins.deny` and
|
||||
`plugins.entries.<id>.enabled: false` still block it.
|
||||
- Bundled opt-in plugins can auto-activate when config names one of their owned
|
||||
surfaces, such as a provider/model ref, channel config, CLI backend, or agent
|
||||
harness runtime.
|
||||
- Bundled plugins follow their built-in default-on/default-off metadata
|
||||
unless config explicitly overrides it.
|
||||
- `plugins.slots.<slot>` (`memory` or `contextEngine`) picks one plugin for an
|
||||
exclusive category. Slot selection counts as explicit activation and
|
||||
force-enables the selected plugin for that slot, even if it would otherwise
|
||||
be opt-in. `plugins.deny` and `plugins.entries.<id>.enabled: false` still
|
||||
block it.
|
||||
- Bundled opt-in plugins can auto-activate when config names one of their
|
||||
owned surfaces, such as a provider/model ref, channel config, CLI backend,
|
||||
or agent harness runtime.
|
||||
- OpenAI-family Codex routing keeps provider and runtime plugin boundaries
|
||||
separate: legacy Codex model refs are legacy config repaired by doctor, while the bundled
|
||||
`codex` plugin owns Codex app-server runtime for canonical `openai/*` agent
|
||||
refs, explicit `agentRuntime.id: "codex"`, and legacy `codex/*` refs.
|
||||
separate: legacy Codex model refs are legacy config that doctor repairs,
|
||||
while the bundled `codex` plugin owns Codex app-server runtime for
|
||||
canonical `openai/*` agent refs, explicit `agentRuntime.id: "codex"`, and
|
||||
legacy `codex/*` refs.
|
||||
|
||||
When `plugins.allow` is unset and non-bundled plugins are auto-discovered from
|
||||
the workspace or global plugin roots, startup logs
|
||||
`plugins.allow is empty; discovered non-bundled plugins may auto-load: ...`.
|
||||
The warning includes discovered plugin ids and, for short lists, a minimal
|
||||
`plugins.allow` snippet. Run
|
||||
[`openclaw plugins list --enabled --verbose`](/cli/plugins#list) or
|
||||
[`openclaw plugins inspect <id>`](/cli/plugins#inspect) with the listed plugin
|
||||
id before copying trusted plugins into `openclaw.json`. The same trust-pinning
|
||||
guidance applies when diagnostics say a plugin loaded
|
||||
`without install/load-path provenance`: inspect that plugin id, then pin the
|
||||
trusted id in `plugins.allow` or reinstall from a trusted source so OpenClaw
|
||||
records install provenance.
|
||||
`plugins.allow is empty; discovered non-bundled plugins may auto-load: ...`
|
||||
with the discovered plugin ids and, for short lists, a minimal `plugins.allow`
|
||||
snippet. Run [`openclaw plugins list --enabled --verbose`](/cli/plugins#list)
|
||||
or [`openclaw plugins inspect <id>`](/cli/plugins#inspect) on the listed
|
||||
plugin id before copying trusted plugins into `openclaw.json`. The same
|
||||
trust-pinning applies when diagnostics say a plugin loaded
|
||||
`without install/load-path provenance`: inspect that plugin id, then pin it in
|
||||
`plugins.allow` or reinstall from a trusted source so OpenClaw records install
|
||||
provenance.
|
||||
|
||||
Run `openclaw doctor` or `openclaw doctor --fix` when config validation reports
|
||||
stale plugin ids, allowlist/tool mismatches, or legacy bundled plugin paths.
|
||||
Run `openclaw doctor` or `openclaw doctor --fix` when config validation
|
||||
reports stale plugin ids, allowlist/tool mismatches, or legacy bundled plugin
|
||||
paths.
|
||||
|
||||
## Understand plugin formats
|
||||
|
||||
@@ -239,23 +236,19 @@ Both formats appear in `openclaw plugins list`, `openclaw plugins inspect`,
|
||||
|
||||
## Plugin hooks
|
||||
|
||||
Plugins can register hooks at runtime, but there are two different APIs with
|
||||
different jobs.
|
||||
Plugins can register hooks at runtime through two different APIs:
|
||||
|
||||
- Use typed hooks via `api.on(...)` for runtime lifecycle hooks. This is the
|
||||
preferred surface for middleware, policy, message rewriting, prompt shaping,
|
||||
and tool control.
|
||||
- Use `api.registerHook(...)` only when you want to participate in the internal
|
||||
hook system described in [Hooks](/automation/hooks). This is mainly for coarse
|
||||
command/lifecycle side effects and compatibility with existing HOOK-style
|
||||
automation.
|
||||
- `api.on(...)` typed hooks for runtime lifecycle events. This is the
|
||||
preferred surface for middleware, policy, message rewriting, prompt
|
||||
shaping, and tool control.
|
||||
- `api.registerHook(...)` for the internal hook system described in
|
||||
[Hooks](/automation/hooks). This is mainly for coarse command/lifecycle side
|
||||
effects and compatibility with existing HOOK-style automation.
|
||||
|
||||
Quick rule:
|
||||
|
||||
- If the handler needs priority, merge semantics, or block/cancel behavior, use
|
||||
typed plugin hooks.
|
||||
- If the handler just reacts to `command:new`, `command:reset`, `message:sent`,
|
||||
or similar coarse events, `api.registerHook(...)` is fine.
|
||||
Quick rule: if the handler needs priority, merge semantics, or
|
||||
block/cancel behavior, use typed hooks. If it just reacts to `command:new`,
|
||||
`command:reset`, `message:sent`, or similar coarse events, `api.registerHook`
|
||||
is fine.
|
||||
|
||||
Plugin-managed internal hooks show up in `openclaw hooks list` with
|
||||
`plugin:<id>`. You cannot enable or disable them through `openclaw hooks`;
|
||||
@@ -264,8 +257,8 @@ enable or disable the plugin instead.
|
||||
## Verify the active Gateway
|
||||
|
||||
`openclaw plugins list` and plain `openclaw plugins inspect` read cold config,
|
||||
manifest, and registry state. They do not prove that an already-running Gateway
|
||||
has imported the same plugin code.
|
||||
manifest, and registry state. They do not prove that an already-running
|
||||
Gateway has imported the same plugin code.
|
||||
|
||||
When a plugin appears installed but live chat traffic does not use it:
|
||||
|
||||
@@ -287,21 +280,22 @@ serves your channels, not only a wrapper or supervisor.
|
||||
| Plugin appears in `plugins list` but runtime hooks do not run | Use `openclaw plugins inspect <id> --runtime --json` and confirm the active Gateway with `gateway status --deep --require-rpc` | Restart the live Gateway after install, update, config, or source changes |
|
||||
| Duplicate channel or tool ownership diagnostics appear | Run `openclaw plugins list --enabled --verbose`, inspect each suspected plugin with `--runtime --json`, and compare channel/tool ownership | Disable one owner, remove stale installs, or use manifest `preferOver` for intentional replacement |
|
||||
| Config says a plugin is missing | Check [Plugin inventory](/plugins/plugin-inventory) for whether it is bundled, official external, or source-only | Install the external package, enable the bundled plugin, or remove stale config |
|
||||
| Config is invalid during install | Read the validation message and run `openclaw doctor --fix` when it points to stale plugin state | Doctor can quarantine invalid plugin config by disabling the entry and removing the invalid payload |
|
||||
| Config is invalid during install | Read the validation message and run `openclaw doctor --fix` if it points to stale plugin state | Doctor can quarantine invalid plugin config by disabling the entry and removing the invalid payload |
|
||||
| Plugin path is blocked for suspicious ownership or permissions | Inspect the diagnostic before the config error | Fix filesystem ownership/permissions, then run `openclaw plugins registry --refresh` |
|
||||
| `OPENCLAW_NIX_MODE=1` blocks lifecycle commands | Confirm the install is managed by Nix | Change plugin selection in the Nix source instead of using plugin mutator commands |
|
||||
| Dependency import fails at runtime | Check whether the plugin was installed through npm/git/ClawHub or loaded from a local path | Run `openclaw plugins update <id>`, reinstall the source, or install local plugin dependencies yourself |
|
||||
|
||||
When stale plugin config still names a no-longer-discoverable channel plugin,
|
||||
Gateway startup skips that plugin-backed channel instead of blocking every
|
||||
other channel. Run `openclaw doctor --fix` to remove stale plugin and channel
|
||||
entries. Unknown channel keys without stale-plugin evidence still fail
|
||||
validation so typos stay visible.
|
||||
config validation downgrades that channel key to a warning instead of a hard
|
||||
failure, so Gateway startup can still serve every other channel. Run
|
||||
`openclaw doctor --fix` to remove stale plugin and channel entries. Unknown
|
||||
channel keys without stale-plugin evidence still fail validation so typos
|
||||
stay visible.
|
||||
|
||||
For intentional channel replacement, the preferred plugin should declare
|
||||
`channelConfigs.<channel-id>.preferOver` with the legacy or lower-priority
|
||||
plugin id. If both plugins are explicitly enabled, OpenClaw keeps that request
|
||||
and reports duplicate channel or tool diagnostics instead of silently choosing
|
||||
and reports duplicate channel/tool diagnostics instead of silently choosing
|
||||
one owner.
|
||||
|
||||
If an installed package reports that it `requires compiled runtime output for
|
||||
@@ -311,12 +305,12 @@ compiled JavaScript, or disable/uninstall the plugin until then.
|
||||
|
||||
### Blocked plugin path ownership
|
||||
|
||||
If plugin diagnostics say
|
||||
If diagnostics say
|
||||
`blocked plugin candidate: suspicious ownership (... uid=1000, expected uid=0 or root)`
|
||||
and config validation follows with `plugin present but blocked`, OpenClaw found
|
||||
plugin files owned by a different Unix user than the process that is loading
|
||||
them. Keep the plugin config in place; fix the filesystem ownership or run
|
||||
OpenClaw as the same user that owns the state directory.
|
||||
and validation follows with `plugin present but blocked`, OpenClaw found
|
||||
plugin files owned by a different Unix user than the process loading them.
|
||||
Keep the plugin config in place; fix the filesystem ownership or run OpenClaw
|
||||
as the same user that owns the state directory.
|
||||
|
||||
For Docker installs, the official image runs as `node` (uid `1000`), so the
|
||||
host bind-mounted OpenClaw config and workspace directories should normally be
|
||||
@@ -334,13 +328,13 @@ sudo chown -R root:root /path/to/openclaw-config/npm
|
||||
```
|
||||
|
||||
After fixing ownership, rerun `openclaw doctor --fix` or
|
||||
`openclaw plugins registry --refresh` so the persisted plugin registry matches
|
||||
the repaired files.
|
||||
`openclaw plugins registry --refresh` so the persisted plugin registry
|
||||
matches the repaired files.
|
||||
|
||||
### Slow plugin tool setup
|
||||
|
||||
If agent turns appear to stall while preparing tools, enable trace logging and
|
||||
check for plugin tool factory timing lines:
|
||||
If agent turns appear to stall while preparing tools, enable trace logging
|
||||
and check for plugin tool factory timing lines:
|
||||
|
||||
```bash
|
||||
openclaw config set logging.level trace
|
||||
@@ -354,17 +348,17 @@ Look for:
|
||||
```
|
||||
|
||||
The summary lists total factory time and the slowest plugin tool factories,
|
||||
including plugin id, declared tool names, result shape, and whether the tool is
|
||||
optional. Slow lines are promoted to warnings when a single factory takes at
|
||||
least 1s or total plugin tool factory prep takes at least 5s.
|
||||
including plugin id, declared tool names, result shape, and whether the tool
|
||||
is optional. Slow lines are promoted to warnings when a single factory takes
|
||||
at least 1s or total plugin tool factory prep takes at least 5s.
|
||||
|
||||
OpenClaw caches successful plugin tool factory results for repeated resolutions
|
||||
with the same effective request context. The cache key includes the effective
|
||||
runtime config, workspace, agent/session ids, sandbox policy, browser settings,
|
||||
delivery context, requester identity, and ownership state, so factories that
|
||||
depend on those trusted fields are re-run when the context changes. If timings
|
||||
stay high, the plugin may be doing expensive work before returning its tool
|
||||
definitions.
|
||||
OpenClaw caches successful plugin tool factory results for repeated
|
||||
resolutions with the same effective request context. The cache key includes
|
||||
the effective runtime config, workspace and agent id, sandbox policy, browser
|
||||
settings, delivery context, requester identity, and ownership state, so
|
||||
factories that depend on those trusted fields re-run when the context
|
||||
changes. If timings stay high, the plugin may be doing expensive work before
|
||||
returning its tool definitions.
|
||||
|
||||
If one plugin dominates the timing, inspect its runtime registrations:
|
||||
|
||||
@@ -373,8 +367,8 @@ openclaw plugins inspect <plugin-id> --runtime --json
|
||||
```
|
||||
|
||||
Then update, reinstall, or disable that plugin. Plugin authors should move
|
||||
expensive dependency loading behind the tool execution path instead of doing it
|
||||
inside the tool factory.
|
||||
expensive dependency loading behind the tool execution path instead of doing
|
||||
it inside the tool factory.
|
||||
|
||||
For dependency roots, package metadata validation, registry records, startup
|
||||
reload behavior, and legacy cleanup, see
|
||||
|
||||
Reference in New Issue
Block a user