Skip to main content
Share your project’s Termpad scripts with teammates by adding a termpad.json file to the repository root. Everyone who opens the project in Termpad gets the same setup, run, and cleanup scripts automatically.

Quick Start

Create a termpad.json file in your repository root:
Commit it to your repo. When a teammate opens this project in Termpad for the first time, the scripts are applied automatically.

File Format

Each entry in runScripts has:

How It Works

Opening a project with termpad.json

Termpad never auto-applies the shared config. When a termpad.json is detected, a Sync from termpad.json button appears on the Scripts settings page with a notification badge indicating there are scripts available to apply. Click the button to review and apply the shared scripts.

Syncing updates

When termpad.json changes (e.g., after a git pull), Termpad detects the update and shows the notification badge again on the sync button.
Syncing overwrites all your local script changes with the contents of termpad.json.

Examples

Node.js project

Python project

Monorepo with Docker

Multiline Scripts

Use \n for multiline scripts in JSON:
Each line runs as a separate command in the terminal.

Environment Variables

All Termpad environment variables are available in termpad.json scripts:

Tips

Commit the file

Add termpad.json to version control so the whole team benefits. It’s a small JSON file with no secrets.

Keep secrets out

Don’t put API keys or passwords in termpad.json. Reference .env files instead:

Use with port management

Combine $TERMPAD_PORT with exclusiveMode: false to let multiple worktrees run dev servers simultaneously on different ports.