Bhindi is an awesome playground for creating & running AI agents, but until today your agents have been… quiet.
Music discovery, curation & playback is still locked away in browser tabs and Spotify apps.

VibeStream injects high-octane Spotify super-powers straight into Bhindi.
Search tracks & artists, build playlists, get recommendations or inspect the current playback — all without ever leaving your chat.

🔥 What makes it magical?
• Hands-free playlist management – tell the agent the vibe and it keeps your queue fresh while you code.
• Lyric-to-song lookup – can't remember the title? Just type a line from the song and watch it drop into your playlist.
• Instant party mode – summon a high-energy banger list in seconds so you can DJ and host.
• Contextual soundtracks – weather, time of day, even your meeting calendar can shape the tracks it serves.
• Focus on shipping – let AI sweat the music decisions while you crush features.

The Problem we are solving
Context-switching between Bhindi and Spotify kills flow‐state 😵‍💫.
Manual playlist curation is slow & uninspired.
Developers want a programmable way to mash music into their workflows.
What we built
• A type-safe Node.js API that wraps Spotify's Web API and exposes it as Bhindi tools.
• Secure OAuth 2.0 flow with refresh logic so your tokens never expire mid-jam.

Challenges Faced

1. Lack of native Spotify OAuth support in Bhindi
   Bhindi did not originally provide a built-in flow for Spotify OAuth. To onboard our Spotify agent, we engineered a bespoke solution: a lightweight front-end that handles the OAuth handshake, acquires the access and refresh tokens, and then redirects users back to Bhindi with clear, step-by-step instructions. This workaround let us integrate Spotify securely while maintaining a seamless user experience.

2. Intermittent Spotify API behaviour
   During development the Spotify Web API occasionally returned inconsistent responses and sporadic 5xx errors, requiring additional error-handling logic and token-refresh safeguards. These edge cases demanded extra testing time and robust retry strategies to ensure a stable user experience.