Config model for workspace

[letanloc1998]

Hi everyone,

1. How can I configure Continue.dev for a specific workspace instead of using the global ~/.continue/config.yaml on macOS/Linux or %USERPROFILE%.continue\config.yaml on Windows?

2. What is the difference between these two approaches, and how can I properly configure the API key (environment variable or input on UI)?

apiKey: ${{ secrets.OPENAI_API_KEY }}
apiKey: ${{ inputs.OPENAI_API_KEY }}

3. Does continue.dev support falling back to a different model if one model fails?

[bdougie]

Hi @letanloc1998 I open a PR to update the docs around this. #8166

For most use cases, use ${{ secrets.SECRET_NAME }} directly in your configuration. This is the recommended approach for both personal and organizational workflows.

[letanloc1998]

Thank you