Native integration versus shortcut profiles
Choose based on the work you need to execute and the state you need to see.
A shortcut profile sends key combinations. It is useful for familiar actions and easy to adapt to a keyboard map. Blender and the correct editor need focus. A key-only button cannot infer whether X-Ray or autokey is currently enabled.
Native integration uses an extension inside Blender. It can read values and availability, fix a specific object and check context before execution. For exposed Geometry Nodes inputs or rig properties, this makes real-value controls possible.
Blender Studio Control Suite keeps both approaches. Native actions need the companion; old customized shortcuts preserve their settings. Losing the connection does not silently turn native controls into key combinations. The error helps recover the missing component.
Native integration requires an additional installation and compatible versions. Some interactive tools still need an existing editor and focus. The plugin does not rearrange layouts to force execution and cannot support every third-party add-on universally.
A small shortcut profile may be enough for a few familiar commands. If you need state synchronization or parameter adjustment, compare native integrations and try a sample scene. Dials are optional because principal functions also have button alternatives.
Blender Studio Control Suite →