fix: DeepSeek API bug: missing api key setting

[daizhengxue]

Fix DeepSeek API Key Support

Relates to

Fix DeepSeek API integration

Risks

Low - Adding missing API key handling for existing DeepSeek provider

Background

What does this PR do?

Adds missing DeepSeek API key handling in getTokenForProvider function to properly support DeepSeek model provider.

What kind of change is this?

Bug fixes (non-breaking change which fixes an issue)

Documentation changes needed?

My changes do not require a change to the project documentation.

Testing

Where should a reviewer start?

Check agent/src/index.ts for the added DeepSeek case in getTokenForProvider

Detailed testing steps

1. Set DeepSeek API key in settings
2. Create character with modelProvider: "deepseek"
3. Verify the API key is properly retrieved

Code Changes

add

case ModelProviderName.DEEPSEEK:
return (
character.settings?.secrets?.DEEPSEEK_API_KEY ||
settings.DEEPSEEK_API_KEY
);

Discord name:masterdai

[daizhengxue]

thx

[tcm390]

Hello @daizhengxue could you resolve the conflict?

[wtfsayo]

@coderabbitai review

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces configuration support for the DeepSeek API by adding a new API key entry in the .env.example file and extending the getTokenForProvider function in agent/src/index.ts to handle the DeepSeek model provider. This change enables users to integrate DeepSeek's API services by specifying their authentication credentials.

Changes

File	Change Summary
.env.example	Added DEEPSEEK_API_KEY= configuration entry for DeepSeek API authentication
agent/src/index.ts	Extended getTokenForProvider function to support ModelProviderName.DEEPSEEK provider, enabling token retrieval for DeepSeek API

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5973e52 and 41cfed1.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• .env.example (1 hunks)
• agent/src/index.ts (1 hunks)

🔇 Additional comments (2)

agent/src/index.ts (1)

417-421: LGTM! Implementation follows established patterns.

The DeepSeek API key retrieval logic is consistent with other providers and properly handles both character-specific and global settings.

.env.example (1)

242-242: LGTM! Configuration follows standard format.

The DeepSeek API key configuration is properly documented and follows the established pattern.

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[daizhengxue]

Hey @tcm390 and @odilitime,
I believe I modified just two files: .env.example and agent/src/index.ts. I'm unsure about resolving the pnpm-lock.yaml conflict; it mirrors the developer branch.
Could you help me with this issue?

[tcm390]

Hey @tcm390 and @odilitime, I believe I modified just two files: .env.example and agent/src/index.ts. I'm unsure about resolving the pnpm-lock.yaml conflict; it mirrors the developer branch. Could you help me with this issue?

I think it’s resolved :)

[daizhengxue]

cool thank you!!