Decision Flow

Question 1: Do you want to use Mindset’s list view UI?

YES - Use Mindset's List View
NO - Build Your Own List View

Embed Builder Components

    <mindset-agents-manager></mindset-agents-manager>

    <mindset-contexts-manager></mindset-contexts-manager>

What You Get

Complete UI

Full list view with cards or table

Search & Filter

Built-in search and filtering capabilities

Edit & Delete

Integrated edit and delete actions

Create New

Built-in create functionality

Best for: Teams who want a complete out-of-box experience with minimal setup

Embed Configuration Components

    <mindset-agent-configuration></mindset-agent-configuration>

    <mindset-context-configuration></mindset-context-configuration>

What You Build vs What SDK Handles

You Build

Custom list view (tiles, cards, tables)
Your own search and filtering
Custom layout and styling
Delete confirmation flows

SDK Handles

Creating new resources
Editing existing resources
Form validation
Save and update logic

Best for: Teams who need full control over the list view presentation

Question 2: Who provides the knowledge/context?

Tenants Upload Their Own Files

Approach: Embed Context Builder or Context Configuration componentsWhen to use:

Tenants manage their own knowledge
Each tenant has unique content
Self-service model

You Provide Centrally

Approach: Create app-level contexts via APIWhen to use:

Centralized knowledge management
Consistent content across tenants
You control all knowledge sources

Mix of Both

Approach: Embed context components AND create app-level contextsWhen to use:

Base knowledge provided centrally
Tenants can add custom content
Hybrid knowledge model

Use RAG MCP Instead

Approach: No contexts needed, provision RAG MCP in agent sessionsWhen to use:

Using external RAG system
Custom vector database
Advanced knowledge retrieval

Component Comparison Matrix

Builder Components
Configuration Components

`<mindset-agents-manager>` & `<mindset-contexts-manager>`

Feature	Status	Details
Purpose	✅ Complete CRUD interface	Full-featured management UI
List View	✅ Included	Cards or table with pagination
Search & Filter	✅ Built-in	Instant search and filtering
Create	✅ Built-in dialogs	Modal-based creation flow
Edit	✅ Built-in dialogs	Modal-based editing flow
Delete	✅ Included	Confirmation dialog included
Setup Complexity	🟢 Low	Embed and initialize
Customization	🟡 Limited	Theme colors and fonts only

Best for: Standard admin interfaces with minimal customization needs

`<mindset-agent-configuration>` & `<mindset-context-configuration>`

Feature	Status	Details
Purpose	✅ Standalone create/edit	Focused configuration interface
List View	❌ Not included	You build your own
Search & Filter	❌ Not applicable	You build your own
Create	✅ Standalone interface	Launch for creation
Edit	✅ Standalone interface	Pass agentUid/contextUid
Delete	❌ Not included	You implement this
Setup Complexity	🟡 Medium	Build custom list view
Customization	🟢 High	Full control over UI/UX

Best for: Custom UI workflows where you control the list view presentation

Common Implementation Patterns

Pattern 1: Full Self-Service (Most Common)

Use Case: Tenants fully manage their agents and knowledgeComponents:

<mindset-agents-manager>
<mindset-contexts-manager>

Setup:

    <mindset-agents-manager></mindset-agents-manager>
    <mindset-contexts-manager></mindset-contexts-manager>

Zero configuration, complete functionality

Pattern 2: Centralized Knowledge

Use Case: You provide all knowledge, tenants just configure agentsComponents:

<mindset-agents-manager>
App-level contexts (created via API)

Setup:

    <mindset-agents-manager></mindset-agents-manager>
    <!-- No context builder needed -->

Simpler UI, centralized content control

Pattern 3: Custom List UI

Use Case: You need branded list views with custom layoutsComponents:

<mindset-agent-configuration>
<mindset-context-configuration>
Your custom list views

Setup:

    // Your custom list
    function openAgentEditor(agentUid) {
      container.innerHTML = `
        <mindset-agent-configuration 
          agentUid="${agentUid}">
        </mindset-agent-configuration>
      `;
    }

Maximum customization, more development

Pattern 4: Hybrid Knowledge Model

Use Case: Base knowledge from you, custom knowledge from tenantsComponents:

<mindset-agents-manager>
<mindset-contexts-manager>
App-level contexts (created via API)

Setup:

Create app-level contexts via API
Embed both builder components
Tenants see app contexts + can create their own

Flexibility for both centralized and custom content

Quick Reference Table

Your Needs	Recommended Components	Complexity	Customization
Complete admin interface, minimal setup	Builder Components	🟢 Low	🟡 Limited
Custom list view, SDK handles forms	Configuration Components	🟡 Medium	🟢 High
Tenants upload knowledge	Include Context Builder/Configuration	🟢 Low	🟡 Medium
You provide all knowledge	Agents only + API contexts	🟢 Low	🟡 Medium
Mix of both approaches	All components + API contexts	🟡 Medium	🟢 High
Using external RAG	Agents only + RAG MCP	🟡 Medium	🟢 High

Overview

Agent Management Studio

Plans and Skills

Widget Studio

Agents

AMS SDK

Prompts

Knowledge

Threads

Question 1: Do you want to use Mindset’s list view UI?

Embed Builder Components

What You Get

Complete UI

Search & Filter

Edit & Delete

Create New

Embed Configuration Components

What You Build vs What SDK Handles

Question 2: Who provides the knowledge/context?

Tenants Upload Their Own Files

You Provide Centrally

Mix of Both

Use RAG MCP Instead

Component Comparison Matrix

`<mindset-agents-manager>` & `<mindset-contexts-manager>`

`<mindset-agent-configuration>` & `<mindset-context-configuration>`

Common Implementation Patterns

Quick Reference Table

​Question 1: Do you want to use Mindset’s list view UI?

​Embed Builder Components

​What You Get

Complete UI

Search & Filter

Edit & Delete

Create New

​Embed Configuration Components

​What You Build vs What SDK Handles

​Question 2: Who provides the knowledge/context?

Tenants Upload Their Own Files

You Provide Centrally

Mix of Both

Use RAG MCP Instead

​Component Comparison Matrix

​<mindset-agents-manager> & <mindset-contexts-manager>

​<mindset-agent-configuration> & <mindset-context-configuration>

​Common Implementation Patterns

​Quick Reference Table

Question 1: Do you want to use Mindset’s list view UI?

Embed Builder Components

What You Get

Embed Configuration Components

What You Build vs What SDK Handles

Question 2: Who provides the knowledge/context?

Component Comparison Matrix

`<mindset-agents-manager>` & `<mindset-contexts-manager>`

`<mindset-agent-configuration>` & `<mindset-context-configuration>`

Common Implementation Patterns

Quick Reference Table