Intents
The detection layer that decides which built-in capabilities your app needs. Sibling to /docs/capabilities, which describes the capabilities themselves.
How Detection Runs
After every code generation or refinement, the intent detector scores your code against every capability definition. Each capability declares hints (keywords, code patterns, UI hooks); a match adds to that capability's confidence score.
Capabilities that cross the confidence threshold are marked enabled and their SDKs are injected on save. Lower-confidence detections are surfaced in the Capabilities panel as suggestions.
Confidence Scores
Each detection emits a confidence between 0 and 1. Higher means more code patterns matched. You can see the score per capability in the Capabilities panel.
Overriding Detection
Open the Capabilities panel from the editor sidebar. Each detected capability has a toggle. Switching it off removes the SDK from your app on the next save; switching it on adds the SDK even when the detector did not pick it up.
When to Care
Most of the time you should not care. The detector is right often enough that you can ignore it. Read this page when:
- You are adding a feature and want to confirm the detector picked it up before generating.
- You are removing a feature and want to make sure the SDK comes off.
- You are debugging an unexpected SDK in your generated app.
For the list of capabilities themselves, see Capabilities.
FAQs
What is an intent?▾
How is this different from /docs/capabilities?▾
When would I override the detection?▾
Ready to build?
Create your first app for free, no credit card required.