E_PLUGIN_NO_MANIFEST

— · Resolution

How to recover

The package author needs to add an `openagentry` block to package.json with `type`, `category`, `id`, and `protocolVersion`.

— · The shape

What an instance looks like

throw new AgentryError({
  code: 'E_PLUGIN_NO_MANIFEST',
  phase: 'init',
  message: '…contextual message…',
  context: { /* adapter-specific */ },
  suggestedFix: 'The package author needs to add an `openagentry` block to package.json with `type`, `category`, `id`, and `protocolVersion`.',
  docs: 'https://openagentry.dev/errors/E_PLUGIN_NO_MANIFEST',
});

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_FOUND A plugin declared in `.agentry/workspace.json` is not installed in the workspace.
• E_PLUGIN_BAD_EXPORT Plugin module is missing an adapter shape on its default export.
• E_PLUGIN_CATEGORY_MISMATCH Manifest declares one category but the runtime adapter exports a different one.
• E_PLUGIN_LAYOUT Could not locate the plugin's `package.json` near its resolved entry point.
• E_PLUGIN_PACKAGE_JSON A plugin's package.json is not valid JSON.
• E_WORKSPACE_EXISTS agentry init refused to overwrite an existing `.agentry/workspace.json`.
• E_WORKSPACE_CONFIG_READ Could not read `.agentry/workspace.json`.
• E_WORKSPACE_CONFIG_INVALID `.agentry/workspace.json` failed schema validation.