DevDeck User Guide

The Ultimate Mission Control for Developers. A macOS Stream Deck plugin by Dloper.

1. Install and get started

Download DevDeck or DevDeck Lite from the DevDeck download page.
On the DevDeck or DevDeck Lite Elgato Marketplace page that opens, click Open in Stream Deck. Stream Deck installs the plugin for you.
In Stream Deck, find DevDeck or DevDeck Lite in the action list on the right. Drag the action you want onto a key in your Stream Deck layout.
Select the key and fill in its settings below the Stream Deck layout.

Requires macOS 13 or later, Stream Deck 6.9 or later, and a Stream Deck keypad (including the keys on Stream Deck +). Supports Apple silicon and Intel Macs. Windows is not supported.

Settings save as you type or change a control. Wait for Settings saved before closing the settings panel. API tokens use the separate Save token button. If the panel reports a disconnection or an unsaved change, select the action again and check its settings.

2. Key colours and confirmations

Green/mint: successful action, running container or active port.
Red: stopped container, inactive port, offline host or an error. Read the key label and settings message for details.
Orange: Port Killer is being held down.
Yellow animated indicator: an action is working or a build/deployment is in progress.
Blue: normal idle state, cancelled run or no runs yet.

Script Runner, IDE Launcher, Docker Prune and Cache Clearer show Done for two seconds after successful completion, then return to their normal icon with no status text. A Hold 1.2s reminder after a short press also clears after two seconds.

3. Actions

Action	Setup and press behavior
Script Runner	Shell command, optional working folder, timeout; press to run in login zsh. Success/failure reflects the exit code. Optional Terminal log viewer.
Port Killer	TCP port 1–65535; green while listening, red when inactive, orange while held. Hold 1.2 seconds and release to kill its listeners. Status checks every 2 seconds. Short-press hints clear after 2 seconds.
IDE Launcher	Project folder plus VS Code, IntelliJ IDEA, Xcode or Cursor. Done clears after 2 seconds; project-window open/closed state is not tracked.
Container Toggle	Existing Docker container name/ID; press to start/stop, status every 5 seconds.
Docker Prune	Hold 1.2 seconds for `docker system prune -f`. No volume pruning.
Compose Up / Down	Compose project directory; tap for `docker compose up -d`, hold 1.2 seconds for `docker compose down`. Checks configured services every 10 seconds.
GitHub Actions	`owner/repo`, optional branch/workflow, Keychain token name. Newest run, refreshed every 60 seconds; press opens its workflow page.
Vercel Deployment	Project ID/name, optional team ID, API token. Latest deployment every 60 seconds.
Netlify Deployment	Site ID and API token. Latest deploy every 60 seconds.
Cache Clearer	NPM, Yarn, Composer or macOS DNS; hold 1.2 seconds. DNS requests administrator permission.
Hosts Switcher	One exact existing `/etc/hosts` entry, without leading `#`. Hold 1.2 seconds to toggle; administrator approval and backup before each edit.
Ping Monitor	Hostname, IP or HTTP(S) URL; ICMP latency every 5 seconds; press refreshes.
Tunnel Toggle	Cloudflare Quick Tunnel or ngrok, local TCP port. Press starts and copies the URL; press again stops. Leaving the key’s profile or quitting stops the owned tunnel.

4. Tools needed for specific actions

Only install the tools needed for the actions you use:

Docker actions: Docker Desktop or a compatible Docker engine; Compose actions also need Docker Compose v2. Start your Docker engine before using these actions.
IDE Launcher: the selected editor must be installed. The confirmation means the open request succeeded; DevDeck does not track whether the project window remains open.
Script Runner and Cache Clearer: the tools referenced by your commands or chosen cache type must already be installed. Enable Show output in Terminal to inspect script output.
Tunnel Toggle: install Cloudflare's cloudflared or ngrok first. Ngrok needs its account configured. Starting a tunnel makes the selected local service accessible through a public URL.

5. Docker status messages

Start Docker: the Docker engine cannot be reached. Start Docker Desktop or your configured engine and wait for it to finish starting. If it is already running, check your Docker connection/context.
Install Docker: DevDeck cannot find the Docker command-line tool.
No container: check the configured container name or ID.
Stopped: Docker is available, but this container is stopped. Press the key to start it.
Check setup: open the action settings for details, then check paths, permissions and configuration.

6. Premium and Lite

DevDeck includes all 13 actions and unlimited configured script keys.

DevDeck Lite includes IDE Launcher, Port Killer and two shared script slots. Each slot can appear on multiple keys. Editing a slot updates its script across every profile that uses that slot.

To get the full version, select Full version in Lite's settings footer or visit the DevDeck download page.

7. Tokens

In an API action, choose a token name (for example personal or work), paste the token and press Save token. DevDeck stores it in macOS Keychain, grouped by provider and token name. Only its name is stored in action settings. Multiple keys can share a token. Remove token deletes that named credential for every key using it. macOS may ask for Keychain permission. Public GitHub repositories can work without a token; authenticated access improves rate limits. Private GitHub repos need Actions read permission.

8. Help and support

Visit DevDeck Support & Guides for help.

Got an idea or issue? Send us your feedback.

When contacting support, include your macOS version, Stream Deck version, DevDeck edition, action name and the message shown in its settings. Do not include API tokens or command output containing secrets.