Here's the swarm configuration I used:

Claude Swarm 2-shotted the conversion yesterday. I just released the Claude Code SDK for Ruby!. Here it is

Using Claude Swarm and the SwarmUI to convert the Claude Code Python SDK to Ruby. I built a UI using Rails to assist running multiple claude-swarm instances in my machine. Will release it very soon!

claude-swarm 0.2 is coming soon and will bring the ability to add OpenAI instances to the swarm, so you can have O3 criticize the work Opus does. And in tandem there will be a Web UI from where you can launch and manage multiple swarms from a single interface.

RT @obie: 🚀 ClaudeOnRails v0.2.0 is here!. Now with Rails MCP Server integration for real-time documentation access. Your AI agents just go….

RT @obie: 🚂 Announcing ClaudeOnRails!. Hey everyone! Just released a gem that might change how you build Rails apps. ClaudeOnRails creates….

RT @obie:

Raix 1.0 by @obie is out!.

Ready to 10x your development speed?. 1. Install: `gem install claude_swarm`.2. Create your team: `claude-swarm init`.3. Launch: `claude-swarm --vibe`. Star the repo: Join the revolution of AI-powered development teams. What will you build? 🚀.

It's not about better AI. It's about better architecture. Why have one overworked generalist when you can have focused specialists?.

claude-swarm under the hood:. • Uses MCP for inter-agent communication.• Each agent runs in isolated directories with specific permissions.• Tree-like hierarchy (architect → team leads → specialists).• All sessions logged in .claude-swarm/. Open source & MIT licensed 🔥.

Your swarm can have agents that work together across multiple codebases. Before: $10k/month, 2-week sprints, communication issues.After: $40/month, instant results, perfect coordination. The kicker? The AI team documents everything automatically. (Yes, for real).

Stop context-switching between different parts of your codebase.With claude-swarm, each AI agent stays focused:. - Frontend agent ONLY sees /frontend. - Backend agent ONLY touches /api. - DevOps agent manages /infrastructure. They collaborate when needed, stay focused always.

Here's claude-swarm in action:. 1. Define your team in YAML.2. Run `claude-swarm --vibe`.3. Give it the instructions.4. Watch your AI team collaborate. The lead delegates to a tree of specialists. They communicate via MCP. It's like having a $800k/year team for $40/month.

🐝 Just released claude-swarm 0.1.9: Turn Claude into an entire AI dev team. Imagine having:. - A lead architect Claude. - Frontend specialist Claude. - Backend expert Claude. - DevOps engineer Claude. All working together on YOUR codebase. This changes everything 🧵.

RT @obie: Behold the power of @AnthropicAI's Opus 4 in Claude Code. About 4 hours of human clock time yesterday….

RT @nixcraft: sudo retweet.

RT @TumaT: Orbital Clash foi o projeto que mais gostei de trabalhar. O primeiro jogo divertido a ponto de gerar um campeonato entre os alun….

Nobody will switch audiobook stores because a home assistant. Nobody will switch assistants because of audiobook stores. Same for music and any other service. None of you own all the best services. So please, I beg you, allow each other support your best services.

Dear @Apple, @googlenest and @alexa99 - you know what’s delaying everyone’s home automation dreams? Not being able to tap into each other’s services. You probably make more money on services than selling your $50 assistant speakers. ⬇️.