Skip to content

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.

14.5 KB
Raw Blame

X posts: Three.ws User Group first in-world meetup (IBM Community)

Copy for the launch-day X push. The IBM angle is the point of this event, so IBM leads every post: this is the first in-world meetup of the Three.ws User Group on IBM Community, an official IBM Community user group, held inside three.ws itself rather than on a call.

Event: three.ws Community Meetup: Live on the $THREE Server When: Friday, August 7, 2026, 8:00 AM Pacific / 11:00 AM Eastern / 4 PM London / 5 PM Berlin Where: three.ws/play, the $THREE world pinned at the top of the lobby Cost: free, no download, no install, no account, no wallet

IBM event listing (the link every post points at): https://community.ibm.com/community/user/events/event-description?CalendarEventKey=25d71799-16b5-4342-b2e5-019fcf9622ca&CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016

Two rules for every post here:

  1. Never state hours-until. Say "today" and give the absolute clock time. A post that says "in 4 hours" is wrong the moment it is reposted, quoted, or found late.
  2. IBM in the first line. The user group is the reason this event exists. Do not bury it under the game features.

1. Main teaser (post this first, with video)

Today: the first in-world meetup of the Three.ws User Group on IBM Community.

Not a webinar. Open three.ws/play in a browser, become a 3D avatar, and walk around the $THREE world with the team. Spatial voice, live demos, open Q&A.

8 AM PT / 11 AM ET. Free, no install, no account.

[IBM event link]

Media: the strongest 20 to 40 seconds you have of /play. Lead with movement (a crowd in the plaza, avatars walking) rather than a static wide shot. First frame matters more than the last.


2. The IBM technical post (this is the one that earns the user group its members)

Post this second, roughly an hour after the teaser. It is the reason an IBM developer should care.

Why an IBM Community user group is meeting inside a 3D world:

three.ws is an IBM Business Partner. Our agents think on IBM Granite served through watsonx.ai, and two of our MCP servers are IBM-native:

@three-ws/ibm-watsonx-mcp, watsonx.ai on your own IBM Cloud account @three-ws/ibm-x402-mcp, pay-per-use Granite billed in USDC, no IBM account needed

Come ask us about any of it, in person: [IBM event link]


3. Alternates for the main slot

Pick one. Do not post all three.

Short and blunt

The Three.ws User Group on IBM Community meets today, inside three.ws.

A browser tab, a 3D avatar, spatial voice, live demos, and the team answering anything.

8 AM PT / 11 AM ET. Free: [IBM event link]

Contrast-led

Most user groups meet on a video call.

Ours meets in a 3D world you open in a browser tab. You walk up to someone and you hear them, from the direction they are standing.

First Three.ws User Group meetup on IBM Community is today, 8 AM PT: [IBM event link]

Builder-led

If you build AI agents that need a body, spatial reasoning, or generative 3D, the Three.ws User Group on IBM Community is your room. It meets today, and it meets inside the product.

8 AM PT / 11 AM ET, free, browser only: [IBM event link]


4. Thread version (if you want the reach)

1/

Today: the first in-world meetup of the Three.ws User Group on IBM Community.

Not a Space, not a webinar. An actual 3D world you walk into from a link, with the team standing in it.

8 AM PT / 11 AM ET: [IBM event link]

2/ (attach the best plaza / crowd clip)

How you join, in full: open three.ws/play, click the $THREE world pinned at the top, you are in. Guests get an avatar automatically. No download, no account, no wallet.

3/ (attach voice or group-conversation footage)

Voice is spatial. You hear the people near you, from the direction they are standing, fading as you walk away. Three conversations can happen twenty meters apart without talking over each other, exactly like a conference hallway.

4/ (attach /create footage, or an avatar generation clip)

Want to show up as yourself? Build a custom 3D agent first at three.ws/create from a text prompt or a selfie. Rigged and animation-ready in about a minute, and it follows you into the world.

5/ (attach the strongest world / demo footage)

Why IBM Community: three.ws is an IBM Business Partner, our agents run on IBM Granite through watsonx.ai, and we ship @three-ws/ibm-watsonx-mcp and @three-ws/ibm-x402-mcp for anyone building on watsonx.

Live demos and open Q&A on all of it today: [IBM event link]

6/

Every community can do this, not just ours. Every pump.fun coin already has a world at three.ws/play?coin=. No booking, no whitelist, no fee. The venue layer is a URL scheme.

Come see it working: [IBM event link]


5. Follow-ups for the rest of the day

Shortly before doors (quote your own main post)

Doors open shortly. New to 3D worlds? Come 10 minutes early and we will walk you through the controls personally. three.ws/play

The moment it goes live

We are live. The Three.ws User Group on IBM Community is meeting inside three.ws right now.

Open three.ws/play, click the pinned $THREE world, walk over and say hi.

Mid-event, with a screenshot of the actual crowd

This is an IBM Community user group meeting, happening right now. Still time to walk in: three.ws/play

After it ends (this is the one that recruits for the next event)

That was the first Three.ws User Group meetup on IBM Community.

[attach the group shot or the best clip from the day]

The group is open and the world stays open. Join the group: [IBM user group link]


5b. Sharing Jessica's IBM Community blog

Jessica's post on the user group ("Join the Three.ws User Group's First In-World Meetup This Friday") is the single best asset in this campaign, because it is IBM's own voice saying the thing we have been saying all week. Our posts are marketing; hers is a user group organizer telling her own members not to skip this. Lead with who wrote it, let the quote carry the argument, and keep our own commentary to one line.

Two accounts, two jobs. @trythreews posts the institutional version: IBM wrote this, here it is. @nichxbt posts the human version: working with her has been great. Do not put the warm personal note on the brand account, and do not post both within a few minutes of each other.

From @trythreews (recommended, tight quote). This is the posted version.

The official @IBM blog for today's meetup is up, written by Jessica, a core member of the @IBM team behind the Three.ws User Group and the one who made all of this possible.

"It is not a video call. The three.ws team is hosting the group's first community meetup inside the platform itself, in the flagship world at three.ws/play. You attend as an avatar, you hear the people standing near you through spatial voice chat, and the product tour happens by literally walking through the product."

[blog link]

That cut is deliberate. The second paragraph of her post is the whole argument in four sentences and it ends on the best line she wrote ("the product tour happens by literally walking through the product"). Ending a quote on the strongest sentence is worth more than including every sentence.

From @trythreews (full quote, if you want her framing of why the group exists)

The official blog for today's meetup is up on IBM Community, written by Jessica, a core member of the @IBM Community team behind the Three.ws User Group.

"When this user group launched in July, the promise was more than threads and blog posts: it was live sessions with the people actually building AI agents with 3D capabilities. This Friday we get the first one, and I want to make sure nobody misses it because they assumed it was another webinar link.

It is not a video call. You attend as an avatar, you hear the people standing near you through spatial voice chat, and the product tour happens by literally walking through the product."

[blog link]

From @nichxbt (the human one, quote-tweeting the @trythreews post above)

Jessica has been helping us with this from the start, and honestly it has been a pleasure working with her. IBM Community got a real organizer on this group.

Read her post, then come meet her in-world. She built her own 3D agent from a selfie for today.

Media for the @trythreews post: Jessica's custom 3D agent, in-world, is the single best image you can attach. It closes the loop: the person who wrote the IBM blog is standing in the product, as an avatar she generated from a selfie. Second choice is a clean screenshot of the blog header on community.ibm.com so the IBM domain is visible in the frame.

Rules for this one:

  • Name her and her role in the first line. "Jessica from IBM wrote this" is the headline, not the blog title.
  • Quote verbatim inside quotation marks. Do not paraphrase her into our voice. The credibility of the post comes entirely from it being her words, not ours.
  • One link, hers, at the end. Do not stack the event listing and the user group link on this post; every other post in the campaign already carries those.
  • Do not add our own "and here is why that matters" paragraph. Her post already argues it.

5c. Sharing Jessica's recap (published)

Jessica's recap, "The First Three.ws User Group Meetup: How It Went", is up on IBM Community. Same two-account split as the announcement post in 5b: @trythreews posts the institutional version, @nichxbt quote-tweets it with the human one. Do not post both within a few minutes of each other.

From @trythreews (recommended, leads with the concurrency stat). This is the posted version.

The stat is the hook: it's the single number in her post a reader has no way to guess, and it lands harder on X than the framing sentence does. This excerpt is contiguous, verbatim, straight out of her post, just the framing clause and the number, without the full paragraph's extra sentence.

Jessica, the @IBM Community organizer behind the Three.ws User Group, just published her own recap of Friday's meetup.

"This group is still small, but the open world we held it in is not gated to members: anyone with the link could walk in, and a lot of people did. Peak concurrency in the world hit 3,145 avatars at once over the course of the day, well past anything a call could have seated."

https://community.ibm.com/community/user/blogs/jessica-swanson/2026/08/08/the-first-threews-user-group-meetup-ibm

From @trythreews (alternate, tight quote without the stat)

Jessica, the @IBM Community organizer behind the Three.ws User Group, just published her own recap of Friday's meetup.

"Neither IBM nor three.ws is the slow, boring-enterprise thing people assume from the outside. We both like trying things that are actually new, and a nine-hour user-group meetup held entirely inside a 3D world, instead of on a call, is exactly that kind of thing. It held up."

https://community.ibm.com/community/user/blogs/jessica-swanson/2026/08/08/the-first-threews-user-group-meetup-ibm

From @trythreews (full quote, if you want both the framing and the number)

Jessica, the @IBM Community organizer behind the Three.ws User Group, just published her own recap of Friday's meetup.

"Neither IBM nor three.ws is the slow, boring-enterprise thing people assume from the outside. We both like trying things that are actually new, and a nine-hour user-group meetup held entirely inside a 3D world, instead of on a call, is exactly that kind of thing. It held up. This group is still small, but the open world we held it in is not gated to members: anyone with the link could walk in, and a lot of people did. Peak concurrency in the world hit 3,145 avatars at once over the course of the day, well past anything a call could have seated, even though most of that crowd came for the open world itself rather than being User Group members."

https://community.ibm.com/community/user/blogs/jessica-swanson/2026/08/08/the-first-threews-user-group-meetup-ibm

From @nichxbt (the human one, quote-tweeting the @trythreews post above)

Jessica called it exactly right: this was never going to be the slow, boring-enterprise version of a partnership. Proud of what we built together and even more proud she felt like writing that.

Read the whole thing, then go stand in the world she's describing: three.ws/play

Media for the @trythreews post: a clean screenshot of the recap's header on community.ibm.com, so the IBM domain and Jessica's byline are visible in the frame. Second choice: the in-world plaza shot from the day, if you have one with a visibly dense crowd, since the post is making a concurrency claim.

Rules for this one, same as 5b:

  • Name her and her role in the first line. "Jessica wrote a recap" is the headline, not the blog title.
  • Quote verbatim inside quotation marks. Do not paraphrase her into our voice.
  • One link, hers, at the end. Do not stack the event listing or the user group link on this post.
  • Do not add our own "and here is why that matters" paragraph. Her post already argues it.

6. Recycling the existing /play footage

Map what you already have to the beats above, so each post carries a clip that matches its copy:

Post Best clip to use
Main teaser Crowd or plaza movement. Motion in frame one, no menus, no cursor.
IBM technical post Screen-recording of an agent responding, or the world at its best. Text carries this one.
Thread 2 The lobby, then landing in the world. Shows the zero-friction claim rather than asserting it.
Thread 3 Avatars standing in a group, chat bubbles, people walking up to each other.
Thread 4 An avatar generation on /create, then that avatar in-world.
Thread 5 and 6 Widest good-looking shot you own, or any world other than $THREE.

Practical notes for reused footage:

  • Trim anything showing a debug overlay, a localhost URL, an empty world, or an FPS counter.
  • Assume muted autoplay. If a clip only works with sound, it does not work.
  • Native upload, never a link to a video elsewhere. X suppresses off-platform video reach.
  • Square or 4:5 outperforms 16:9 in the timeline. Crop toward the avatars.
  • One link per post, at the end. The IBM event listing before and during; the IBM user group page after it ends.