Table of Contents

Installation 🔗

VS Code extension 🔗

Install the Basamake VS Code extension: download the latest VSIX from the releases page and install it in VS Code (Extensions → ... → Install from VSIX). There is also a snapshot release if you want the latest changes.

If you also have Metals installed, VS Code will prompt you which language server to use for .scala/.sbt files — select Basamake.

BSP setup 🔗

You must install BSP manually — Basamake does not do it for you. There is no "import build" step in Basamake: it only reads .bsp/ configs, it never generates them. Run the setup command of your build tool once per machine, per project.

Basamake speaks the Build Server Protocol: it talks to your build tool through a small config file in a .bsp/ directory. Most build tools can generate it for you:

The generated .bsp/*.json files are usually gitignored (they are machine-specific), so re-run the setup command when you switch machines or clone a project.

Multiple build tools in one workspace 🔗

A workspace may contain several projects, each with its own build tool and .bsp/ directory (e.g. an sbt project in app/ and a scala-cli script in scripts/).

Basamake discovers all .bsp/ directories (up to 10 levels deep) and routes each editor request to the right build server automatically — you don't have to configure anything.

Logs 🔗

All logs go to .basamake/logs/basamake.log in your project root. If something misbehaves, check that file first.