Configuration¶
Most common configuration options you need is in the Settings page of the web UI.
Other, more technical configuration options, are available through the config files. These are located in different places depending on your platform, see the directories documentation for where to find them.
Note
In v0.11.0, the previous .ini config files used by all Python-based modules were replaced by .toml files (commented out by default, to allow for updates to the defaults). If you had made any modifications to the ini files prior to v0.11, you need to migrate them to the new files.
Configuration options for the server, client, and default watchers are listed below:
aw-server-python¶
hostHostname to start the server on. Currently onlylocalhostor127.0.0.1are supported.portPort number to start the server on.storageType of storage for holding buckets and events. Supported types arepeewee,memory(useful in testing), ormongodb(MongoDB support will be removed in a future version).cors_originsComma-separated list of allowed origins for CORS (Cross-Origin Resource Sharing). Useful in testing and development to let other origins access the ActivityWatch API, such as aw-webui in development mode on port 27180.
aw-server-rust¶
hostHostname to start the server on. Currently onlylocalhostor127.0.0.1are supported.portPort number to start the server on.corsList of allowed origins for CORS (Cross-Origin Resource Sharing). Useful in testing and development to let other origins access the ActivityWatch API, such as aw-webui in development mode on port 27180.
aw-client¶
server.hostnameHostname of the server to connect to.server.portPort number of the server to connect to.client.commit_intervalHow often to commit events to the server (in seconds).
aw-watcher-afk¶
timeoutTime in seconds after which a period without keyboard or mouse activity is considered to be AFK (away from keyboard).poll_timeTime in seconds between checks for activity.
See aw_watcher_afk/config.py for the default config values.
aw-watcher-window¶
poll_timeTime in seconds between window checks.exclude_titleDon’t track window titlesstrategy_macosThe strategy to use on macOS to fetch the active window, can be “swift”, “jxa” or “applescript”. Swift strategy is preferred.