wehub-resource-sync
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
# Environment variables
|
|
|
|
This page details all environment variables that are currently in use by SWE-agent.
|
|
|
|
* All API keys (for LMs and GitHub) can be set as an environment variable. See [here](../installation/keys.md) for more information.
|
|
* `SWE_AGENT_CONFIG_ROOT`: Used to resolve relative paths in the [config](config.md). E.g., if `SWE_AGENT_CONFIG_ROOT=/a/b/c` and you set
|
|
add a tool bundle as `tools/my_bundle`, it will be resolved to `/a/b/c/tools/my_bundle`. The default of `SWE_AGENT_CONFIG_ROOT` is the
|
|
the `swe-agent` package directory.
|
|
|
|
The following variables can only be set as environment variables, not in the config file.
|
|
|
|
If you install `swe-agent` without the `--editable` option, please make sure to set
|
|
|
|
* `SWE_AGENT_CONFIG_DIR` (default `<PACKAGE>/config`)
|
|
* `SWE_AGENT_TOOLS_DIR` (default `<PACKAGE>/tools`)
|
|
* `SWE_AGENT_TRAJECTORY_DIR` (default `<PACKAGE>/trajectories`)
|
|
|
|
In addition, the following env variables allow to configure the logging.
|
|
|
|
* `SWE_AGENT_LOG_TIME`: Add timestamps to log
|
|
* `SWE_AGENT_LOG_STREAM_LEVEL`: Level of logging that is shown on the command line interface (`TRACE` being a custom level below `DEBUG`). Will have no effect for `run-batch`.
|
|
|
|
!!! hint "Persisting environment variables"
|
|
Most environment variables can also be added to `.env` instead. |