# elizaOS Discord - 2025-06-30

## Overall Discussion Highlights

### ElizaOS V2 Announcements
- Kenk highlighted five key upgrades coming in ElizaOS V2:
  - Multi-agent orchestration
  - Dynamic character evolution
  - Trusted Execution Environment (TEE)
  - New CLI & service layer
  - Native RAG framework
- A Notion workspace has been created to support V2 communications and marketing efforts
- Partners are being asked to help amplify V2 messaging "while the sun is shining on Solana"

### Twitter/X Plugin Issues
- Multiple users reported 403 errors with the Twitter plugin, particularly with `fetchHomeTimeline`
- Root cause: Twitter's API changes from v1 to v2 endpoints and increased pricing ($200/month for basic tier)
- Workarounds discussed include:
  - Using twurl for authentication testing
  - Disabling timeline features
  - Potentially updating the plugin to use v2 endpoints

### ElizaOS Positioning
- Discussion about ElizaOS's role in the AI agent ecosystem
- jintern explained that ElizaOS is focused on being open-source infrastructure rather than token-based
- Kenk noted that many "Virtuals agents" use elizaOS as their underlying framework

### Technical Issues
- Character file formatting issues with the outdated chats2character.js script
- Docker build problems related to git submodules
- Entity creation settings for Discord bots with large servers

## Key Questions & Answers

**Q: Why do we not have a known Eliza agent with millions of followers?** (DorianD)  
A: Building good agents takes time, most are still experimental. Plus getting millions of followers is hard even for humans. We're still early days, focus is on making the tech solid first. (jintern)

**Q: Will you make the airkit plugin so AI agents can utilize it?** (Dr. Neuro)  
A: That's above my intern pay grade, but sounds like a cool idea. Maybe bring it up in #feature-requests or tag one of the core devs. (jintern)

**Q: Can someone please give me a proper argument on why ElizaOS is going to be the leader in AI agents frameworks over virtuals for example?** (3on_.)  
A: Many virtuals 'agents' use elizaOS as the framework. Says it all really. (Kenk)

**Q: Why is the Twitter/X client deprecated?** (~oxy)  
A: The Twitter client uses old v1 API endpoints that Twitter's been phasing out, causing 403 errors, especially on free tier. Plus they increased API pricing to $200 for basic access. (jintern)

**Q: What's the optimal character file length?** (Luke 🇦🇺)  
A: Long is fine, with the most important parts being style and messageExamples. The style section is fully loaded as context, while bio loads 10 random entries, messageExamples loads 5, and topics loads 1. (Gnomon🪲)

**Q: How can I prevent my agent from creating entities for all 54k members in a Discord server?** (Scooter)  
A: Set `ENTITY_CREATION_MODE=on_interaction` in your .env file to only create entities when users actually talk to the agent. (jintern)

**Q: Can you share how you did the 3-legged oauth for Twitter?** (alerios)  
A: Use twurl (version 0.9.7) with the command `twurl authorize --consumer-key "$X_CONSUMER_KEY" --consumer-secret "$X_CONSUMER_SECRET"` and open the generated URL in incognito mode. (Luke 🇦🇺)

## Community Help & Collaboration

### Twitter API Troubleshooting
- **Helper:** Luke 🇦🇺 | **Helpee:** alerios
- **Context:** Struggling with Twitter OAuth authentication
- **Resolution:** Provided detailed instructions on using twurl to authorize Twitter API access

### Discord Bot Configuration
- **Helper:** jintern | **Helpee:** Scooter
- **Context:** Agent creating entities for all 54k Discord server members
- **Resolution:** Suggested setting `ENTITY_CREATION_MODE=on_interaction` in .env file to limit entity creation

### Docker Build Issues
- **Helper:** jintern | **Helpee:** Robert
- **Context:** Docker build errors with ElizaOS 1.0.12
- **Resolution:** Suggested adding `SKIP_POSTINSTALL=1` to bun install command or editing package.json to remove the postinstall script

### Documentation Resources
- **Helper:** Bealers | **Helpee:** gamingalpha_
- **Context:** Providing better starting point for ElizaOS
- **Resolution:** Suggested https://eliza.how as the best starting point

### Health Data Project Feedback
- **Helper:** jintern | **Helpee:** yashpunmiya
- **Context:** User shared a health data project
- **Resolution:** Provided feedback on the UI and suggested considering privacy/encryption for sensitive health information

## Action Items

### Technical
- Update Twitter plugin to use v2 API endpoints instead of deprecated v1 endpoints (Gnomon🪲)
- Fix bearer token not being added to request headers in Twitter plugin (jintern)
- Try disabling timeline settings in Twitter plugin to see if it boots with just mentions and replies (Gnomon🪲)
- Set `ENTITY_CREATION_MODE=on_interaction` in .env to prevent creating entities for all Discord server members (jintern)
- Check if Pendium has solved the Twitter API issues and potentially adopt their approach (alerios)

### Documentation
- Update Twitter plugin README.md to reflect current API limitations and pricing (Robert)
- Collate AI16z-related assets into a single space (Kenk)
- Review and utilize the elizaOS Community Workspace for V2 communications (Kenk)
- Need for better explanation of ElizaOS advantages over competitors like Virtuals (3on_.)
- Coordinate marketing efforts to increase visibility of V2 while Solana is trending (Kenk)

### Feature
- Airkit plugin for AI agents (Dr. Neuro)
- Token integration for ElizaOS similar to Virtuals (hildi)