# elizaOS Development Discord - 2025-04-09

## Overall Discussion Highlights

### ElizaOS v2 Migration & Architecture
- The architecture has significantly changed from v1 to v2:
  - The "agent" package has been moved into "cli" with REST API integration
  - Agents are now database-driven rather than client-driven, enabling programmatic creation
  - REST API is now natively integrated into the system
- Users are actively working through the beta CLI setup process
- GitHub authentication is now required during fresh installation before interacting with the default character

### Plugin Development
- Community members are collaborating on plugin migration strategies for v2
- The `setup-monorepo` command is being recommended as a starting point
- The plugin-starter structure is being referenced as a template for new plugin development
- Several users are looking for guidance on how to adapt existing plugins to the new architecture

### API Integration
- Questions about REST API availability in v2 are emerging
- At least one user reported difficulties with message endpoints returning 404 errors despite agent showing active status
- Google Generative AI enterprise version configuration support is being questioned

## Key Questions & Answers

**Q: How has the architecture changed from v1 to v2?** (asked by standard)  
**A:** The "agent" package moved into "cli" with REST API integration, and agents are now database-driven for programmatic creation (answered by shaw)

**Q: How do I migrate a plugin to be used in v2?** (asked by LemonS)  
**A:** Use `npx @elizaos/cli@beta setup-monorepo`, check package/plugin-starter/index.ts structure or other plugins like openai and twitter (answered by sayonara)

**Q: Should I watch the existing AI Agent Dev School videos or wait for new content after v2?**  
**A:** It's recommended to wait, especially for those completely new to the subject

## Community Help & Collaboration

- **shaw** helped **standard** understand the new architecture by explaining how the agent package moved to CLI, REST API integration, and database-driven agents
- **sayonara** assisted **LemonS** with plugin migration to v2 by providing the CLI command for setup-monorepo and suggesting reference points
- **Nisita** reinforced advice to **LemonS** about plugin migration and shared a video resource (with disclaimer about possible changes)
- An unnamed community member successfully helped **Ξ2T** set up v2 late at night

## Action Items

### Technical
- Fix REST API message endpoint for v2 (message endpoint returns 404 despite agent showing active status) | Mentioned by: Titan | Livepeer-Eliza.com
- Address GitHub authentication requirement during fresh installation (CLI requires GitHub credentials before allowing interaction with default character) | Mentioned by: Titan | Livepeer-Eliza.com
- Resolve installation issues with error message shown in screenshot (user encountering errors when trying to start Eliza) | Mentioned by: AbdelazizElbagdadi
- Investigate support for Google Generative AI enterprise version configuration | Mentioned by: lay.qin

### Documentation
- Create migration guide for v1 to v2 (users struggling to understand architectural changes) | Mentioned by: standard
- Document plugin migration process for v2 (clear steps needed for converting existing plugins) | Mentioned by: LemonS
- Update or create new AI Agent Dev School content for v2 | Implied by discussion in agent-dev-school channel