multica-ai/multica · error

--no-start cannot be used with --unassign

Error message

--no-start cannot be used with --unassign

What it means

Error "--no-start cannot be used with --unassign" thrown in multica-ai/multica.

Source

Thrown at server/cmd/multica/cmd_issue.go:1395

	return cli.PrintJSON(os.Stdout, result)
}

func runIssueAssign(cmd *cobra.Command, args []string) error {
	toName, _ := cmd.Flags().GetString("to")
	unassign, _ := cmd.Flags().GetBool("unassign")
	noStart, _ := cmd.Flags().GetBool("no-start")
	toNameSet := cmd.Flags().Changed("to")
	toIDSet := cmd.Flags().Changed("to-id")

	if !toNameSet && !toIDSet && !unassign {
		return fmt.Errorf("provide --to <name>, --to-id <uuid>, or --unassign")
	}
	if (toNameSet || toIDSet) && unassign {
		return fmt.Errorf("--to/--to-id and --unassign are mutually exclusive")
	}
	if noStart && unassign {
		return fmt.Errorf("--no-start cannot be used with --unassign")
	}

	client, err := newAPIClient(cmd)
	if err != nil {
		return err
	}

	ctx, cancel := cli.APIContext(context.Background())
	defer cancel()

	issueRef, err := resolveIssueRef(ctx, client, args[0])
	if err != nil {
		return fmt.Errorf("resolve issue: %w", err)
	}

	body := map[string]any{}
	displayTarget := toName
	if unassign {

View on GitHub (pinned to 2c0912b6ec)

Solutions

1. Remove --no-start when using --unassign.

When it happens

Trigger: Thrown at server/cmd/multica/cmd_issue.go:1395 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15). Data as JSON: /api/errors/3ec2af58f971bd6f. Report an issue: GitHub.