ScriptDeck GitHub
Open sourceFree under the MIT License

Run your package.json scripts from the menu bar.

Dev servers, watchers and one-off tasks keep running in the background, each in its own real terminal. Works with pnpm, yarn, npm and bun, workspaces included, and gives every project the right Node version.

Latest release · Apple silicon and Intel · Also for Windows

brew install --cask svichas/tap/scriptdeck
The ScriptDeck menu bar window: the same dev server running in two worktrees, an API server and a failed build, then a project's branch, group and pinned scripts

Features

Everything you keep a terminal tab open for

Add your projects once. ScriptDeck finds every script, workspace packages included, runs them in the background and tells you when one falls over.

Every script, one click away

Root scripts, every workspace package's scripts and your own commands, for pnpm, yarn, npm and bun.

Leave them running

Each script gets its own real terminal. Open it from the menu bar, type into it, restart or stop it. Quitting ScriptDeck stops everything it started.

Reopen after a restart

Turn on Reopen running scripts, and the scripts still running when you quit, log out or update start again with ScriptDeck. Ones you stopped stay stopped.

Find in the output

Cmd+F (Ctrl+F on Windows) searches a terminal's whole scrollback. Cmd+click (Ctrl+click) opens any web link a script prints.

CPU and memory

Hover a script's terminal tab to see what all its processes use together, like 1.2 GB · 42%. CPU is a share of the whole Mac, so 100% means every core is busy. Past 500 MB or 10% CPU, its row in the menu bar window shows it too. macOS only.

AI agents (MCP)

Turn it on in Settings, and Claude Code or another agent can see your scripts, read and search their output, and start, restart or stop them. Agents never type into a terminal. Not on Windows yet.

Branches and worktrees

Each project in a git repository shows its branch, uncommitted changes and what's left to pull. Check out or make a branch, pull, or switch to another worktree: its scripts run there while the others keep running, so the same dev can run on two branches at once.

Search across all projects

Click the icon or press your shortcut, type a few letters, press Enter.

Run with arguments

Option-click a script's Run button (Alt-click on Windows), or press Shift+Enter on a search result, then type --watch. ScriptDeck adds the -- npm needs and remembers the arguments for next time.

Pin what you use

Pinned scripts stay at the top, and the menu bar icon shows how many are running.

Groups

Start the scripts you always run together, say web, api and a worker, with one click, and stop them the same way. Each still gets its own terminal.

Dev server links

The port a script prints becomes a one-click link to it.

Port already in use

When a script can't start because its port is taken, its row names what holds it, another script or a leftover process, and Free port stops that and restarts yours. macOS only.

Node per project

Follows .nvmrc, .node-version or a Volta pin, or pick any version from nvm, fnm or Volta. Missing versions get an install button.

Edit package.json scripts

Add, change, rename or delete scripts for the root or any workspace package. Key order, indentation and line endings stay as they were.

Crash notifications

A notification when a script fails on its own. Stopping it yourself doesn't count, and neither does a failure you're watching.

Test results

A notification when tests pass or fail, however quick: any script with test, e2e, vitest or jest in its name or command.

Restart on crash

Switch it on per script, and a script that dies on its own comes back after 1, 2, 4, 8 and 16 seconds. If all five restarts crash within a minute, it stays down.

Durations

Each script shows how long it has been running, or how long it took. Anything that takes 30 seconds or more posts a notification when it finishes.

Toolkit

Install, outdated, update, audit and clean reinstall, with the project's own package manager.

The Settings window: a project's branch, custom scripts, group and package.json scripts
Settings: each project's branch and worktrees, Node version, toolkit, custom scripts, groups and package.json scripts.

Install

Download ScriptDeck

Every release is built from its tag by the Release workflow on GitHub Actions and published on GitHub Releases with its release notes. From 0.2.0 on, ScriptDeck updates itself: a banner in the menu bar window offers each new release, and the app restarts into it when you click Restart Now.

macOS

Universal app for Apple silicon and Intel

Download .dmg
  1. Open the disk image and drag ScriptDeck to Applications.
  2. Open ScriptDeck. It's ad-hoc signed, not notarized, so macOS blocks the first launch.
  3. In System Settings › Privacy & Security, click Open Anyway. ScriptDeck appears in the menu bar.

Or install it with Homebrew, then do step 3 on the first launch:

brew install --cask svichas/tap/scriptdeck

Windows

Installer for 64-bit Windows

Download .exe
  1. Run the installer.
  2. It isn't signed, so SmartScreen may warn about it: click More info, then Run anyway.
  3. ScriptDeck is developed on macOS. If anything behaves differently on Windows, please report it.

All releases and release notes · Build from source

Docs

How to use ScriptDeck

Getting started

  1. Install ScriptDeck and open it. It lives in the menu bar (the notification area on Windows) and shows in the Dock only while Settings or a terminal window is open.
  2. Click the icon, then Add a project. In Settings, click + and choose a folder with a package.json, or drop folders on the window.
  3. Click the menu bar icon again and press the play button next to a script. Click a running script to open its terminal.

Turn on Launch at login in Settings › Preferences so your scripts are a click away after a restart.

Running scripts

Every script runs in its own terminal through your login shell, so it gets the same PATH as your terminal app, and colours, prompts and interactive tools work as usual.

  • Running and failed scripts are listed at the top of the menu bar window, each with how long it has run. Restart or stop one there, or click Stop all.
  • Click a running script to open its terminal window: watch the output, scroll back or type into it. Cmd+F (Ctrl+F on Windows) finds text in its whole scrollback, and Cmd+click (Ctrl+click) opens a web link it printed.
  • Hover a terminal tab to see the CPU and memory all of its script's processes use, with CPU as a share of the whole Mac. A script past 500 MB or 10% CPU shows it in the menu bar window too. macOS only.
  • When a script prints a local address, its port appears as a link, such as :5173, that opens it in your browser.
  • If a script can't start because its port is taken, its row names what holds the port, another script or a leftover process. Free port stops that and restarts yours. macOS only.
  • To add arguments such as --watch, Option-click a script's Run button (Alt-click on Windows). ScriptDeck adds the -- npm needs and remembers them for next time.
  • Stopping a script escalates from Ctrl-C to SIGTERM to SIGKILL on its whole process tree, so no stray child keeps a port busy.
  • Quitting ScriptDeck stops every script it started. With Reopen running scripts on in Settings › Preferences, the ones still running start again the next time ScriptDeck opens, after an update too.
  • The menu bar icon shows how many scripts are running. Right-click it for Open ScriptDeck, Settings…, Stop All Scripts and Quit ScriptDeck.

Restart on crash

Click the pulse icon on a script's row in its project's settings (Restart if it crashes). It stays lit while it's on. When the script dies on its own, it comes back after 1 second, then 2, 4, 8 and 16. If all five restarts crash within a minute of starting, it stays down. Stopping it yourself never restarts it.

Notifications

With Notify when a script fails on in Settings › Preferences, you get a system notification when a script exits with an error on its own. Stopping a script yourself doesn't count, and neither does a failure you're watching in its terminal. A script that restarts on crash notifies once as it starts restarting, and again if it gives up.

Notify when a long script finishes tells you when one that ran for 30 seconds or more, such as an install or a build, is done.

Notify when tests pass or fail covers any script with test, tests, e2e, vitest, jest, mocha or cypress in its name or command, however quick it was. Test runners in watch mode never exit, so they don't notify.

If macOS is blocking ScriptDeck's notifications, Settings › Preferences shows an Allow button above the switches. macOS asks only once, so after a Don't Allow the button opens System Settings instead.

Package managers and workspaces

ScriptDeck reads the packageManager field in package.json, or else looks for a lockfile: pnpm-lock.yaml, yarn.lock, bun.lock or bun.lockb, or package-lock.json. It checks parent folders too, so a package added on its own still uses its monorepo's package manager. With neither, it uses npm.

Workspace packages come from pnpm-workspace.yaml or the workspaces field, and their scripts run with the package manager's own filter:

Package managerRuns a workspace script as
pnpmpnpm -F @acme/app run start
yarnyarn workspace @acme/app run start
npmnpm run start -w @acme/app
bunbun run --filter @acme/app start

Custom scripts

For commands that aren't in any package.json, like one package's Storybook or a database container, add a name and a command under Custom scripts in the project's settings. Custom scripts always show in the menu bar window.

Branches and worktrees

A project in a git repository shows its branch beside its name, with a dot for uncommitted changes and ↓2 when there's something to pull. Click it to open the switcher:

  • Pick a branch to check it out. Type a name that isn't one yet to make it here, or to make a new worktree for it.
  • Switch the project to another worktree of the repository. Its scripts then run in that folder, and what's already running keeps running, so the same dev can run on two branches at once, each in its own terminal named after its branch.
  • Pull fast-forwards the branch. Git never waits on a password prompt: it uses your credential helper or SSH agent, or says why it can't.
  • A new worktree or a fresh clone with no node_modules shows its install command, like pnpm install.

Manage worktrees… at the foot of the switcher opens the project's settings at its worktrees, each with what's running in it, Use and Remove, and a form for a new one from a new or existing branch. New worktrees go beside the repository, so app and feature/x make app-feature-x. A worktree is never removed while it has uncommitted or untracked files, another worktree inside it, or scripts running in it.

To clone a repository, click the button beside + in Settings, then give a URL or owner/repo and a folder. The clone opens as a project. Committing and pushing stay in your terminal or editor.

Node versions

Each project runs with its own Node version. By default ScriptDeck follows the project's .nvmrc, .node-version or Volta pin, looking in parent folders too.

  • To use a different one, pick any version installed with nvm, fnm or Volta under Node version in the project's settings.
  • If the version a project wants isn't installed, an Install button runs your version manager's install command.
  • The project's Node is set after your shell's rc files run, so it wins over your version manager's default.
  • Settings shows the engines range from package.json beside the version your scripts will use.
  • Without nvm, fnm or Volta, scripts use whatever node your shell finds.

Editing package.json scripts

A project's settings list the scripts of its root package.json and of every workspace package, with a filter to find one fast.

  • Add a script with +, change its name or command with the pencil, or delete it with ×. A renamed script keeps its pin.
  • ScriptDeck changes only the entry you edit. Key order, indentation and line endings stay as they were, so your diffs stay small.

AI agents (MCP)

ScriptDeck has an MCP server, so Claude Code or another AI agent can list your scripts, read and search their output, and start, restart or stop them. It's off by default, and not on Windows yet.

  1. Turn on Let AI agents read and restart scripts (MCP) in Settings › Preferences.
  2. Click Copy beside Add to Claude Code and run the command in your terminal. Another agent needs a stdio server that runs the same app path with --mcp.

Agents never type into a terminal. They reach ScriptDeck through a socket only your user can open, only while the switch is on, and no network port is opened. An agent can read everything your scripts print, so leave the switch off if that includes secrets.

Settings

Open Settings from the gear in the menu bar window, or right-click the menu bar icon.

  • Projects. Add folders with + or by dropping them on the window, or clone a repository with the button beside +. Rename a project by editing its name, or remove it from ScriptDeck; your files aren't touched.
  • Groups. Under Groups in a project's settings, click +, name the group and pick its scripts from Add script. The group gets a row in the menu bar window that starts or stops them all, and you can run it from Settings too.
  • Toolkit. Install, Outdated, Update, Audit and Clean reinstall run with the project's package manager, each in its own terminal like a script. Clean reinstall deletes node_modules first, so it asks before it runs.
  • Preferences. Launch at login, reopening running scripts, the global shortcut, failure, test and long-script notifications, a system, light or dark theme, the terminal font size, AI agent access, and Check for Updates. While macOS blocks ScriptDeck's notifications, an Allow button sits above their switches.

How it works

ScriptDeck is a Tauri 2 app: Rust for the processes, plain HTML and JS for the windows.

  • src-tauri/src/sessions.rs owns the PTYs: scrollback, stop escalation and URL detection.
  • src-tauri/src/project.rs reads and edits package.json and finds workspaces. node.rs resolves Node versions across nvm, fnm and Volta.
  • ui/ has no framework and no build step. The terminal is xterm.js, vendored in ui/vendor/.
  • src-tauri/src/update.rs updates the app from the latest GitHub release with the Tauri updater.
  • src-tauri/src/git/ runs the git command line, never through a shell, with your login shell's PATH and the project's Node, so hooks such as husky's work as in a terminal. Pulls are fast-forward only.
  • src-tauri/src/permission.rs asks macOS whether ScriptDeck may post notifications.
  • src-tauri/src/mcp.rs is the MCP server for AI agents. ScriptDeck --mcp, which an agent launches, pipes its stdio to a Unix socket the app opens in its config folder while the switch is on.
  • Projects and settings live in config.json in the app's config folder: ~/Library/Application Support/com.scriptdec.desktop/ on macOS, %APPDATA%\com.scriptdec.desktop\ on Windows. The bundle identifier keeps the app's old name, ScriptDec: changing it would move this folder, and installed apps would lose their projects and settings.

No telemetry. ScriptDeck has no account and no analytics. On its own it only fetches the latest release's latest.json from GitHub, at most every six hours, and it installs only updates signed with the release key. It only opens localhost links found in script output.

Build from source

You need Rust, Node.js with pnpm, and the Tauri prerequisites for your OS.

git clone https://github.com/svichas/ScriptDeck.git
cd ScriptDeck
pnpm install
pnpm devRuns the app with your changes. Reload a window from its right-click menu to pick up UI changes; Rust changes rebuild and restart the app.
pnpm testRuns the Rust tests.
pnpm buildBuilds ScriptDeck.app (an NSIS installer on Windows) into src-tauri/target/release/bundle/.
pnpm dmgBuilds the app and a disk image, macOS only. It skips the Finder step that arranges the icons, the usual reason DMG builds fail.

Troubleshooting

macOS says ScriptDeck can't be opened

The app is ad-hoc signed, not notarized by Apple, so macOS blocks the first launch. Open it once, then click Open Anyway in System Settings › Privacy & Security.

I installed it with Homebrew: how do I update or remove it?

ScriptDeck updates itself, so brew upgrade leaves it alone. To remove it, run brew uninstall --cask scriptdeck. Add --zap to delete its settings and caches too.

Windows SmartScreen warns about the installer

The installer isn't signed. Click More info, then Run anyway.

A script works in my terminal but not in ScriptDeck

Scripts run through your login shell, so they get the same PATH. Check which Node version the project uses in its settings: a project's .nvmrc wins over your default. If it still fails, open a bug report with the script's command and package manager.

My global shortcut doesn't work

It needs Ctrl, Option or Cmd. If another app already uses the combination, ScriptDeck says it can't use it: record a different one.

I don't get notifications

Open Settings › Preferences. While macOS blocks ScriptDeck's notifications, an Allow button sits above the switches. After an earlier Don't Allow, it opens System Settings › Notifications, where you can switch ScriptDeck back on. Nothing is posted while ScriptDeck's terminal window is in front, since you're already watching.

Open source

Built in the open

ScriptDeck is free software under the MIT License. Read the code, report a bug or send a pull request: issues and pull requests are both welcome.

Guidelines

  • One fix or feature per pull request, as small as it can be.
  • No frontend framework or bundler. Build DOM with h() from ui/shared.js, never innerHTML with data: names come from other people's package.json files.
  • Anything from a repo that reaches a shell is quoted with sh_quote.
  • Colours come from the tokens at the top of ui/app.css. Check light and dark.
  • New logic in src-tauri/src gets a test beside it.

Before you open a pull request

pnpm test
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings

CI runs both on macOS for every pull request. To release, bump the version in package.json, src-tauri/Cargo.toml and src-tauri/tauri.conf.json, then push a tag such as v0.2.0. Publishing the draft release ships the update; CONTRIBUTING.md has the checks to do first.