Skip to main content

​
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 Manager Components

<mindset-agents-manager></mindset-agents-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

​
Question 2: Who provides the knowledge/context?

Tenants Upload Their Own Files

Approach: Embed Context Manager 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

  • Manager Components
  • Configuration Components

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

FeatureStatusDetails
Purpose✅ Complete CRUD interfaceFull-featured management UI
List View✅ IncludedCards or table with pagination
Search & Filter✅ Built-inInstant search and filtering
Create✅ Built-in dialogsModal-based creation flow
Edit✅ Built-in dialogsModal-based editing flow
Delete✅ IncludedConfirmation dialog included
Setup Complexity🟢 LowEmbed and initialize
Customization🟡 LimitedTheme colors and fonts only
Best for: Standard admin interfaces with minimal customization needs

​
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
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 manager needed -->
Simpler UI, centralized content control
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
Use Case: Base knowledge from you, custom knowledge from tenantsComponents:
  • <mindset-agents-manager>
  • <mindset-contexts-manager>
  • App-level contexts (created via API)
Setup:
  1. Create app-level contexts via API
  2. Embed both manager components
  3. Tenants see app contexts + can create their own
Flexibility for both centralized and custom content

​
Quick Reference Table

Your NeedsRecommended ComponentsComplexityCustomization
Complete admin interface, minimal setupManager Components🟢 Low🟡 Limited
Custom list view, SDK handles formsConfiguration Components🟡 Medium🟢 High
Tenants upload knowledgeInclude Context Manager/Configuration🟢 Low🟡 Medium
You provide all knowledgeAgents only + API contexts🟢 Low🟡 Medium
Mix of both approachesAll components + API contexts🟡 Medium🟢 High
Using external RAGAgents only + RAG MCP🟡 Medium🟢 High