83c977f6d7
- Phase 34 Partner API Keys battlecard - A2A Enterprise Deep-Dive SEO brief + social copy - Phase 30 social copy (X + LinkedIn threads) - Phase 30 blog post (remote-workspaces) - Launch pages (org-scoped API keys, instance ID, EC2 SSH) - Fly.io + Discord Adapter + EC2 social copy - Screencast storyboards (4 demos) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.8 KiB
2.8 KiB
Phase 30 — Short-Form Social Copy
Source: PR #1306 merged to origin/main (2026-04-21) Status: MERGED — awaiting Marketing Lead approval for publishing
X (140–280 chars)
Version A — Technical
Phase 30 ships: Molecule AI remote workspaces are GA.
Agents running on your laptop, AWS, GCP, or on-prem now register to the same org as your Docker agents. Same A2A. Same auth. Same canvas.
Remote badge. That's the only difference.
→ docs: https://moleculesai.app/docs/guides/remote-workspaces
Version B — Product
Your laptop is now a valid Molecule AI runtime.
One org. Mixed fleet: Docker agents on the platform, remote agents wherever your infrastructure lives. One canvas. One audit trail.
Phase 30 is live.
Version C — Developer
How to run a Molecule AI agent on your laptop in 3 steps:
1. Create a workspace (runtime: external)
2. Run the Python SDK
3. Watch it appear on the canvas
That's it. Phase 30 is live.
docs → https://moleculesai.app/docs/guides/remote-workspaces
Version D — Enterprise
Multi-cloud AI agent fleets, single governance plane.
Phase 30: agents on AWS, GCP, on-prem, your laptop — all visible in one canvas, all governed by the same platform auth, all auditable.
GA today.
LinkedIn (150–300 words)
We're launching Phase 30: Remote Workspaces.
Most AI agent platforms assume all agents run in the same environment as the control plane. Molecule AI didn't — but until today, that's where the story ended.
Phase 30 changes that. Your agent can now run anywhere:
- On a developer's laptop, for local iteration and debugging
- On AWS or GCP, for production workloads in your cloud
- On an on-premises server, for enterprise environments with data residency requirements
- On a third-party endpoint, for existing SaaS integrations
And from the canvas, you can't tell the difference. Same workspace card. Same status. Same chat tab. Same audit trail. The only visible signal: a purple REMOTE badge.
The governance is the same. The A2A protocol is the same. The auth contract is the same. Where the agent runs is a deployment detail — not an architectural constraint.
Phase 30 is generally available today.
See the quick start → [link]
Read the guide → [link]
Image suggestions per post
| Post | Best image |
|---|---|
| X Version A (Technical) | Fleet diagram: marketing/assets/phase30-fleet-diagram.png |
| X Version B (Product) | Canvas screenshot: marketing/assets/phase30-canvas-remote-badge.png (once captured) |
| X Version C (Developer) | Terminal screenshot: python3 run.py + canvas showing REMOTE badge |
| X Version D (Enterprise) | Fleet diagram (same as A) |
| Fleet diagram OR canvas screenshot |
Hashtags
#MoleculeAI #RemoteWorkspaces #AIAgents #AgentFleet #AIPlatform #MCP #A2A #MultiCloud