You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying out one of the AG2 examples, I had a few thoughts around improving the initial developer experience — specifically to reduce the friction in reaching a first successful run.
Current State
The current examples default to using OpenAI (OAI) as the LLM provider (both in README and examples).
However, OAI requires a paid subscription, which might act as a barrier for first-time users.
Observations & Suggestions
Consider alternative defaults: Google’s Gemini provides an AI Studio with a generous free tier, which allows users to get started immediately.
Provider switch mechanism: It may help to provide an easy way for users to switch between providers (e.g., Claude, Gemini, OAI). Even simple code snippets with minimal copy-paste/setup friction could go a long way.
Example config I used to get Gemini working with AG2 for the first:
seed=42# for caching, use None for no cachingllm_config=LLMConfig.from_json(
path="OAI_CONFIG_LIST",
seed=seed,
).where(model="gemini-2.0-flash-001")
This took me a 5-7 minutes of trial and error as a first-time user. Ideally - the quick start should be specific enough that there is no possibility of friction in getting it to work.
Documentation/UI enhancement Possibilities:
A step-by-step guide for Gemini (and possibly Claude) would help:
Go to Google AI Studio (or Claude settings)
Get API key
Create config file
Select exact LLM config
Run example
A tabbed UI for examples (OAI | Gemini | Claude) might reduce onboarding friction significantly.
Rationale:
Reaching a "first success" quickly is key to adoption.
Many developers (esp. personal users or non-enterprise) are increasingly diversifying away from OAI.
Anecdotally, in my circles, people use Claude or Gemini more for personal use.
Diversity in provider preference should be acknowledged in examples/documentation.
Thanks again for considering this. Happy to iterate or help out further!
Steps to reproduce
No response
Screenshots and logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Describe the issue
While trying out one of the AG2 examples, I had a few thoughts around improving the initial developer experience — specifically to reduce the friction in reaching a first successful run.
Current State
Observations & Suggestions
Example config I used to get Gemini working with AG2 for the first:
And the corresponding setup in code:
This took me a 5-7 minutes of trial and error as a first-time user. Ideally - the quick start should be specific enough that there is no possibility of friction in getting it to work.
Documentation/UI enhancement Possibilities:
Rationale:
Thanks again for considering this. Happy to iterate or help out further!
Steps to reproduce
No response
Screenshots and logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: