Skip to content
Treadle

Integrations: your own GitHub and OBS

Updated October 5, 2026

Treadle can show read-only GitHub status (CI and pull requests) and control OBS from the panel. You connect each with your own credentials over your own network — nothing routes through a Treadle server, because there isn't one in the path once you are set up.

GitHub (read-only)

Connect a fine-grained, read-only token — the connection page tells you exactly which read scopes to pick, and never asks for write access. Treadle then shows:

  • CI build — the latest workflow run on each watched repo's default branch (passing, failing or running). The tile goes red when a build fails.
  • Pull requests — how many are waiting on your review.

You choose the repos and how often to check (at least every 15 seconds). Treadle talks only to api.github.com, honours GitHub's rate limits, and stops polling when you disconnect.

OBS Studio (local network)

Connect to OBS's WebSocket on your local network — a loopback, private (192.168.x, 10.x, 172.16–31.x) or .local address only; a public address is refused. Then:

  • Tiles show recording status and time, input levels, and the on-air scene.
  • Buttons can set a scene, toggle recording and toggle mute — a fixed, read-and-control list; nothing else is callable.

Signing out of either integration deletes its Keychain item and drops Treadle's copy immediately.

Integrations are part of the paid plan. See what's free and what's paid.

Questions & answers

Are my tokens safe?
Your credentials stay on your Mac and are used only to reach your own GitHub or OBS. They're never sent to a device or to Treadle.
Does this phone home?
No. The connections go from your Mac to your own services. Treadle runs no server in that path.

Related