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

feat: add venice provider #1017

Closed
wants to merge 1 commit into from

Conversation

bussyjd
Copy link

@bussyjd bussyjd commented Dec 12, 2024

Relates to:

Issue #1016 - Add Venice AI Provider Integration

Risks

Low - Adds new provider option without modifying existing functionality

  • Only affects users who explicitly configure Venice
  • No changes to core framework behavior
  • No database changes required

Background

What does this PR do?

Adds Venice AI as a new provider option to Eliza framework, offering a privacy-focused, uncensored alternative to existing AI providers.

What kind of change is this?

Features (non-breaking change which adds functionality)

  • Adds new Venice provider implementation
  • Extends provider types and configurations
  • Updates environment variable examples

Documentation changes needed?

My changes require a change to the project documentation.

  • Added Venice provider configuration to .env.example
  • Adding Venice in the list of supported providers
  • Updated provider type definitions
  • Added Venice-specific configuration documentation

Testing

Where should a reviewer start?

  1. Review the Venice provider implementation in packages/core/src/generation.ts
  2. Check environment variable handling in .env.example
  3. Review type definitions in packages/core/src/types.ts

Detailed testing steps

  1. Copy .env.example to .env
  2. Add Venice API credentials
  3. Configure character to use Venice provider
  4. Test basic text generation functionality
    • Verify privacy headers are properly set
    • Confirm uncensored responses work as expected
    • Check error handling behaves correctly

Discord username

bussyjd#4778

@bussyjd bussyjd closed this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant