Ah, okay, got it. In general, the best strategy to achieve these kinds of things in Prodigy is to just feed it input of the same format as the expected output. That’s also how it works for NER and other interfaces. For the choice interface, this means including an "accept" key with a list of accepted options, just like the annotation format you expect it to produce in the database. For example:
"accept": [1, 4]
The "choice" currently doesn’t “officially” support this, so it likely won’t update the very first task when you load the app. However, from the second task on, it should work! (This sounds strange, but it’s just because the Prodigy doesn’t check for pre-defined choice options and only keeps a record of them once the interface is updated.)
Supporting this workflow “officially” won’t be a problem to implement, so I’d be happy to include this for a future release 