Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: A page in extension to show the recommended ways to integrate with non-openai models #5118

Closed
ekzhu opened this issue Jan 20, 2025 · 0 comments · Fixed by #5196
Closed
Labels
documentation Improvements or additions to documentation needs-triage proj-extensions
Milestone

Comments

@ekzhu
Copy link
Collaborator

ekzhu commented Jan 20, 2025

We need a documentation page in the Extensions to show the recommended ways to integrate with non-OpenAI models:

Reference: semantic kernel connectors: https://github.com/microsoft/semantic-kernel/tree/main/python/semantic_kernel/connectors/ai

Also, update the tutorial documentation in both AgentChat and Core to point to this page for non-OpenAI models and local models.

@ekzhu ekzhu added documentation Improvements or additions to documentation proj-extensions labels Jan 20, 2025
@ekzhu ekzhu added this to the 0.4.x milestone Jan 20, 2025
@ekzhu ekzhu changed the title A page in extension to show the recommended ways to integrate with non-openai models doc: A page in extension to show the recommended ways to integrate with non-openai models Jan 20, 2025
@ekzhu ekzhu closed this as completed in e582072 Jan 26, 2025
MohMaz pushed a commit to MohMaz/autogen that referenced this issue Jan 29, 2025
…microsoft#5196)

Partially resolves: microsoft#5118

Once the extension page is ready, update the tutorial pages to reduce
duplication.

---------

Co-authored-by: Victor Dibia <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation needs-triage proj-extensions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant