API keys from environment variables with trailing whitespace cause cryptic "expected a cloneable request" error

[alpo]

When an API key environment variable contains trailing whitespace (commonly a newline character), aichat fails with a confusing error message that doesn't indicate the actual problem.

Error with streaming (default):

Error: Failed to call chat-completions api

 Caused by:
     expected a cloneable request

Error with stream: false:

 Error: Failed to call chat-completions api

 Caused by:
     0: builder error
     1: failed to parse header value

Root Cause

HTTP header values cannot contain newline characters. When an API key with a trailing newline is used in the Authorization: Bearer {key} header, reqwest's RequestBuilder enters an error state. In the streaming code path, reqwest-eventsource calls builder.try_clone() which returns None for error-state builders, resulting in the misleading "expected a cloneable request" error.

How to Reproduce

1. Set an API key environment variable with a trailing newline:
   export XAI_API_KEY="xai-your-key-here
   "

2. Configure the provider in config.yaml: clients:

   • type: openai-compatible
     name: xai
     api_base: https://api.x.ai/v1

3. Run aichat:
   aichat -m xai:grok-2-latest "hello"

4. Observe the cryptic error message

Expected Behavior

Either:

1. Automatically trim whitespace from environment variable values, or
2. Provide a clear error message indicating the API key contains invalid characters

[0m364]

Fix applied in src/client/macros.rs:
This trims leading/trailing whitespace (including newlines) from API keys read from both environment variables and config files, fixing the "failed to parse header value" and "expected a cloneable request" errors.

std::env::var(&env_name)
.map(|v| v.trim().to_string()) // Trim whitespace from env var
.ok()
.or_else(|| self.config.$field_name.clone().map(|v| v.trim().to_string()))
.ok_or_else(|| anyhow::anyhow!("Miss '{}'", stringify!($field_name)))