Use the default profile in gateway when no profile specified #276
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } else if options.WorkingSet == "" { | ||
| // ELSE we're in working set mode, | ||
| // so IF no profile specified, use the default profile | ||
| options.WorkingSet = "default" |
There was a problem hiding this comment.
With the profiles feature enabled, the run handler defaults options.WorkingSet to "default" whenever no legacy flags are set. The legacy detection omits the --session flag, so invoking docker-mcp gateway run --session <name> now falls into this block and forces working-set mode, causing Gateway.NewGateway to ignore the session-specific file-based configuration and load the default profile instead. This regresses session usage whenever the profiles feature flag is enabled and only --session is provided.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Will open a follow up PR for this.
What I did
This fulfills what this other PR promises. When the profiles feature flag is on and no profile is specified, we use the "default" profile.
Related issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did