# Configuration

> Where GUIJam saves your AI tool and model choice, the config.toml format, and the GUIJAM_GJD_BIN, GUIJAM_BROWSER and XDG_CONFIG_HOME variables.

GUIJam has very little to configure. Your AI tool choice is the only setting, and the CLI writes it for you.

## config.toml

`npx guijam init` and `npx guijam provider use` save your choice for your user:

| System                          | Location                              |
| ------------------------------- | ------------------------------------- |
| macOS and Linux                 | `~/.config/guijam/config.toml`        |
| Windows                         | `%APPDATA%\guijam\config.toml`        |
| Any, with `XDG_CONFIG_HOME` set | `$XDG_CONFIG_HOME/guijam/config.toml` |

```toml title="config.toml"
[providers]
active = "opencode"

[providers.opencode]
model = "deepseek/deepseek-chat"

[providers.claude-code]
effort = "high"
```

| Key                     | What it sets                                                                                                                                                                                               |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `providers.active`      | The AI tool: `claude-code`, `codex`, `opencode`, `qwen-code` or `gemini-cli`                                                                                                                               |
| `providers.<id>.model`  | The model to use with that tool, for every request                                                                                                                                                         |
| `providers.<id>.effort` | `low`, `medium` or `high`, for every request. Only Claude Code and Codex use it. Without it, GUIJam uses low for small edits and questions, and medium for sketches, images, links and open-ended changes. |

An unknown tool ID, a blank model or effort, or a file that can't be read counts as not set. GUIJam then uses the first tool that is logged in, and that tool's default models.

The file applies to every project, and GUIJam reads it on every request: a change takes effect on your next request, without restarting your dev server.

There is no per-project config file. Per-project options go in your framework's config, as options to `guijam()`. See the [API reference](https://guijam.francistinao.com/docs/reference/api).

## Environment variables

| Variable          | What it does                                                                                                                                                                                         |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `GUIJAM_GJD_BIN`  | Path to a `gjd` binary to use instead of the one installed from npm                                                                                                                                  |
| `GUIJAM_BROWSER`  | Path to the Chromium-based browser that takes screenshots of links in your prompts. By default GUIJam finds Chrome, Brave, Edge or Chromium. Set it to `off`, `none` or `0` to turn screenshots off. |
| `XDG_CONFIG_HOME` | Moves the saved AI tool choice to `$XDG_CONFIG_HOME/guijam/config.toml`. Without it, the choice is saved in `~/.config/guijam/` on macOS and Linux and in `%APPDATA%\guijam\` on Windows.            |

Set them where you start your dev server, for example:

```bash
GUIJAM_BROWSER=off npm run dev
```

## Project files

GUIJam keeps its run state, logs and undo journal in `.guijam/` in your project. `init` adds that folder to `.gitignore`. See [The .guijam directory](https://guijam.francistinao.com/docs/reference/guijam-directory).
