# elizaOS Development Discord - 2025-01-07

## Overall Discussion Highlights

### Plugin Development & Integration
- **Cryptocurrency Tracking**: Discussions about plugin-coinprice which supports CoinGecko, CoinMarketCap, and CoinCap APIs
- **Social Media Integration**: 
  - Twitter client integration issues and error troubleshooting
  - Instagram client development with a draft PR in progress
  - Challenges with Twitter client ignoring plugins and not waiting for plugin actions to complete
- **Solana Ecosystem**: Discussions about onchain data solutions for Solana and potential plugin development for tracking memecoins not listed on major exchanges
- **Plugin Discovery**: Users seeking information about available plugins and installation methods

### Technical Infrastructure
- **Database Issues**: SQLite errors with zero-length vectors resolved by deleting db.sqlite file and pulling latest develop branch
- **Node.js Compatibility**: Several users encountered problems with Node.js version requirements (v23.3.0 vs older versions) causing build errors
- **API Configuration**: Users struggled with OpenAI and Heurist API configurations, receiving quota exceeded errors
- **CUDA Errors**: Memory-related crashes when attempting to use local LLMs
- **Code Organization**: Discussions about improving file structure in repositories, with PR #47 for agent-twitter-client addressing this

### Agent Development
- **Knowledge Integration**: Questions about effectively using folder2knowledge functionality and managing knowledge sections
- **Image Context**: Implementing systems to map specific images to predefined contexts/captions
- **Model Configuration**: Changing models from gpt-4o to gpt-4o-mini through environment variables
- **Framework Understanding**: Users expressing difficulty understanding the actions-evaluators-providers framework

### Project Direction
- **Token Standards**: Discussion about a potential move from Token 2022 to legacy token for cross-chain compatibility, clarified by Odilitime that no immediate changes were planned
- **Pull Requests**: Several PRs discussed including website enhancements, code organization improvements, and module conflict resolutions

## Key Questions & Answers

**Q: What is the difference between developing with eliza-starter and eliza?**  
A: Eliza comes with everything, while with starter you add plugins yourself.

**Q: How can I add a bot to Discord?**  
A: You need to configure DISCORD_APPLICATION_ID and DISCORD_API_TOKEN in .env file and add "discord" to clients in character file.

**Q: How can I add knowledge base beyond character file? Like couple of pdf files**  
A: Use folder2knowledge tool from the characterfile repo.

**Q: Where should I put the knowledge.json file in my Eliza project?**  
A: It goes into the character file JSON in the knowledge field.

**Q: How do I enable plugins like tavily websearch?**  
A: Add something like "@elizaos/plugin-web-search" in the plugins section of character file.

**Q: Where could I look for all the available plugins?**  
A: Look in https://github.com/elizaOS/eliza/tree/main/packages for everything with the plugin suffix.

**Q: What is the best way to install a plugin from develop branch?**  
A: Either checkout develop branch or clone it in a different folder and copy the plugin folder manually.

**Q: How can I make my agent use specific images I provide for contexts like memes?**  
A: Create a configuration dictionary/JSON where each image filename is associated with its corresponding context, then preload these mappings as context providers.

**Q: How to change the node version of Eliza framework?**  
A: Use nvm (Node Version Manager) to install and switch to the required version (23.3.0).

**Q: How to change the model in Eliza from gpt-4o to gpt-4o-mini?**  
A: Add SMALL_OPENAI_MODEL=gpt-4o-mini and MEDIUM_OPENAI_MODEL=gpt-4o-mini to your .env file.

**Q: Why does Twitter client ignore plugins and respond before plugin actions complete?**  
A: You need to use the client-twitter inside your plugin.

**Q: Are we moving away from Token 2022 to the legacy token for better cross-chain compatibility?**  
A: No major code refactor is happening right now; v2 is still in planning stages.

## Community Help & Collaboration

- **SQLite Error Resolution**: Santi helped BitCoder resolve SQLite errors by suggesting deletion of db.sqlite file and pulling the latest develop branch
- **Discord Bot Configuration**: W3_Bounty provided AD with specific .env configuration and character file settings for Discord integration
- **Knowledge Base Integration**: W3_Bounty recommended folder2knowledge tool to AD for adding PDF content to knowledge bases
- **Plugin Installation**: Cesar Rodriguez shared PR links showing required file modifications for installing plugins from the develop branch
- **Cryptocurrency API Selection**: Proteus recommended CoinGecko API to bendermind, noting its free tier allows 1000 calls per day
- **Node.js Version Management**: Ruby provided DreedX with step-by-step instructions for using nvm to manage Node versions
- **API Endpoint Creation**: Ruby shared code examples using Express to help Trọng create custom API endpoints in TypeScript
- **Code Organization**: Spit created PR #47 for agent-twitter-client to organize code into modules with absolute imports and better exports
- **Project Direction Clarification**: Odilitime reassured Dev LoD that no immediate changes to token standards were planned

## Action Items

### Technical
- Fix SQLite error with zero-length vectors by deleting agent/data/db.sqlite and pulling latest develop branch (Mentioned by Santi)
- Integrate Instagram client by completing and testing Instagram client PR (Mentioned by Spit)
- Create plugin for Solana onchain data for trades, Raydium and PumpFun data (Mentioned by Kostya)
- Implement image-to-text reference mapping for meme context (Mentioned by Ruby)
- Fix Node.js version compatibility issues with v23.3.0 (Mentioned by Multiple users)
- Resolve OpenAI quota and rate limit errors (Mentioned by spaded)
- Fix Twitter client plugin integration (Mentioned by saccharinedreams)
- Address CUDA memory errors with local LLMs (Mentioned by spaded, Idos)
- Review and merge PR #1951 (Mentioned by Santi)
- Review PR #47 for agent-twitter-client code organization refactor (Mentioned by Spit)
- Fix defillama plugin that doesn't work or remove it from PR #1773 (Mentioned by sayonara)
- Review PR #2027 related to removing non-working defillama plugin (Mentioned by sayonara)
- Review PR #1641 for module with resolved conflicts (Mentioned by Kaito)
- Address issues #46 and #44 in agent-twitter-client (Mentioned by sayonara)
- Reduce size of eliza in PR #3 in cloud-deployment-eliza repository (Mentioned by Mike D.)

### Documentation
- Add instructions for Instagram API app ID in README.md (Mentioned by R0am)
- Create guide for image context integration (Mentioned by Ruby)
- Improve provider runtime operation documentation (Mentioned by kAI wilder)
- Update Node.js version requirements in setup docs (Mentioned by Multiple users)
- Create more examples of simple agent applications demonstrating actions-evaluators-providers framework (Mentioned by 9000)
- Provide specific examples of evaluator implementations beyond bootstrap (Mentioned by kAI wilder)
- Create tutorial content for proper implementation of evaluators (Mentioned by 9000)

### Feature
- Twitter spaces plugin to listen to Twitter spaces without infinite loop (Mentioned by Vice man)
- Support for tracking Solana memecoins not listed on major exchanges (Mentioned by bendermind)
- Cross-channel memory for Discord agents (Mentioned by skmd | Kev's meat space)
- Better Twitter DM support (Mentioned by PushBear| BobaSaur)
- Enhance rabbi trader plugin with better EVM capabilities using premium API key from matcha.xyz (Mentioned by sayonara)