Library and configuration

Know what belongs to a project and what is shared across your projects.

2 min readReference

Flux’s reference system has two layers, and the split is what lets a permanent reading library coexist with fully self-contained projects:

The point of the split: your library can grow to thousands of papers without bloating any project, and a project still zips, clones, and compiles standalone — hand the folder to a collaborator and every citation resolves, no FluxLib required.

The citekey is the join key: the same smithNeuralBasis2021 names the paper in FluxLib, in every project that cites it, and in your manuscript.

The citekey is the join key

Every paper has one stable citation key (smithNeuralBasis2021-style — the same format Zotero’s Better BibTeX plugin uses, so keys arriving from a Zotero sync and keys Flux mints itself look alike). That key is how you cite it in any manuscript ([@smithNeuralBasis2021]), the name of its folder in the library, and the handle agents use to fetch, highlight, or discuss it. Keys are permanent join keys — they never change out from under a project.

What’s inside FluxLib

FluxLib lives at <FluxConfig>/FluxLib (by default ~/FluxConfig/FluxLib; flux config prints this machine’s paths). Like projects, it’s plain files with a clear source-vs-derived split:

Portability

Because it’s all files, moving machines is copying a folder: ~/FluxConfig carries your library (FluxLib/), your agent context and skills (Context/UserContext/, including Skills/), and your global plot library (plot_library/). Back it up like you’d back up your documents — it is documents.

Search the docs

Search guides, workspaces, and reference topics.

↑ ↓ to move · Enter to open · Esc to close