m4Mindset docs
llms.txt

Mindset v3 / Build & Optimize / AMS SDK

View as Markdown

Decision Flow

Use this guide to determine which Agent Builder SDK components best fit your implementation needs.

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

Embed Builder Components

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

Embed Configuration Components

Agent Configuration
    <mindset-agent-configuration></mindset-agent-configuration>
Context 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

Question 2: Who provides the knowledge/context?

Tenants Upload Their Own Files

Approach: Embed Context Builder or Context Configuration components

When to use:

  • Tenants manage their own knowledge
  • Each tenant has unique content
  • Self-service model
You Provide Centrally

Approach: Create app-level contexts via API

When 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 contexts

When 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 sessions

When to use:

  • Using external RAG system
  • Custom vector database
  • Advanced knowledge retrieval

Component Comparison Matrix

<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

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

FeatureStatusDetails
Purpose✅ Standalone create/editFocused configuration interface
List View❌ Not includedYou build your own
Search & Filter❌ Not applicableYou build your own
Create✅ Standalone interfaceLaunch for creation
Edit✅ Standalone interfacePass agentUid/contextUid
Delete❌ Not includedYou implement this
Setup Complexity🟡 MediumBuild custom list view
Customization🟢 HighFull control over UI/UX

Common Implementation Patterns

Pattern 1: Full Self-Service (Most Common)

Use Case: Tenants fully manage their agents and knowledge

Components:

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

Setup:

html
    <mindset-agents-manager></mindset-agents-manager>
    <mindset-contexts-manager></mindset-contexts-manager>
Pattern 2: Centralized Knowledge

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

Components:

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

Setup:

html
    <mindset-agents-manager></mindset-agents-manager>
    <!-- No context builder needed -->
Pattern 3: Custom List UI

Use Case: You need branded list views with custom layouts

Components:

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

Setup:

javascript
    // Your custom list
    function openAgentEditor(agentUid) {
      container.innerHTML = `
        <mindset-agent-configuration 
          agentUid="${agentUid}">
        </mindset-agent-configuration>
      `;
    }
Pattern 4: Hybrid Knowledge Model

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

Components:

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

Setup:

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

Quick Reference Table

Your NeedsRecommended ComponentsComplexityCustomization
Complete admin interface, minimal setupBuilder Components🟢 Low🟡 Limited
Custom list view, SDK handles formsConfiguration Components🟡 Medium🟢 High
Tenants upload knowledgeInclude Context Builder/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