Config And Credentials
Gitquarry keeps config and credentials separate on purpose.Config Paths
By default, gitquarry uses the user config directory and stores data under:config.tomlcredentials.tomlfor the explicit insecure fallback path
gitquarry config path returns:
GITQUARRY_CONFIG_DIR
You can override the config root:
Config Schema
Saved config fields:hostformatlimitprogresscolor
format:pretty|json|compact|csvprogress:auto|on|offcolor:auto|always|never
Intentionally Unsaved Defaults
Gitquarry does not persist defaults that would silently enable heavier search behavior. That includes:moderankdepthreadmeexplain- blended weights
- discovery engine knobs
Credential Resolution Order
For a given normalized host, gitquarry resolves credentials in this order:- host-specific env var
- global
GITQUARRY_TOKEN - saved secure credential
- explicit insecure fallback file
Secure Storage
Secure OS storage is the default path. On login, gitquarry verifies that the token can be read back before it reports success.Insecure Fallback
The fallback file is allowed only when:E_AUTH_STORAGE.
On Unix-like systems, gitquarry restricts the config directory to owner-only permissions and does the same for the insecure credential file.
Status And Logout Semantics
auth status reports the effective state for the current host.
If an environment override is active, that is reported separately from saved credential state.
auth logout removes saved credentials for the current host, including the opt-in insecure file.