feat: Add DeepSeek API to modelProviders #1636
Closed
+156
−48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added Support for DeepSeek V3 using `deepseek-chat` for the model, set defaults, included support for the DeepSeek API
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hi @SYMBaiEX! Welcome to the ai16z community. Thanks for submitting your first pull request; your efforts are helping us accelerate towards AGI. We'll review it shortly. You are now a ai16z contributor!
monilpat
requested changes
Jan 1, 2025
monilpat
previously approved these changes
Jan 1, 2025
|
Please run pnpm i -r -no-frozen-lockfile and resubmit please thank you (unrelated change to fix) |
pnpm i -r -no-frozen-lockfile
Done |
monilpat
previously approved these changes
Jan 1, 2025
odilitime
approved these changes
Jan 1, 2025
|
@SYMBaiEX can you resolve the conflicts? |
|
I'll take a look when I get back today, no problem |
|
I really need this , please |
|
Check develop
I think is already there
…On Thu, Jan 9, 2025 at 20:46, mrlonely ***@***.***(mailto:On Thu, Jan 9, 2025 at 20:46, mrlonely <<a href=)> wrote:
I really need this , please
—
Reply to this email directly, [view it on GitHub](#1636 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BE5QO4CNIAPCDPIEFAOJN6L2JZ4U7AVCNFSM6AAAAABUOXONPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBQGIYTMNJSGU).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
closing in favor of #2067 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to:
No Tickets.
Adding DeepSeek as a new ModelProvider for ElizaOS.
Risks
new model added
Background
What’s new in DeepSeek V3?
671B MoE parameters
37B activated parameters
Trained on 14.8T high-quality tokens
What does this PR do?
Adds support for DeepSeek API so ElizaOS can use the DeepSeek V3 model directly.
What kind of change is this?
I personally wanted to try out the DeepSeek V3 model using the DeepSeek API. I see DeepSeek_AI doing a lot of updates and I believe having accessibility long term to their API could be useful.
Documentation changes needed?
Testing
Where should a reviewer start?
Follow the test steps below (should be really easy!)
Detailed testing steps