paperclipai/paperclip · error
Cannot execute tool "${namespacedName}" — worker for plugin
Error message
Cannot execute tool "${namespacedName}" — worker for plugin "${pluginId}" is not running. What it means
Execution precondition guard in executeTool: either no worker manager is configured, or the owning plugin's worker is not running, so the tool call cannot be dispatched over the worker channel. The stopped/unconfigured worker is at fault.
Source
Thrown at server/src/services/plugin-tool-registry.ts:419
if (!tool) {
throw new Error(
`Tool "${namespacedName}" is not registered. ` +
`The plugin may not be installed or its worker may not be running.`,
);
}
// 3. Verify the worker manager is available
if (!workerManager) {
throw new Error(
`Cannot execute tool "${namespacedName}" — no worker manager configured. ` +
`Tool execution requires a PluginWorkerManager.`,
);
}
// 4. Verify the plugin worker is running (use DB UUID for worker lookup)
const dbId = tool.pluginDbId;
if (!workerManager.isRunning(dbId)) {
throw new Error(
`Cannot execute tool "${namespacedName}" — ` +
`worker for plugin "${pluginId}" is not running.`,
);
}
// 5. Dispatch the executeTool RPC call to the worker
log.debug(
{ pluginId, pluginDbId: dbId, toolName, namespacedName, agentId: runContext.agentId, runId: runContext.runId },
"executing tool via plugin worker",
);
const rpcParams: ExecuteToolParams = {
toolName,
parameters,
runContext,
};
const result = await workerManager.call(dbId, "executeTool", rpcParams);View on GitHub (pinned to 120ae5428f)
Solutions
- Start the plugin's worker before executing its tools; check worker status and restart the plugin if it crashed.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/src/services/plugin-tool-registry.ts:419 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@120ae5428f (2026-08-18).
Data as JSON: /api/errors/fba8de6f1cd73553.
Report an issue: GitHub.