A conform map (as configuration) used for model names when exporting from autogroq about autogroq HOT 9 CLOSED

Correct on all counts. Groq's paid service will not suffer from this limitation.

In the meantime, you can click any gear icon and change the default model for all agents at once to a non-Groq option...

-jjg

from autogroq.

Achieved (almost) what I wanted;

1. Using the fireworks api in autogroq. Changed the file: AutoGroq/AutoGroq/config.py
   [attached here as: config-py.txt]
   config-py.txt

and added the provider file: AutoGroq/AutoGroq/llm_providers/fireworks_provider.py
[attached here as: fireworks_provider-py.txt]
fireworks_provider-py.txt

2. Tested that the two above files make fireworks-api to work in AutoGroq. OK, so the test prompt was simple: "Why do dogs bark at cats?" but it still/anyway verifies the basic functionality.

3. Exported to Autogen. Yes, it did do it.

4. In autogen; PROBLEMS

Running (in Autogen Playground) the [AutoGroq Workflow] which AutoGroQ exported to Autogen, will produce error.

Reason is following:

• In AutoGroq to run correctly the base url must be: https://api.fireworks.ai/inference/v1/chat/completions

• In Autogen to run correctly the base url must be: https://api.fireworks.ai/inference/v1

The official (and thus correct way) by fireworks.ai is: https://api.fireworks.ai/inference/v1/chat/completions

In conclusion: TODO

A. I will open a bug/error in/for autogen staff to handle.

B. I will use the specific config_local.py described in https://youtu.be/MGEXFuK7RDY (at 1:43+) to fix my (local) config to be resilient regardless AutoGroq updates.

C. Mr J.Gravelle will include the file "fireworks_provider.py" into AutoGroq build.

from autogroq.

Make sure you share this on Discord, please... -jjg

https://discord.gg/DXjFPX84gs

from autogroq.

I mean, you can do openrouter.ai as well:
https://openrouter.ai/docs/models

This sort of change should be in the new local config, not in config.py. (making config.py use more custom options like new providers or tweaking existing ones makes sense )

from autogroq.

Achieved (almost) what I wanted;

1. Using the fireworks api in autogroq. Changed the file: AutoGroq/AutoGroq/config.py
   [attached here as: config-py.txt]
   config-py.txt

and added the provider file: AutoGroq/AutoGroq/llm_providers/fireworks_provider.py [attached here as: fireworks_provider-py.txt] fireworks_provider-py.txt

2. Tested that the two above files make fireworks-api to work in AutoGroq. OK, so the test prompt was simple: "Why do dogs bark at cats?" but it still/anyway verifies the basic functionality.
3. Exported to Autogen. Yes, it did do it.
4. In autogen; PROBLEMS

Running (in Autogen Playground) the [AutoGroq Workflow] which AutoGroQ exported to Autogen, will produce error.

Reason is following:

• In AutoGroq to run correctly the base url must be: https://api.fireworks.ai/inference/v1/chat/completions
• In Autogen to run correctly the base url must be: https://api.fireworks.ai/inference/v1

The official (and thus correct way) by fireworks.ai is: https://api.fireworks.ai/inference/v1/chat/completions

In conclusion: TODO

A. I will open a bug/error in/for autogen staff to handle.

B. I will use the specific config_local.py described in https://youtu.be/MGEXFuK7RDY (at 1:43+) to fix my (local) config to be resilient regardless AutoGroq updates.

C. Mr J.Gravelle will include the file "fireworks_provider.py" into AutoGroq build.

As regarding the: TODO A. I created the following bug-report to autogen studio;

[Bug]: Autogen Studio App does not use the given baseurl #2903
microsoft/autogen#2903

from autogroq.

I thought I did 'C.' already...

from autogroq.

I thought I did 'C.' already...

Yes, you did. So TODO of C is done.

I will recheck the TODO of A with the newest Autogen Studio. (=0.0.56rc12 of May30th) [How to get it? See: https://github.com//issues/37]

The TODO of B is of course specific to each user of AutoGroq. I will let you know what I use once I have figured it out myself.

from autogroq.

As to: TODO of A.

I updated the autogen-bug-item. BUG still remains.

I have a growing suspicion that autogen will continue making life difficult for everyone else and will (continue) to choose to pick OpenAI-type api-inferences base-urls only if they are given as ending by: "v1"

This means that AutoGroq might need to change any OpenAI-type [NOTE: the TYPE ones and not just actual OpenAI-ones] base-urls to end to "v1" when exporting to autogen. Either that or wait [during the wait having functionality breaking exports] the 2-months release-cycle when MAYBE the autogen has/will? fix this.

from autogroq.

Agreed. We should wait for both Autogen to finish their re-write and AutoGroq to finish ours...

from autogroq.