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: deva client integration #1238

Open
wants to merge 28 commits into
base: develop
Choose a base branch
from

Conversation

stopmalone
Copy link

@stopmalone stopmalone commented Dec 19, 2024

Pull Request: Integrate Deva into Eliza

Relates to

This PR adds a new Deva client integration for the Eliza AI agent, enabling posting and scheduling posts to the Deva feed.

Risks

  • Minimal Risk: This integration is additive and does not alter existing functionalities of Eliza.
  • Dependency Management: Introduces a new dependency on Deva's API, which requires monitoring for future updates or changes.
  • Data Privacy: Ensures that any data shared between Eliza and Deva complies with our privacy policies.

Background

What does this PR do?

This PR introduces the capability to post and schedule content directly to the Deva platform from the Eliza AI agent. Users can now seamlessly integrate their Eliza-generated content with Deva, enhancing their content distribution and engagement strategies.

What kind of change is this?

Feature: This is a non-breaking change that adds new functionality to the Eliza AI agent by integrating with Deva’s API for posting and scheduling content.

Documentation Changes Needed?

Not at the moment.

Testing

Detailed Testing Steps

  1. Create a Deva Account

    • Navigate to deva.me, create an account, and press the "Get Started" button in the top right.
    • Get Started
  2. Complete Onboarding

    • Click through the onboarding screens and connect your preferred social account (e.g., Twitter) to Deva.
  3. Access the Deva Feed

    • You can now see the Deva feed, where you can post and interact with other Devas.
    • image
  4. Create an Application to get the token

    • At this point, you'll be able to get a token to interact with Deva, to do so:
      • Navigate to Apps chapter in settings by clicking the user icon in top right corner and then settings -> Apps, or opening apps
      • Press Apps and Session

        image
      • Press Create new app

        image
      • You are redirected to the form of the app creation, Name, Redirect URL and descriptions are necessary fields. Permissions are preselected and they are exactly enough for Eliza agent to post a message in feed.
      • After creating an app, select it from the list of apps;
      • Inside you will find a Get Token button, to generate a new token for your app:

        image
      • Later, it'll be visible in the list:

        image
  5. Update Environment Variables

    • Once you have the token, update the environment variables in the .env file:
      DEVA_API_KEY=YourApiKey
      DEVA_API_BASE_URL=https://api.deva.me # Production API URL
  6. Select Deva Client as Default Character

    • Select the Deva client as Eliza's default character and choose the desired model:

      Select Deva Client
  7. Run the Application

    • Execute the following commands to install dependencies and start the application:
      pnpm install && pnpm start
    • This will initiate the Deva client:

      Initiate Deva Client
    • Fetch the persona associated with your agent and the posts that you have pushed to the Deva feed:

      Fetch Persona and Posts
    • Once done, Eliza will post one message to the Deva feed immediately and schedule another one as a test message:

      Post Messages
  8. Eliza agent's post is in the feed!

    • image

Staging Environment Testing

To avoid populating the production Deva feed, you can perform the same flow in the staging environment. Ensure you update the related environment variable:

DEVA_API_BASE_URL=https://api-staging.deva.me # Staging API URL

@stopmalone stopmalone changed the base branch from main to develop December 19, 2024 13:06
@odilitime odilitime changed the title Feat/deva client integration feat: deva client integration Dec 20, 2024
odilitime
odilitime previously approved these changes Dec 20, 2024
@stopmalone
Copy link
Author

@odilitime
Thank you for the initial approval, can you please tell me what are the next steps for this PR approval?
Seems like it is not being reviewed by maintainers to mover further

Copy link

@luduvigo luduvigo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting PR, didn't know DEVA

btw I see a lot of indentation issues there

@@ -2,7 +2,8 @@

## Overview

Eliza's client packages enable integration with various platforms and services. Each client provides a standardized interface for sending and receiving messages, handling media, and interacting with platform-specific features.
Eliza's client packages enable integration with various platforms and services. Each client provides a standardized

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this went to a new line?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats the maximum chars in line enforce

Thank you for you pointing this out I've pushed an update!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About Deva:

The project is fresh and we are just having a silent run to improve quality :)

@@ -1,73 +1,74 @@
{

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indentation?

@stopmalone
Copy link
Author

@luduvigo

Hello,
The conflicts and issues are resolved, please tell me if we need to add something else to the PR or is it good to go!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants