Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
Community
three.ws is built in the open and the conversation happens in public. Pick the room that fits what you want to do.
Where to find us
| Channel | Best for | Link |
|---|---|---|
| GitHub Discussions | Design questions, feature ideas, showing off what you built, anything worth keeping searchable | github.com/nirholas/three.ws/discussions |
| Telegram community | Real-time chat, quick help, "is this thing on?" | t.me/three_ws_community |
| X community | Demos, avatars people made, launch chatter | x.com/i/communities/1923523161230078106 |
| IBM Community group | Enterprise and integration discussion with the IBM developer community | community.ibm.com group |
| Release channel | Every user-visible change, pushed automatically on deploy | t.me/three_ws and /changelog |
| Issues | Bugs and concrete feature requests | github.com/nirholas/three.ws/issues |
| Security | Vulnerabilities, privately | Report an advisory |
Announcements also go out on @trythreews, which is the
only X account three.ws posts from. The founder's personal account, @nichxbt, has
been unavailable since August 27, 2026, so nothing posted under that handle is us
while it is down.
The table above is the complete set of rooms we run. three.ws/community carries the same list alongside the one $THREE contract address, so anything claiming to be us can be checked against a single page. Two rules that never change: nobody from three.ws messages you first or asks for a seed phrase, a private key, or a wallet signature, and there is no second token, so a "new" or "migrated" $THREE contract is a theft whatever it is posted under.
Which channel for which question
- "How do I embed an avatar on my site?" Discussions, Q&A category. The answer helps the next person who searches it.
- "The avatar renders as a T-pose." Open an issue with the GLB or a link to it. Rig problems are almost always reproducible and we want the file.
- "Look what I made." Show and tell on Discussions, or the X community. We repost good ones.
- "Is anyone working on X? I want to help." Check
good first issuefirst, then say so in the issue thread so nobody duplicates your work. - "I found a security hole." Never a public issue. Use the advisory form.
House rules
The Code of Conduct applies in every one of these rooms, not just the GitHub ones. It is the Contributor Covenant, and it is enforced.
Two additions specific to this project:
- No trading talk in the technical channels. three.ws has on-chain surfaces and there is a token in the ecosystem. Price talk belongs nowhere near a bug thread. Issues and Discussions are for the software.
- Share the file. Rendering and rigging bugs are hard to guess at and trivial to diagnose from the actual GLB. If you can share the model, share it.
Contributing
New here? Start with Your first contribution, a 15-minute path from clone to open PR. The full guide is CONTRIBUTING.md, and how we sort incoming work is documented in Triage.