BloopAI/vibe-kanban · warning

No setup script configured for this project

Error message

No setup script configured for this project

What it means

Thrown by the RunSetupScript workspace action when workspacesApi.runSetupScript returns success:false with error.type === 'no_script_configured'. This means the backend has no setup script registered for the project, so there is nothing to execute. It is a deliberate, structured error rather than an unexpected failure.

Source

Thrown at packages/web-core/src/shared/actions/index.ts:1167

        },
      });
    },
  },

  // === Script Actions ===
  RunSetupScript: {
    id: 'run-setup-script',
    label: 'Run Setup Script',
    icon: TerminalIcon,
    shortcut: 'R S',
    requiresTarget: ActionTargetType.WORKSPACE,
    isVisible: (ctx) => ctx.hasWorkspace,
    isEnabled: (ctx) => !ctx.isAttemptRunning,
    execute: async (_ctx, workspaceId) => {
      const result = await workspacesApi.runSetupScript(workspaceId);
      if (!result.success) {
        if (result.error?.type === 'no_script_configured') {
          throw new Error('No setup script configured for this project');
        }
        if (result.error?.type === 'process_already_running') {
          throw new Error('Cannot run script while another process is running');
        }
        throw new Error('Failed to run setup script');
      }
    },
  },

  RunCleanupScript: {
    id: 'run-cleanup-script',
    label: 'Run Cleanup Script',
    icon: TerminalIcon,
    shortcut: 'R C',
    requiresTarget: ActionTargetType.WORKSPACE,
    isVisible: (ctx) => ctx.hasWorkspace,
    isEnabled: (ctx) => !ctx.isAttemptRunning,
    execute: async (_ctx, workspaceId) => {

View on GitHub (pinned to 4deb7eca8f)

Solutions

1. Add a setup script to the project configuration (project settings / setup_script field).
2. Hide or disable the RunSetupScript action when no script is configured (extend the action context with hasSetupScript).
3. Verify you are targeting the correct project/workspace — scripts are per-project.
4. If the script was recently added, reload the workspace/project record to pick up the new config.

Example fix

// before
isEnabled: (ctx) => !ctx.isAttemptRunning,
// after
isEnabled: (ctx) => !ctx.isAttemptRunning && ctx.hasSetupScript,
isVisible: (ctx) => ctx.hasWorkspace && ctx.hasSetupScript,

// before running
const ctx = getWorkspaceContext(workspaceId);
if (!ctx.hasWorkspace) return;
if (!ctx.project.setupScript) {
  toast.info('No setup script configured for this project');
  return;
}
await workspacesApi.runSetupScript(workspaceId);

function isNoScriptError(result: RunScriptResult): boolean {
  return result.success === false && result.error?.type === 'no_script_configured';
}

try {
  const result = await workspacesApi.runSetupScript(workspaceId);
  if (!result.success && result.error?.type === 'no_script_configured') {
    toast.info('Add a setup script in project settings first.');
    return;
  }
  if (!result.success) throw new Error(result.error?.message ?? 'Failed to run setup script');
} catch (err) {
  toast.error(String(err));
}

When it happens

Trigger: Executing RunSetupScript on a workspace whose project has no setup script defined in its configuration (setup_script null/empty), so the server responds with { success: false, error: { type: 'no_script_configured' } }.

Common situations: New projects created without a setup script in project config, users deleting the setup script from project settings and later invoking the action, or projects created before the setup-script feature was added.

Related errors

• No cleanup script configured for this project
• No archive script configured for this project
• Failed to run setup script
• Failed to run cleanup script
• Workspace has no repositories configured

AI-assisted analysis of BloopAI/vibe-kanban@4deb7eca8f (2026-08-29). Data as JSON: /api/errors/38c8c13f98e7c416. Report an issue: GitHub.