# elizaOS Development Discord - 2025-03-30

## Overall Discussion Highlights

### Technical Issues & Troubleshooting
- **Plugin Import Errors**: Multiple users reported persistent issues with plugin imports on Linux, macOS, and WSL environments. A workaround was discovered by replacing `@import` statements with hardcoded paths to module files.
- **Agent Storage in v2**: Confusion around where user-created agents are stored in v2dev. While premade agents are in `/packages/the-org`, user-created agents via CLI appear to be stored elsewhere, possibly in a database rather than as code files.
- **Documentation Discrepancies**: Users noted inconsistencies between documentation and actual implementation, particularly regarding differences between v1 and v2 versions of ElizaOS.

### Platform Updates & Announcements
- **Agent Dev School Paused**: The agent development school sessions have been temporarily paused for 1-2 weeks while the team focuses on releasing v2 and auto.fun.
- **RAG Functionality**: Questions about the current status of Retrieval-Augmented Generation (RAG) functionality, which had previously experienced issues, went unanswered.

### Community Projects
- **Farcaster Plugin**: Development of a Farcaster plugin was discussed, with Odilitime sharing a link to the GitHub repository: https://github.com/elizaos-plugins/client-farcaster
- **GitHub-Chat Product**: A user named Sashimikun promoted their GitHub-Chat product built on ElizaOS.

### Plugin Management
- **No Official Versioning**: Odilitime clarified that there's currently no official versioning system for ElizaOS plugins, and descriptions are hardcoded in some plugin directories but not standardized.

## Key Questions & Answers

1. **Q**: What vector databases are people using these days? Is Pinecone a standard?  
   **A**: "pg-vector for me!" (answered by DefiniteOptimist)

2. **Q**: Can we expect an agent dev school tomorrow?  
   **A**: "Paused until v2 and auto.fun are released, approximately 1-2 weeks" (answered by shaw)

3. **Q**: How to change the name and version on npm?  
   **A**: "There is no versioning afaik. For names, it depends on what specifically needs to be changed." (answered by Odilitime)

4. **Q**: What is the currently agreed way of doing things in regards to installation and configuration?  
   **A**: Partially answered by jin who pointed to https://eliza.how/docs/quickstart and mentioned testing it recently

## Community Help & Collaboration

1. **Plugin Import Workaround**:
   - **Helper**: Tiki
   - **Helpee**: NnrbzZ
   - **Context**: Shared a workaround for plugin import errors by replacing `@import` with hardcoded path to index.js

2. **Scam Warning**:
   - **Helper**: Veight
   - **Helpee**: ElizaBAO🌟
   - **Context**: Successfully warned a user about a potential scam link, who then moved cryptocurrency to another wallet

3. **Vector Database Recommendation**:
   - **Helper**: DefiniteOptimist
   - **Helpee**: Hidden Forces
   - **Context**: Recommended pg-vector as an alternative to Pinecone for vector database needs

4. **Documentation Guidance**:
   - **Helper**: jin
   - **Helpee**: worldestroy
   - **Context**: Provided quickstart documentation link that was recently tested to address installation concerns

## Action Items

### Technical
1. **Fix plugin import resolution issues in the CLI**
   - Description: Module imports failing on Linux/WSL/macOS
   - Mentioned By: Tiki

2. **Investigate RAG usability issues**
   - Description: Follow up on previously reported RAG problems
   - Mentioned By: Mr. Stark

3. **Implement proper versioning system for ElizaOS plugins**
   - Description: Currently no versioning system exists for plugins
   - Mentioned By: Odilitime

4. **Update documentation to accurately reflect v2 installation and configuration processes**
   - Mentioned By: worldestroy

5. **Clarify where user-created agents are stored in v2 and how to access them**
   - Mentioned By: mindxploit

### Documentation
1. **Create guide for running ElizaOS on different platforms**
   - Description: Address recurring issues with Linux/WSL/macOS
   - Mentioned By: NnrbzZ

2. **Document GitHub dependency version pinning**
   - Description: How to pin versions for dependencies using the github: pattern
   - Mentioned By: DefiniteOptimist

3. **Update documentation to explain differences between v1 and v2**
   - Mentioned By: mindxploit

4. **Create clear instructions for creating and managing agents in v2**
   - Mentioned By: mindxploit

5. **Document the four plugin directories mentioned**
   - Description: Odilitime mentioned knowing of four plugin directories, which should be documented
   - Mentioned By: Odilitime

### Feature
1. **Improve visibility of user-created agents in the codebase**
   - Mentioned By: mindxploit

2. **Investigate standardizing plugin versioning and descriptions**
   - Description: Currently no official way to set descriptions, with hardcoded values in some directories
   - Mentioned By: Odilitime