CORE · Error
E_PLUGIN_CATEGORY_MISMATCH
Manifest declares one category but the runtime adapter exports a different one.
— · Resolution
How to recover
The package author needs to align `package.json#openagentry.category` with the adapter's runtime `.category` field.
— · The shape
What an instance looks like
throw new AgentryError({
code: 'E_PLUGIN_CATEGORY_MISMATCH',
phase: 'init',
message: '…contextual message…',
context: { /* adapter-specific */ },
suggestedFix: 'The package author needs to align `package.json#openagentry.category` with the adapter\'s runtime `.category` field.',
docs: 'https://openagentry.dev/errors/E_PLUGIN_CATEGORY_MISMATCH',
});
The context field carries adapter-specific
detail (HTTP status, missing env-var names, validation issues). It
never contains secret values.
— · See also
Related codes from @openagentry/cli
-
E_PLUGIN_NOT_FOUNDA plugin declared in `.agentry/workspace.json` is not installed in the workspace. -
E_PLUGIN_BAD_EXPORTPlugin module is missing an adapter shape on its default export. -
E_PLUGIN_LAYOUTCould not locate the plugin's `package.json` near its resolved entry point. -
E_PLUGIN_PACKAGE_JSONA plugin's package.json is not valid JSON. -
E_PLUGIN_NO_MANIFESTPlugin's package.json is missing the `openagentry` manifest block. -
E_WORKSPACE_EXISTSagentry init refused to overwrite an existing `.agentry/workspace.json`. -
E_WORKSPACE_CONFIG_READCould not read `.agentry/workspace.json`. -
E_WORKSPACE_CONFIG_INVALID`.agentry/workspace.json` failed schema validation.