Bixby Developer Center

Guides

intent

optional

A set of signals that the Bixby planner interprets to create a plan. This is also the structured representation of a user's request.

You define an intent in a number of situations, such as defining what happens in an on-click on user interfaces, modifying or computing inputs to an action, or defining what happens in a refresh, among other situations.

Example

// Give two values (number of dice and number of sides) with the
// goal of rolling dice
intent {
goal: example.dice.RollResultConcept
value: example.dice.NumSidesConcept (6)
value: example.dice.NumDiceConcept (2)
}

Child Keys

goal
optional
A goal specifies one model type, be it a concept or an action, that will be the target of the plan
goal-set
optional
A collection of goals
route
optional
A signal that tags a node as being important, or necessary, to reaching the goal
subplan
optional
Use a subplan to embed one plan intent inside another
value
optional
A signal that signifies the presence of a provided concept value that the plan must use
value-set
optional
Almost identical to value, this signal is a way to specify a (possibly empty) collection of values of the same type