Skip to content

Build and contribute

Respawn Studios edited this page Nov 15, 2026 · 1 revision

Build and contribute

You don't need a release certificate or a big feature idea to help. A focused fix, clearer guide or accessibility improvement is welcome. You keep your copyright; contributions use GPLv3, with no CLA or per-PR legal statement.

Start from a clean checkout

Follow Development setup for Xcode, Python, the pinned Rust components and public dependency caches. Build outputs and development profiles stay in the checkout's ignored .build/ directory.

python3 -B tools/worker_setup.py --fetch
python3 -B tools/dev.py build
python3 -B tools/dev.py run --skip-build

The setup guide covers cross-building the Intel app on the qualified Apple Silicon/Xcode host. Running the app on Intel and building it on an Intel host are separate compatibility checks. Don't copy another developer's generated app or use release credentials to get a local build running.

Make one useful change

Find the existing module that owns the behavior, keep filesystem work out of UI callbacks, and reuse the normal operation and presentation paths. Add focused validation for the behavior you changed. A documentation fix doesn't need an entire app regression run.

Use the engineering guide for source ownership and validation, and Contributing for the PR workflow. Update the user guide when behavior changes. Public release notes belong in the root changelog as well as the app's release catalog.

Bugs, ideas and security

Issues are for reproducible bugs; Discussions are a good home for questions and ideas. Crash-report drafts remain editable before you publish them. Review paths, server names and screenshots for private information.

Please use private vulnerability reporting for a security issue rather than posting its details in public. Security explains the process.

Clone this wiki locally