Exploring Chat Assistant Development in B2B Tools
We’re diving into building a chat assistant for our B2B developer tool, and it’s a journey filled with choices. Here’s what we’re considering:
- Key Features: Integrating domain-specific tools (MCP), streaming responses (SSE), and preserving conversation history.
- Claude Agent SDK: A potential time-saver with built-in agent loop, compaction, hooks, and session management.
- Challenges:
- Single-user CLI orientation leading to inefficiencies.
- Overhead and memory issues in long-running processes.
- Dependency complexities between Node.js and Python.
As we weigh our options, we’re leaning towards building our agent loop via the Messages API.
🔍 Your Experience Matters: Have you navigated similar decisions? We’re keen to learn from anyone who’s used the SDK in multi-tenant settings or those who transitioned from the SDK to custom solutions.
💬 Let’s Connect: Share your insights in the comments! Your expertise could illuminate the path for many of us.
