Where Is the OpenLogi Configuration File Located on Windows?

On Windows, OpenLogi stores its configuration in %USERPROFILE%\.config\openlogi\config.toml as a plain TOML file that both the GUI and background agent read on startup.

OpenLogi is a Rust-based logistics automation platform that persists user settings and device keys in a platform-specific configuration directory. The project follows the Windows user-profile convention rather than the registry, making it easy to back up or version-control your settings.

Windows Configuration File Path

The authoritative location for the OpenLogi configuration file on Windows is:

%USERPROFILE%\.config\openlogi\config.toml

In practice, this resolves to a path like C:\Users\YourUsername\.config\openlogi\config.toml. This location is documented in the project's Configuration guide at docs/CONFIGURATION.md lines 5–8.

To locate the file quickly, paste the following into Windows PowerShell:

# Display the expected config path

Join-Path $env:USERPROFILE ".config\openlogi\config.toml"

If the directory does not exist, the OpenLogi GUI or agent will create it automatically on first run.

Cross-Platform Configuration Locations

While the primary keyword targets Windows users, OpenLogi uses the dirs::config_dir() helper from the Rust dirs crate to resolve paths consistently across operating systems:

• Windows: %USERPROFILE%\.config\openlogi\config.toml
• macOS: $HOME/Library/Application Support/openlogi/config.toml (or $XDG_CONFIG_HOME/openlogi/config.toml if set)
• Linux: $XDG_CONFIG_HOME/openlogi/config.toml (defaults to ~/.config/openlogi/config.toml)

How OpenLogi Resolves the Config Path

According to the OpenLogi source code, the configuration path is constructed programmatically in crates/openlogi-core/src/config.rs. The core library uses the standard dirs crate to locate the user's configuration directory, then appends the openlogi subdirectory and config.toml filename:

// openlogi-core/src/config.rs (simplified)
use std::path::PathBuf;
use dirs::config_dir;

/// Returns the full path to OpenLogi’s config file for the current platform.
fn config_path() -> PathBuf {
    let mut base = config_dir().expect("Unable to locate config directory");
    base.push("openlogi");
    base.push("config.toml");
    base
}

Both the GUI and the background agent—whose entry point is crates/openlogi-agent/src/main.rs—call this same function to ensure they read identical settings.

Working with the Configuration File

Creating and Editing the File

Rather than creating the file from scratch, copy the provided template shipped with the repository at docs/config.example.toml. This example contains all valid configuration keys, including commented sections for physical-device mappings that you can uncomment and populate after your first OpenLogi run.

Backup and Atomic Writes

The OpenLogi GUI performs atomic writes to prevent corruption during concurrent access. Before overwriting config.toml, the application:

1. Writes the new content to a temporary file.
2. Renames the existing config.toml to config.toml.backup.1 (cascading previous backups up to config.toml.backup.5).
3. Moves the temporary file to config.toml.

If you edit the file externally while the GUI is running, the next GUI save operation is rejected to prevent overwriting your external changes. This synchronization mechanism ensures the agent and GUI remain consistent.

Summary

• Primary location: %USERPROFILE%\.config\openlogi\config.toml on Windows.
• Format: Plain TOML, editable in any text editor.
• Template: Reference docs/config.example.toml in the repository for valid keys.
• Implementation: Path resolution occurs in crates/openlogi-core/src/config.rs using dirs::config_dir().
• Safety: The GUI maintains up to five rotating backups and uses atomic writes to prevent data loss.

Frequently Asked Questions

Where exactly is the OpenLogi configuration file on Windows 10 and Windows 11?

On both Windows 10 and Windows 11, the file is located at %USERPROFILE%\.config\openlogi\config.toml, which typically expands to C:\Users\<YourUsername>\.config\openlogi\config.toml. This path follows the Windows user-profile convention and does not use the Registry or Program Files directories.

What format does the OpenLogi configuration file use?

OpenLogi uses the TOML (Tom's Obvious, Minimal Language) format for its configuration. The file must be valid UTF-8 and follows the schema defined in docs/config.example.toml. Both boolean values and string keys for physical devices are supported within [device] tables.

How do I reset OpenLogi to default settings?

To reset to defaults, close the OpenLogi GUI and agent, then delete or rename the config.toml file at %USERPROFILE%\.config\openlogi\config.toml. The next time you launch the application, it will generate a fresh configuration file with default values. You may also delete the backup files (config.toml.backup.1 through config.toml.backup.5) if you want to remove all historical settings.

Can I move the OpenLogi configuration file to a different location?

No, the OpenLogi configuration file location is hardcoded relative to the user's configuration directory as returned by dirs::config_dir(). Neither the GUI nor the agent currently supports environment variables or command-line flags to override the config path. If you need to share configurations across machines, consider symbolic links or a dotfiles manager pointing to %USERPROFILE%\.config\openlogi.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}