[FEATURE] Document EmpirioLabs in the LLM provider configuration examples
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Start in docs/en/concepts/llms.mdx and read the existing Nebius AI Studio and SambaNova provider configuration accordions. Add a matching EmpirioLabs entry with its environment variable, an LLM(model=...) example, short feature notes, and the LiteLLM dependency note. Done means the English documentation lists EmpirioLabs consistently with the other LiteLLM-backed providers.
Written by the indexing model from the issue text.
Description
Feature Area
Documentation
Is your feature request related to a an existing bug? Please link it here.
NA
Describe the solution you'd like
docs/en/concepts/llms.mdx lists Provider Configuration Examples for the LiteLLM-backed providers, and EmpirioLabs is missing from that list even though it is a registered LiteLLM provider, so LLM(model="empiriolabs/<model>") already routes through the standard LiteLLM fallback path in crewai.llm with no code change.
The ask is one more accordion in that section, matching the existing Nebius AI Studio and SambaNova entries: the env var, an LLM(model=...) example, short feature notes, and the LiteLLM dependency note. English docs only.
Describe alternatives you've considered
Leaving it out and letting users work it out from the generic LiteLLM instructions. That works, but every other provider in the same position has an entry, so the omission just makes a supported provider look unsupported.
- Dominant language
- Python
- Stars
- 58.8k
- Forks
- 8.5k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 103
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from crewAIInc/crewAI
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
[BUG] AttributeError: 'int' object has no attribute 'get' in crew_run_tui.py during plan rendering Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
All issues in crewAIInc/crewAI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100