# ADDED: Button that changes Workspaces **URL:** \ **Category:** OSC/PILOT Bugs And Feature Requests\ **Created:** [August 30, 2020, 4:57am UTC](https://forum.oscpilot.com/t/added-button-that-changes-workspaces/180 "2020-08-30T04:57:17Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![malcolm](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.oscpilot.com/malcolm/32/19_2.png) [@malcolm](https://forum.oscpilot.com/u/malcolm)\ **Post date:** [August 30, 2020, 10:46pm UTC](https://forum.oscpilot.com/t/added-button-that-changes-workspaces/180/3 "2020-08-30T22:46:14Z")
In this forum post: > [@Requests from an LD](https://forum.oscpilot.com/t/requests-from-an-ld/136/3): > > Great feedback, I’ll take note of all of these. Excited to see it used in your field. Some thoughts: I’m thinking the way to make this extensible is to add a “OSC Loopback” toggle for widgets, that causes their OSC messages to be sent back to OSC/PILOT instead of out to the target machine. That way you can use the custom OSC messages that OSC/PILOT listens for to do custom operations. The idea here is that instead of an exploding number of widgets/parameters, this feature can be extended just… I suggest one possible workflow I’m considering for this. What are you opinions on it? I’m trying to avoid an explosion of options and widgets for all cases, so something like this loopback method may allow for existing buttons to send quite a few different messages without lots of new parameters. Thoughts? --- _[View the full topic](https://forum.oscpilot.com/t/added-button-that-changes-workspaces/180)._