Examples and your graphs
Boltjar keeps what ships with it apart from what you make.
examples/: shipped, read-only
Section titled “examples/: shipped, read-only”The graphs in examples/ come with Boltjar and show up in your list of graphs. You can open one, turn it On and change it, but saving never writes to the example: it writes your own copy to user/graphs/, and from then on your copy is the one that opens. Delete your copy and the example comes back as it shipped.
examples/ also holds a small node pack, examples/packs/hello, to start your own from. Everything in examples/ is also under MIT No Attribution, so copy from it freely and license the result however you like.
user/: everything you make
Section titled “user/: everything you make”| Folder | What is in it |
|---|---|
user/graphs/ |
your saved graphs, one JSON file each |
user/autosave/ |
a timestamped snapshot on every Save, the newest 50 per graph |
user/data/dbs/ |
the SQLite files of your Database nodes |
user/data/kv/ |
the JSON files of your KV Store nodes |
user/data/vectors/ |
the files of your Vector Store nodes |
user/data/files/ |
the only folder file nodes read and write, and where Image and Audio nodes read local files |
user/data/secrets.json |
the keys and secrets you add in Settings › AI Providers |
user/data/endpoints.json |
the OpenAI-compatible endpoints you add in Settings › AI Providers (their keys stay in the secrets) |
user/data/models-cache.json |
the last model list each provider gave, for starting offline |
user/data/token |
this install’s token, created on the first start |
user/models/ |
your own model manifests (see Models) |
Git ignores all of user/, so an update never touches it, and a back-up of user/ (plus .env, if you use one) is a back-up of everything you made.
Sharing a graph
Section titled “Sharing a graph”A graph is one JSON file in user/graphs/. Put a file there and it appears in your list of graphs; the guides on this site offer theirs as downloads for that. Before you share one, check it holds no keys typed into fields: a key in a {{secret.NAME}} token stays on your machine, and one typed in plain text travels with the file.
Before you run a graph someone else made, read it: a graph is code. See Security.