> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bach builds Windows installers from one bach.toml with the bach command: bach init, bach check, bach preview, bach build. Installs are per user and need no administrator rights by default. installer.scope = "machine" installs for every user after one Windows prompt. On Windows, run setup files with Start-Process -Wait -PassThru in PowerShell, and give signtool arguments that start with the word sign.

# Editor support: the bach.toml JSON schema

> Get completion and typo checking for bach.toml in VS Code, Zed and JetBrains with the published JSON schema that bach init adds to every new config.

Bach publishes a JSON schema for `bach.toml`, so your editor can complete every setting and flag typos as you type. `bach init` adds the schema line to every file it writes.

```toml bach.toml theme={"theme":{"light":"github-light","dark":"github-dark"}}
#:schema https://raw.githubusercontent.com/usebach/bach/main/schema/bach.schema.json
```

## Supported editors

| Editor | Needs |
| - | - |
| VS Code | The Even Better TOML extension |
| Zed | Built-in TOML support |
| JetBrains IDEs | The Taplo support |

Any editor with TOML support that reads `#:schema` comments works.

## What you get

* Completion for every section and setting, including the four values of options.
* Warnings on unknown settings and wrong types.
* Hover descriptions where your editor shows them.

## The schema stays complete

The schema lives at `schema/bach.schema.json` in the repository, and a test keeps it complete: adding a setting to Bach without adding it to the schema fails the build.

> [!TIP]
>
> The schema is for editors. `bach check` is the authority: it also checks that files exist, that patterns match and that paths are safe.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.