paperclipai/paperclip · error
DEPLOYMENT_MODE_UNSUPPORTED
DEPLOYMENT_MODE_UNSUPPORTED
Error message
Board chat is only available on local single-operator instances
What it means
Error "Board chat is only available on local single-operator instances" thrown in paperclipai/paperclip.
Source
Thrown at server/src/routes/board-chat.ts:118
// is off, not just hidden.
const experimental = await instanceSettingsService(db).getExperimental();
if (experimental.enableConferenceRoomChat !== true) {
res.status(403).json({
error: "Conference Room Chat is not enabled",
code: "FEATURE_DISABLED",
});
return;
}
// The relay spawns the operator's local `claude` CLI with permissions
// skipped (it must run headless), so it is only safe where the requester
// IS the machine operator: local_trusted is loopback-only single-operator
// by construction (see server/src/index.ts boot guards). Refuse everywhere
// else rather than lending the server's shell to remote users.
if (opts.deploymentMode !== "local_trusted") {
res.status(403).json({
error: "Board chat is only available on local single-operator instances",
code: "DEPLOYMENT_MODE_UNSUPPORTED",
});
return;
}
const { companyId, message, taskId } = req.body as {
companyId?: string;
message?: string;
taskId?: string;
};
if (!companyId || !message) {
res.status(400).json({ error: "companyId and message are required" });
return;
}
// The body-supplied companyId must belong to the authenticated actor —
// it scopes issue reads/writes below and is exported to the subprocess.
assertCompanyAccess(req, companyId);View on GitHub (pinned to 120ae5428f)
Solutions
- Use board chat only on a local single-operator instance; it is disabled on multi-user or non-local deployments.
When it happens
Trigger: Thrown at server/src/routes/board-chat.ts:118 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/b5793cb1ddd891b5.
Report an issue: GitHub.