band-ai-helper

What it does

A reference and troubleshooting guide for Band.ai, the agent-coordination platform behind the "Band of Agents" hackathon, for when Claude Code hits an unresolvable package name or a confusing auth error while wiring an agent into Band.

How it works

Band splits into two APIs: a REST "Request API" (client to platform, for sending) and a WebSocket "Subscriptions API" (platform to client, for receiving). Most confusing bugs trace back to only implementing one half. An agent that "sends fine but never receives anything" almost always means only the REST side got built.

The skill routes by integration path, Framework Adapter, official Python SDK, Custom Integration for other languages, or MCP for platform management only (MCP categorically can't receive messages), and resolves the single most common point of confusion: there's no band-sdk npm package. It's Python-only on PyPI. If Claude Code asks why "Band SDK isn't on npm," that question itself means the project needs a hand-rolled REST + WebSocket integration against Band's own documented API, not an npm install.

Try it

I'm getting [error] while connecting my agent to Band.ai. My stack is [language/framework]. I'm trying to [send messages / receive messages / both]. Walk me through which Band integration path fits (Framework Adapter, the official SDK, a Custom Integration, or MCP) and fix the specific error I'm seeing.

When to reach for it

Any time Band.ai, BAND_API_KEY, agent_config.yaml, or a Band websocket/auth error shows up in a Claude Code session and the fix isn't obvious.