# Questions & Answers

## Q1: For F1: Which K4000 operations should trigger auto-creation of the config? Options: (a) list_project_tasks only, (b) any task operation (create, analyze, etc.), (c) a dedicated init command
**Category:** other
**Answer:** Any task operation (create, analyze, list_project_tasks, etc.) should trigger auto-creation of the config

## Q2: For F2: Should the generated config.toml include all available settings with their defaults, or only minimal essential settings?
**Category:** other
**Answer:** Yes, include all available settings with their defaults

## Q3: Should K4000 notify the user when it auto-creates the config file (e.g., return a message saying 'Created default config at ...')?
**Category:** other
**Answer:** Yes, notify the user when auto-creating the config file

## Q4: If config.toml exists but is missing new settings added in a K4000 update, should K4000 automatically add the missing settings with defaults, or leave the file unchanged?
**Category:** other
**Answer:** Add missing settings with defaults, but be very careful to not overwrite settings that are already there. Preserve existing user values.
