End of support for the Twitch Developer Rig

In 2018, we introduced the Twitch Developer Rig with RFC0004 and launched the beta version in the same year. This native application provided an alternative approach for getting started with an Extension by providing templates, view testing, configuration service management, and Bits-product management. The Developer Rig has helped many developers begin their Extensions journey by centralizing these aspects of development.

Due to portions of the Developer Rig being powered by deprecated internal services and Bits product management becoming available in the developer console, we have made the decision to end support for this application on or soon after January 31, 2023.

What to expect when support ends

Any developer who continues to use the Developer Rig after the above date can expect the following behaviors.


New projects will no longer be able to be created for an existing Twitch Extension.

Extension Views

There should be no noticeable change. Existing projects will be able to test their Extension views.


The monetization tab in the Developer Rig will no longer be available to manage Bits-in-Extensions. Bits product management is now available in the developer console and is the recommended alternative to the Rig. In conjunction with this announcement, Bits product management in the developer console is now considered generally available (promoted from its open beta launch in December). It is also possible to manage Bits products directly with Twitch API endpoints.

Configuration Service

There should be no noticeable change. Existing projects can continue to use this tab to manage configuration service segments. It is also possible to use the configuration service Twitch API endpoints.


Documentation on the developer website will be updated today to indicate the end of support timeline. Resources will be updated to remove mention of the Developer Rig on or soon after the date above.

What action needs to be taken?

Review the behaviors above to consider any changes to your current Extension development workflow. We are also aware that members of the community have built alternative tools and services for Extension developers, and we encourage the sharing of additional resources below if they are helpful to others.

1 Like

F o7

1 Like

TOOT OWN HORN: GitHub - BarryCarlyon/twitch_extension_tools: Tools for Twitch Developers to assist them working on a Twitch Extension

Available for Windows and Mac (and the Mac App Store)

Check the supported features list - GitHub - BarryCarlyon/twitch_extension_tools: Tools for Twitch Developers to assist them working on a Twitch Extension

See also: End of support for the Twitch Developer Rig - #7 by BarryCarlyon for another tool!


Hey @jbulava,

Quick question, do you think it’s possible to make the Developer Rig open source so the community can take care of it?

I’m facing an issue where there’s no tool available to simulate Extension Views, and I have around 15 different views within my extension. Creating 15 Twitch accounts to test them out is just not feasible.


Open sourcing the Rig was discussed, but it was not possible within the timeline for when the underlying internal services were going offline. While it may be possible in the future, there are no active plans to rewrite the Rig to remove the internal source code and make it available publicly.

That being said, if you already have the Developer Rig installed, simulating Extension views should still function as expected.

The view testing part of the Rig should still work.

But it’s difficult to add/change the version of an extension in order to do that testing.

I’ve create a tool that will allow users to inject a project into the rig, bypassing the checks/looksup the rig tries and now fails to do

Windows only right now but this should help some people out.

The Developer Rig Manifester - GitHub - BarryCarlyon/twitch_developerrig_manifester: Lets you add a manifest to the deprecated Twitch Developer Rig bypassing any checks the rig tries and fails to do

1 Like