Changelog

PushToDisplay for Raycast

Send an update to a board without leaving your keyboard. The extension is in the Raycast store review queue.

• Send Update — compose a message, pick a board and a panel (1–4), and style each block: text size, weight, color, and background.
• Quick Send — type the message, hit Enter, and it lands on your default board.
• Sign in with your Push To Display account. No API keys to manage — the session lives in your macOS Keychain and refreshes on its own.

CLI: auth status you can read (and script)

The CLI landed a few releases of improvements through v0.1.15.

• auth status reports how you're signed in — API key or OAuth2 — when the access token expires, and whether it can refresh.
• Pass --json to get the same info in scripts and agents; exit codes tell you whether you're authenticated.
• When you're not signed in, it says so plainly and points you to auth login.
• Dependencies are now locked, so installs behave the same everywhere.

n8n and Zapier integrations are live

Two no-code ways to push content to a board. Both are verified and available now.

• The official n8n community node (n8n-nodes-pushtodisplay) adds a Send Update step to any workflow. Install it from the n8n UI or npm.
• The Zapier app exposes the same Send Update action to 7,000+ connected apps.
• New docs for both, plus a short n8n walkthrough video.

Business plan on Microsoft Azure Marketplace

Buy the Business plan through your Azure agreement. Seats are billed per assigned user.

• Admins can manage seats in the portal: see your subscription, and assign or unassign users.
• The pricing page and site footer now link to the Marketplace listing.

OAuth apps in the portal

Create and manage OAuth apps from your account — including the one the n8n node uses.

• New OAuth Apps section: create an app, edit it, delete it, or rotate the secret. Client IDs and secrets are shown once, never again.
• The n8n node connects with OAuth2 too: paste your n8n redirect URL, get your client ID and secret, then sign in with your Push To Display account.
• The n8n docs walk through the whole flow step by step.

Three new tutorials

Step-by-step builds for the displays people actually want on a wall.

• GitHub Actions dashboard — build, test, and deploy status on one screen. One YAML file.
• Claude Code hooks — push task completions, errors, and session summaries to a mounted screen.
• Node-RED andon board — line status, output counts, and quality alerts on one screen.

MCP server listed in the official registry

The CLI is the MCP server. It's now registered in the official MCP directory, so agent tools can find it by name.

• Registered as io.github.pushtodisplay/cli.

API Playground walkthrough video

Two minutes, no code: sign in, create an API key, open the Playground, and push a pre-built message to a live iPad display.

Mobile apps 1.2 → 1.4

iOS and Android releases through 1.2–1.4. The sign-in screen now says what the app is for, and shows the ways you can push content: HTTP POST, CLI, MCP server, or GitHub Actions. Free to start, set up in seconds.

Docs landing page

The docs now open on a section grid instead of a bare list — Introduction, Getting Started, HTTP API, CLI, MCP Server, GitHub Action, and Integrations, each with a one-line description.

Email sign-in: errors that make sense

Wrong or expired verification codes now say what happened. Sending a new code works reliably, and after you verify, you land in the right place.

Site and portal polish

A batch of improvements to the site and the web portal.

• New accessibility statement page, plus better focus states, labels, and keyboard navigation across the site.
• Privacy policy rewritten — legal bases, retention periods, and your rights. Terms updated too.
• Copy Board ID button in the portal's Boards section, so wiring up an integration doesn't mean retyping an ID.
• Homepage: new features grid, expanded FAQ, and a clearer headline.

CLI goes stable, GitHub Action hits v1

The CLI reached its first stable releases the same week the GitHub Action went to v1.

• CLI 0.1.6–0.1.9: the first non-alpha releases. Sign-in got smoother, access tokens refresh on 401, and the MCP server handles authentication on connect.
• pushtodisplay/action@v1: push build and deploy status from any GitHub Actions workflow, with per-block text styling (size, weight, color) and a proper publish pipeline.
• Both the CLI and the action now use API keys (pt_...) instead of the old push tokens.

Apps submitted to the App Store and Google Play

Push To Display went to Apple and Google for review. The mobile apps hit version 1.1 two days later, and the web portal, CLI, and action were all ready alongside them.

• The iOS and Android apps were already showing boards, panels, and real-time delivery before the store doors opened.

Kiosk mode for always-on screens

Lock a device to one board and hide every control. Kiosk mode is included in the Business plan and made for displays nobody should touch.

Default board, and board IDs you can't guess

Two small API changes that mattered: send to your default board without naming one, and boards are addressed by signed IDs so a guessed ID can't reach another account's board.

CLI published to npm

The CLI landed on npm. Zero install on most machines — just run it with npx: npx pushtodisplay send "Hello".

• Run it with npx or install it globally.
• First npm releases went out here (0.1.1-alpha) and automated publishing followed in June.

CLI goes open source; GitHub Action added

The CLI became MIT-licensed and the first GitHub Action landed in the same day.

• The CLI now stores credentials in your OS keychain instead of a vault library — tokens sit with your other secrets, not in the app.
• pushtodisplay/action pushes content from CI with API key auth, and secrets are masked in the logs.

CLI 0.1.0 — the first public piece

The first version of the CLI shipped: terminal, MCP server, and CLI auth in one package.

• Commands for sending updates, listing boards, managing devices, and checking auth status.
• A built-in MCP server, so AI agents could push to boards from day one.
• Device-code sign-in for headless machines: no browser needed on the box itself.