> For the complete documentation index, see [llms.txt](https://threadforge.gitbook.io/threadlink-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadforge.gitbook.io/threadlink-documentation/designer-reference/input-prompts.md).

# Input Prompts

Threadlink shows the right button glyph for the active input device, and swaps it when the device changes. It recognises four device families: mouse and keyboard, Xbox, PlayStation, and Switch Pro controllers.

1. Add a **`DextraInputIcon`** component to a UI Image.
2. Set the control it shows (its input control path).

Inside one of Dextra's interfaces, that's all. Elsewhere, an engineer's component must boot and discard it (see [Dextra](/threadlink-documentation/engineer-reference/dextra.md#device-resolution)).

The Dextra Config maps each control and device to a sprite. Designers supply and assign the sprites; engineers set the control paths. Sprites are Addressable assets (see [Registering Scenes, Prefabs and Assets](/threadlink-documentation/designer-reference/registering-content.md)).

If the active device has no sprite, the image is hidden and an error is logged.