dsh-troubleshoot

Run `dsh --profile web --dump-config` to inspect the assembled configuration and grep for your plugin. Then check whether it is disabled, whether its fiber is ACTIVE, and whether its declared dependencies have providers, since unmet dependencies leave components silently inactive.

This error occurs when the plugin file has a default export. The loader's unwrapExports prefers exports.default, resolving to the bare apply function while discarding named exports like inject and name. Remove the default export and keep only named exports.

Check the frontmatter key casing first: invocation policy keys must be kebab-case like user-invocable, and camelCase like userInvocable causes the entire skill to be discarded. Also verify the name is kebab-case, description exists, and the skill is not in a nested directory.

UNKNOWN_TOOL means the model called a tool absent from the registry. Confirm the providing plugin is in the dump-config output, is not disabled, and its fiber is ACTIVE rather than stuck INACTIVE due to unsatisfied dependencies.

Run `lsof -nP -iTCP:3080 -sTCP:LISTEN` to find which process holds the port. The most common cause is a previous DSH instance that did not shut down cleanly; kill it and restart.

Only inside a plugin's config block. Cordis evaluates !!js solely within config; using it on metadata fields like disabled or isolate produces a truthy expression object, permanently disabling the plugin with no diagnostic output. Use explicit overlay files instead.