A Windows command-line tool for managing a Pogly overlay through its HTTP API — and an open-source reference for building your own API integrations.
pogly elements add text --text "New follower!" --size 64 --color "#82a5ff" --x 200 --y 150
pogly layouts set-active --name "Starting Soon"
pogly elements list
Feedback and questions: https://discord.gg/pogly API documentation: https://docs.pogly.gg/#http-api
Quick install (PowerShell):
iwr https://cli.pogly.gg -useb | iexThis downloads the latest release, installs it to %LOCALAPPDATA%\Pogly\cli, and adds it to your PATH. The script it runs is install.ps1 if you'd rather read it first.
- Download
pogly.exeandpogly-cli.exefrom the latest release. - Place them like this (
<version>is the release version, e.g.0.1.0):%LOCALAPPDATA%\Pogly\cli\pogly.exe %LOCALAPPDATA%\Pogly\cli\bin\<version>\pogly-cli.exe - Add
%LOCALAPPDATA%\Pogly\clito yourPATH.
Run uninstall.ps1 — it removes the binaries, version store, and PATH entry. Your overlay profiles are kept unless you pass -PurgeConfig.
pogly.exe is a small launcher that runs the selected pogly-cli.exe, so multiple versions can live side by side:
pogly version # show the current version
pogly version upgrade # install and switch to the latest release
pogly version list # list installed versions
pogly version use 0.1.0 # switch to another installed version
Mint an API token in Pogly under Settings → API Access, then register your overlay:
pogly overlay add https://cloud.pogly.gg/overlay?module=<overlay-address> --token pgly_xxxx --nickname main
overlay add accepts a full overlay URL, a raw overlay address (64 hex chars), or a legacy overlay name. The first overlay you add becomes the default; every other command runs against the default unless you pass --overlay <nickname>.
pogly whoami
pogly layouts list
pogly elements add image --url "https://cdn.7tv.app/emote/xxxx/4x.webp" --width 128 --height 128
pogly elements update 42 --x 500 --y 300 --locked true
pogly elements delete 42
| Command | Description |
|---|---|
ping |
Check that the overlay API is reachable (no token needed) |
whoami |
Show the token's label, identity, and permissions |
overlay list|add|update|remove|set-default |
Manage overlay profiles (stored in %APPDATA%\Pogly\cli\config.toml) |
elements list|add <type>|update|delete |
Manage elements; add has text, image, widget, and media subcommands |
elementdata list|add|update|delete |
Manage element data assets |
layouts list|add|duplicate|rename|delete|set-active |
Manage layouts; set-active switches the live scene |
folders list|add|update|delete |
Manage asset folders |
version [list|use|upgrade] |
Show, switch, or upgrade the installed CLI version |
Every command supports --help for its full flag list, --json for the raw API response, and --overlay <nickname> to target a specific profile.
Writes require the matching permission on the token owner's account (e.g. AddElement for elements add); read commands require Whitelisted. Read-only tokens are rejected for all writes.
The examples/ folder shows how to hook the CLI into your stream: Streamer.bot-triggered alerts on subs/raids/channel points, automatic Pogly↔OBS scene sync, live counters, and one rick roll. Anything that can run a program can drive your overlay.
cargo build --release
Produces target\release\pogly-cli.exe (the CLI) and target\release\pogly.exe (the launcher). Run the CLI directly during development: cargo run -p pogly-cli -- <args>.
To test version upgrade against a fork, set POGLY_RELEASES_REPO=<owner>/<repo>.