FM-Agent-Config

Configure FM-Agent in $HOME/.fm-agent-plugin/FM-Agent using its two configuration files:

• fm-agent.toml contains committed, non-secret settings.
• .env contains only the secret LLM_API_KEY.

Configuration precedence is: process environment, .env, fm-agent.toml, then built-in defaults. A legacy non-secret value left in .env overrides the corresponding TOML value.

Prerequisite

Require $HOME/.fm-agent-plugin/FM-Agent/main.py to exist. If it does not, stop and ask the user to run /fm-agent:install.

Configuration workflow

1. Ensure both files exist

Set the installation path and verify the TOML file:

fm_home="$HOME/.fm-agent-plugin/FM-Agent"
test -r "$fm_home/fm-agent.toml" || { echo "fm-agent.toml is missing; reinstall or update FM-Agent"; exit 1; }

If .env is missing, copy the secret-only template without overwriting an existing file:

fm_home="$HOME/.fm-agent-plugin/FM-Agent"
test -e "$fm_home/.env" || cp "$fm_home/.env.example" "$fm_home/.env"

Never source .env or print the API key to the conversation.

2. Show the current configuration

Read fm-agent.toml and present its values grouped by section: llm, runtime, scope, erlang, and codegraph. For .env, report LLM_API_KEY only as configured or missing; treat an empty value or YOUR_LLM_API_KEY as missing.

Check for legacy non-secret entries in .env while revealing names only:

fm_home="$HOME/.fm-agent-plugin/FM-Agent"
awk -F= '/^[[:space:]]*[A-Za-z_][A-Za-z0-9_]*=/{key=$1; gsub(/[[:space:]]/, "", key); if (key != "LLM_API_KEY") print key}' "$fm_home/.env"

If any are present, explain that they override TOML. Ask whether to migrate them. When migrating, preserve their effective values in the corresponding TOML fields, then remove the non-secret lines from .env. Use the environment-variable mappings documented in fm-agent.toml comments or config.py; keep only LLM_API_KEY in .env.

3. Ask what to modify