Skip to content

Companion Setup Guide

The ReadyTab companion app enables Folder, File, and Command / Script launchers through Chrome native messaging.

Companion launcher support is available for Windows, Linux, and macOS.

Short version

Pick your platform, install the matching companion files, run the platform installer with your ReadyTab extension ID, then restart Chrome / Chromium.

Downloads

Each download contains the platform-specific companion files (host, install, and uninstall scripts). The same files are also available in the ReadyTab repository under launchers/windows/, launchers/linux/, and launchers/macos/.

What the companion app does

  • Open folders in the native file manager
  • Open files with their default application
  • Run commands or scripts from launcher items
  • Show native folder and file picker dialogs

Supported platforms

Windows

  • Uses PowerShell-based companion scripts
  • Opens folders in Windows Explorer
  • Runs command launchers through PowerShell
  • Packaged zip download is available on this page

Linux

  • Uses a python3 native host plus shell scripts
  • Opens folders/files through xdg-open
  • Runs command launchers through your shell
  • Native pickers use zenity or kdialog

macOS

  • Uses a python3 native host plus shell scripts
  • Opens folders/files through open
  • Runs command launchers through your shell
  • Native pickers use built-in osascript dialogs

Requirements

Windows

  • Windows 10 or later
  • PowerShell 5.1 or later
  • Google Chrome or another Chromium browser
  • ReadyTab installed

Linux

  • Linux desktop session
  • python3
  • A POSIX shell such as bash or sh
  • Google Chrome or Chromium
  • zenity or kdialog for native picker dialogs

macOS

  • macOS
  • python3
  • A POSIX shell such as zsh or sh
  • Google Chrome or Chromium

Find your extension ID

The published ReadyTab ID

If you installed ReadyTab from the Chrome Web Store, its extension ID is ccakmoofmcbcplfaloecafdmpaihlenm. The install commands below already use it, so you can copy and run them as-is. You only need to look up the ID yourself if you are running an unpacked / development build (see below).

The extension ID is not your Pro license key

These are two completely different things. The extension ID is a fixed, public identifier for the ReadyTab listing in the Chrome Web Store — it is the same for everyone and is only used to connect the companion app. Your Pro license key is the private code you received when purchasing Pro, used to unlock paid features. Never put your license key into the companion install commands, and never share it.

To find the ID for an unpacked / development build:

  1. Open chrome://extensions in Chrome / Chromium.
  2. Find ReadyTab and copy the extension ID shown on the card.
  3. Use that ID as your development ID when running the installer.
  4. Restart the browser after install so it reloads the native messaging manifest.

Install commands by platform

Windows

The command below already uses the published ReadyTab Web Store ID as the -ProductionId. If you are running an unpacked / development build instead, replace it with your own ID from chrome://extensions.

powershell
powershell.exe -ExecutionPolicy Bypass -File install.ps1 -ProductionId ccakmoofmcbcplfaloecafdmpaihlenm

A Windows security warning is expected

Because the companion files are downloaded from the web, Windows may show an "Open File – Security Warning" or a SmartScreen notice. This is normal for the script-based companion. If SmartScreen appears, select More info, then Run anyway to continue. Only run the ReadyTab companion files you downloaded from this page.

Linux

Open a terminal in launchers/linux/ and run:

bash
chmod +x install.sh host.sh uninstall.sh
./install.sh --production-id ccakmoofmcbcplfaloecafdmpaihlenm

macOS

Open Terminal in launchers/macos/ and run:

bash
chmod +x install.sh host.sh uninstall.sh
./install.sh --production-id ccakmoofmcbcplfaloecafdmpaihlenm

A macOS security prompt is expected

The companion is an unsigned script, so macOS may warn that it is from an unidentified developer, or quarantine the downloaded files. Running ./install.sh from Terminal as shown above is the supported path. If macOS still blocks a file, you can clear the quarantine flag with xattr -d com.apple.quarantine ./install.sh and re-run it. Only run the ReadyTab companion files you downloaded from this page.

Extension ID behavior

  • Published Chrome Web Store ID: fixed and stable for that store listing.
  • Development / unpacked ID: may differ from the published ID and may vary between development setups.

If you want one companion install to work with both, pass both IDs to the installer.

How to use it in ReadyTab

  1. Create or edit a launcher item
  2. Choose Folder, File, or Command / Script
  3. Save the launcher
  4. Click it from your dashboard

You can also check the companion status from Settings → Data inside ReadyTab.

Troubleshooting

Companion shows as not installed

Re-run the installer for your platform, verify the extension ID matches the actual ReadyTab ID, then restart Chrome / Chromium fully.

Windows: "Running scripts is disabled on this system"

Run the installer explicitly with execution policy bypass:

powershell
powershell.exe -ExecutionPolicy Bypass -File install.ps1 -ProductionId ccakmoofmcbcplfaloecafdmpaihlenm

Linux: picker dialog does not appear

Install zenity or kdialog, then retry.

Linux / macOS: command launcher does not run

Make sure the command works in your shell first. If you are launching a script file directly, make sure it has execute permission or invoke it explicitly with bash, sh, or your preferred shell.

Companion still does not connect

  • Verify the extension ID in the install command matches the actual ReadyTab ID
  • Restart Chrome / Chromium fully
  • Re-run the installer from the same companion folder
  • Check ReadyTab's Companion App status in Settings → Data

Uninstall

Windows

powershell
powershell.exe -ExecutionPolicy Bypass -File uninstall.ps1

Linux

bash
./uninstall.sh

macOS

bash
./uninstall.sh

Restart Chrome / Chromium after uninstalling.

Support

Use the support path that matches the kind of issue: