# elizaOS Discord - 2026-03-17

## Overall Discussion Highlights

### Business Strategy & Token Performance

Community members expressed significant concerns about ElizaOS token performance, particularly as the broader AI crypto ecosystem experiences growth. Multiple users questioned the marketing strategy and Shaw's focus on promoting other projects, specifically Milady.

**Odilitime clarified the business model:** The strategy involves Shaw promoting the Milady product to create distribution for elizacloud, which generates revenue to power the ElizaOS flywheel. While acknowledging the plan hasn't achieved results yet, the team plans to launch the elizacloud product by end of week or early next week.

**Unresolved confusion:** Multiple users asked which version of Milady (SOL or BSC) is officially supported, but this question remained unanswered throughout the discussions.

### Technical Development & Integration

**Unbrowse Integration:** lekt9 introduced "unbrowse," an innovative browser for agents that operates at 100x speed by traversing APIs instead of DOM while indexing web APIs for agent use. They sought guidance on integrating this with ElizaOS. Odilitime provided concrete direction by pointing to the plugin registry and documentation resources.

**Framework Organization:** SYMBiEX from CidSociety proposed creating a centralized directory/registry system similar to Clawhub that would house both skills and plugins. Stan expressed agreement with this proposal, suggesting community interest in more organized framework component management.

### Technical Issues

A Google Form-based role assignment system experienced configuration problems, with users encountering "Invalid Dynamic Link" errors indicating either unparseable URIs or incorrectly configured Dynamic Links domains.

## Key Questions & Answers

**Q: I'm building unbrowse, a browser for agents - where can I integrate this with elizaos?**  
**A:** Check https://github.com/elizaos-plugins/registry for the distribution system and packaging, or docs.elizaos.ai for plugin creation guide. You can also use cursor to make one. *(answered by Odilitime)*

**Q: What's the best way to contact shaw?**  
**A:** You can probably just dm him *(answered by Inhuman Resources)*

**Q: What if we did something similar to Clawhub for a directory/registry with skills and plugins?**  
**A:** Stan expressed agreement with the idea *(answered by Stan ⚡)*

### Unanswered Questions

- Does Milady support Sol or BSC after all? *(asked by 梦行人 and g)*
- Why is the Google form role assignment not working? *(asked by heimejorgen)*
- Do you happen to have a ticket channel where I can talk to an admin? *(asked by Yk_kendy)*

## Community Help & Collaboration

**Odilitime → lekt9**  
Provided comprehensive guidance on integrating unbrowse browser for agents with ElizaOS, directing to plugin registry link and documentation resources, and suggesting using cursor for automation.

**Inhuman Resources → lekt9**  
Assisted with contact information, suggesting direct messaging Shaw for communication needs.

**Odilitime → Community**  
Addressed widespread confusion about business strategy by explaining the flywheel model connecting Milady product to elizacloud to ElizaOS revenue generation.

## Action Items

### Technical
- **Launch elizacloud product end of this week/early next week** *(mentioned by Odilitime)*
- **Fix Google Form Dynamic Link configuration error preventing role assignment** *(mentioned by heimejorgen)*
- **Complete unbrowse integration as ElizaOS plugin for API-based agent browsing at 100x speed** *(mentioned by lekt9)*

### Documentation
- **Clarify which Milady version (SOL or BSC) is officially supported** *(mentioned by 梦行人, g)*

### Feature
- **Create a Clawhub-style directory/registry system for skills and plugins** *(mentioned by SYMBiEX <<CidSociety>>)*

---

## Community Notes

**New Member Introduction:** truebrujah introduced themselves as a Senior Full-Stack & AI Developer with expertise in LLM integration, autonomous agents, workflow automation, and blockchain systems. Their tech stack includes React, Next.js, TypeScript, Node.js, Python, PostgreSQL, MongoDB, PyTorch, TensorFlow, OpenAI API, LangChain, AWS, Docker, and Kubernetes.