Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/techjarves/Odysseus-Portable/llms.txt

Use this file to discover all available pages before exploring further.

Rather than prepending environment variables to every launch command, Odysseus Portable provides a lightweight JSON configuration file that the orchestrator reads at startup and writes to automatically. The file lives at data/launcher_config.json inside the project folder and is created on the very first launch. Because it is just a plain JSON file, you can open it in any text editor and change it between runs — no special tooling required. Environment variables and CLI flags always win over whatever is stored here, so you can still use one-off overrides without touching the file.

​
File Location

Odysseus-Portable/
└── data/
    └── launcher_config.json   ← edit this file to set persistent defaults
The data/ directory is created automatically if it does not exist. If launcher_config.json is missing or cannot be parsed, the orchestrator logs a warning and falls back to its built-in defaults.

​
Supported Fields

​
backend
string
Inference backend to use on every launch. Accepted values: "llama" or "ollama". When this field is present and valid, the backend is used directly without any further prompting.
​
webPort
number
Preferred port for the Odysseus web UI. Equivalent to the ODYSSEUS_PORT environment variable. Default: 7070.
​
proxyPort
number
Preferred port for the API proxy server. Equivalent to ODYSSEUS_PROXY_PORT. Default: 8080.
​
llamaPort
number
Preferred port for the llama-server process (llama.cpp backend only). Equivalent to ODYSSEUS_LLAMA_PORT. Default: 10086.

​
Example File

A fully populated data/launcher_config.json looks like this: 
{
  "backend": "llama",
  "webPort": 7070,
  "proxyPort": 8080,
  "llamaPort": 10086
}
You can omit any field you want to keep at its default. For example, to only pin the backend without touching the ports: 
{
  "backend": "ollama"
}

​
Precedence Order

When the same setting is specified in multiple places, Odysseus Portable resolves it in this order:
1

CLI flags — highest priority

Flags passed directly to the start script (e.g., --backend=llama) override everything else. Use these for one-off overrides without changing any file.
2

Environment variables

Variables set in the shell environment (e.g., ODYSSEUS_BACKEND=llama) take priority over the config file and built-in defaults.
3

data/launcher_config.json

Persistent settings loaded from the JSON file. Ideal for your usual working configuration on a specific machine or USB drive.
4

Built-in defaults — lowest priority

Hard-coded fallback values used when no other source provides a value (llama backend, port 7070 / 8080 / 10086).
When you launch Odysseus Portable for the first time without a data/launcher_config.json, the orchestrator defaults to the llama backend automatically. The selected backend is then written back to data/launcher_config.json, so subsequent launches use the saved value directly.

​
Editing the File Manually

1

Stop Odysseus Portable

Press Ctrl+C in the terminal where Odysseus is running to trigger a graceful shutdown before making changes.
2

Open the file in a text editor

Navigate to the data/ folder inside your project directory and open launcher_config.json with any plain-text editor.
3

Save and restart

Save your changes, then run start.bat (Windows) or ./start.sh (macOS/Linux) as usual. The updated values take effect immediately.
Port conflict detection is still active even when ports are set via the config file. If a configured port is already in use, the orchestrator automatically selects the next available port above it and logs a notice to the console.

Build docs developers (and LLMs) love

Get started for freeTalk to us