Managed agent
The provider stream is normalised at the backend boundary. Tool activity and long-running status stay inspectable without leaking provider-specific markup into the thread.
BlocksAssistant
Claude Managed Agents
How to wire long-running Claude Managed Agents tasks up to a thread. Authentication and persistence stay on your server, and what reaches the browser is the same normalised Assistant event stream every other provider uses, so the thread component doesn't need to know which one it is.
Adapter boundary
Framework adapters
Show code
const agent = createExternalStoreAssistant({ adapter: claudeManagedAgentsAdapter });
<Thread assistant={agent} />Show code
const agent = createExternalStoreAssistant({ adapter: claudeManagedAgentsAdapter });
<Thread :assistant="agent" />Show code
agent = createExternalStoreAssistant({ adapter: claudeManagedAgentsAdapter });
<grassroot-assistant-thread [assistant]="agent" />Show code
const agent = createExternalStoreAssistant({ adapter: claudeManagedAgentsAdapter });
<Thread assistant={agent} />Show code
const agent = createExternalStoreAssistant({ adapter: claudeManagedAgentsAdapter });
<Thread assistant={agent} />