Your AI. Your Hardware. Your Rules

Try on

Telegram response streaming is enabled by default ("streaming": "true"). Private chats use native rich drafts, while groups progressively edit a placeholder. Set "streaming": "false" to suppress previews; final responses still use rich Markdown with MarkdownV2 and plain-text fallbacks.

LocalAGI is a powerful, self-hostable AI Agent platform that allows you to design AI automations without writing code. Create Agents with a couple of clicks, connect via MCP, and use built-in Skills (manage skills in the Web UI and enable them per agent). Every agent exposes a complete drop-in replacement for OpenAI's Responses APIs with advanced agentic capabilities. No clouds. No data leaks. Just pure local AI that works on consumer-grade hardware (CPU and GPU). Skills follow the skillserver format and can be created, imported, or synced from git.

🛡️ Take Back Your Privacy

Are you tired of AI wrappers calling out to cloud APIs, risking your privacy? So were we.

LocalAGI ensures your data stays exactly where you want it—on your hardware. No API keys, no cloud subscriptions, no compromise.

🌟 Key Features

• 🎛 No-Code Agents: Easy-to-configure multiple agents via Web UI.
• 🖥 Web-Based Interface: Simple and intuitive agent management.
• 🤖 Advanced Agent Teaming: Instantly create cooperative agent teams from a single prompt.
• 📡 Connectors: Built-in integrations with Discord, Slack, Telegram, GitHub Issues, and IRC.
• 🛠 Comprehensive REST API: Seamless integration into your workflows. Every agent created will support OpenAI Responses API out of the box.
• 📚 Short & Long-Term Memory: Built-in knowledge base (RAG) for collections, file uploads, and semantic search. Manage collections in the Web UI under Knowledge base; agents with "Knowledge base" enabled use it automatically (implementation uses LocalRecall libraries).
• 🧠 Planning & Reasoning: Agents intelligently plan, reason, and adapt.
• 🔄 Periodic Tasks: Schedule tasks with cron-like syntax.
• 💾 Memory Management: Control memory usage with options for long-term and summary memory.
• 🖼 Multimodal Support: Ready for vision, text, and more.
• 🔧 Extensible Custom Actions: Easily script dynamic agent behaviors in Go (interpreted, no compilation!).
• 📚 Built-in Skills: Manage reusable agent skills in the Web UI (create, edit, import/export, git sync). Enable "Skills" per agent to inject skill tools and the skill list into the agent.
• 🛠 Fully Customizable Models: Use your own models or integrate seamlessly with LocalAI.
• 📊 Observability: Monitor agent status and view detailed observable updates in real-time.

🛠️ Quickstart

# Clone the repository
git clone https://github.com/mudler/LocalAGI
cd LocalAGI
CPU setup (default)
docker compose up
NVIDIA GPU setup
docker compose -f docker-compose.nvidia.yaml up
Intel GPU setup (for Intel Arc and integrated GPUs)
docker compose -f docker-compose.intel.yaml up
AMD GPU setup
docker compose -f docker-compose.amd.yaml up
Start with a specific model (see available models in models.localai.io, or localai.io to use any model in huggingface)
MODEL_NAME=gemma-3-12b-it docker compose up
NVIDIA GPU setup with custom multimodal and image models
MODEL_NAME=gemma-3-12b-it \
MULTIMODAL_MODEL=moondream2-20250414 \
IMAGE_MODEL=flux.1-dev-ggml \
docker compose -f docker-compose.nvidia.yaml up

Now you can access and manage your agents at http://localhost:8080

Still having issues? see this Youtube video: https://youtu.be/HtVwIxW3ePg

Videos

📚🆕 Local Stack Family

🆕 LocalAI is now part of a comprehensive suite of AI tools designed to work together:

	LocalAI LocalAI is the free, Open Source OpenAI alternative. LocalAI act as a drop-in replacement REST API that's compatible with OpenAI API specifications for local AI inferencing. Does not require GPU.
	LocalRecall A REST-ful API and knowledge base management system. LocalAGI embeds this functionality: the Web UI includes a Knowledge base section and the same collections API, so you no longer need to run LocalRecall separately.

🖥️ Hardware Configurations

LocalAGI supports multiple hardware configurations through Docker Compose profiles:

CPU (Default)

• No special configuration needed
• Runs on any system with Docker
• Best for testing and development
• Supports text models only

NVIDIA GPU

• Requires NVIDIA GPU and drivers
• Uses CUDA for acceleration
• Best for high-performance inference
• Supports text, multimodal, and image generation models
• Run with: docker compose -f docker-compose.nvidia.yaml up
• Default models:

- Text: gemma-3-4b-it-qat - Multimodal: moondream2-20250414 - Image: sd-1.5-ggml

• Environment variables:

- MODEL_NAME: Text model to use - MULTIMODAL_MODEL: Multimodal model to use - IMAGE_MODEL: Image generation model to use - LOCALAI_SINGLE_ACTIVE_BACKEND: Set to true to enable single active backend mode

Intel GPU

• Supports Intel Arc and integrated GPUs
• Uses SYCL for acceleration
• Best for Intel-based systems
• Supports text, multimodal, and image generation models
• Run with: docker compose -f docker-compose.intel.yaml up
• Default models:

- Text: gemma-3-4b-it-qat - Multimodal: moondream2-20250414 - Image: sd-1.5-ggml

• Environment variables:

- MODEL_NAME: Text model to use - MULTIMODAL_MODEL: Multimodal model to use - IMAGE_MODEL: Image generation model to use - LOCALAI_SINGLE_ACTIVE_BACKEND: Set to true to enable single active backend mode

Customize models

You can customize the models used by LocalAGI by setting environment variables when running docker-compose. For example:

# CPU with custom model
MODEL_NAME=gemma-3-12b-it docker compose up
NVIDIA GPU with custom models
MODEL_NAME=gemma-3-12b-it \
MULTIMODAL_MODEL=moondream2-20250414 \
IMAGE_MODEL=flux.1-dev-ggml \
docker compose -f docker-compose.nvidia.yaml up
Intel GPU with custom models
MODEL_NAME=gemma-3-12b-it \
MULTIMODAL_MODEL=moondream2-20250414 \
IMAGE_MODEL=sd-1.5-ggml \
docker compose -f docker-compose.intel.yaml up
With custom actions directory
LOCALAGI_CUSTOM_ACTIONS_DIR=/app/custom-actions docker compose up

If no models are specified, it will use the defaults:

• Text model: gemma-3-4b-it-qat
• Multimodal model: moondream2-20250414
• Image model: sd-1.5-ggml

Good (relatively small) models that have been tested are:

• qwen_qwq-32b (best in co-ordinating agents)
• gemma-3-12b-it
• gemma-3-27b-it

🏆 Why Choose LocalAGI?

• ✓ Ultimate Privacy: No data ever leaves your hardware.
• ✓ Flexible Model Integration: Supports GGUF, GGML, and more thanks to LocalAI.
• ✓ Developer-Friendly: Rich APIs and intuitive interfaces.
• ✓ Effortless Setup: Simple Docker compose setups and pre-built binaries.
• ✓ Feature-Rich: From planning to multimodal capabilities, connectors for Slack, MCP support, built-in Skills, LocalAGI has it all.

🌟 Screenshots

Powerful Web UI

!Web UI Dashboard !Web UI Agent Settings !Web UI Create Group !Web UI Agent Observability

Connectors Ready-to-Go

📖 Full Documentation

Explore detailed documentation including:

• Installation Options
• REST API Documentation
• Connector Configuration
• Agent Configuration
• Skills

Environment Configuration

LocalAGI supports environment configurations. Note that these environment variables needs to be specified in the localagi container in the docker-compose file to have effect.

| Variable | What It Does | |----------|--------------| | LOCALAGI_MODEL | Your go-to model | | LOCALAGI_MULTIMODAL_MODEL | Optional model for multimodal capabilities | | LOCALAGI_LLM_API_URL | OpenAI-compatible API server URL | | LOCALAGI_LLM_API_KEY | API authentication | | LOCALAGI_TIMEOUT | Request timeout settings | | LOCALAGI_STATE_DIR | Where state gets stored | | LOCALAGI_LOCALRAG_URL | Optional URL when using an external LocalRAG URL; not used for built-in knowledge base | | LOCALAGI_BASE_URL | Optional base URL for the app (defaults to ":3000") | | LOCALAGI_ENABLE_CONVERSATIONS_LOGGING | Toggle conversation logs | | LOCALAGI_API_KEYS | A comma separated list of api keys used for authentication | | LOCALAGI_CUSTOM_ACTIONS_DIR | Directory containing custom Go action files to be automatically loaded |

For the built-in knowledge base, optional env (defaults use LOCALAGI_STATE_DIR): COLLECTION_DB_PATH, FILE_ASSETS, VECTOR_ENGINE (e.g. chromem, postgres), EMBEDDING_MODEL, DATABASE_URL (when VECTOR_ENGINE=postgres).

Skills are stored in a fixed skills subdirectory under LOCALAGI_STATE_DIR (e.g. /pool/skills in Docker). Git repo config for skills lives in that directory. No extra environment variables are required.

Installation Options

Pre-Built Binaries

Download ready-to-run binaries from the Releases page.

Source Build

Requirements:

• Go 1.20+
• Git
• Bun 1.2+

# Clone repo
git clone https://github.com/mudler/LocalAGI.git
cd LocalAGI

Build it
cd webui/react-ui && bun i && bun run build
cd ../..
go build -o localagi
Run it
./localagi

Using as a Library

LocalAGI can be used as a Go library to programmatically create and manage AI agents. Let's start with a simple example of creating a single agent:

import (
    "github.com/mudler/LocalAGI/core/agent"
    "github.com/mudler/LocalAGI/core/types"
)
// Create a new agent with basic configuration
agent, err := agent.New(
    agent.WithModel("gpt-4"),
    agent.WithLLMAPIURL("http://localhost:8080"),
    agent.WithLLMAPIKey("your-api-key"),
    agent.WithSystemPrompt("You are a helpful assistant."),
    agent.WithCharacter(agent.Character{
        Name: "my-agent",
    }),
    agent.WithActions(
        // Add your custom actions here
    ),
    agent.WithStateFile("./state/my-agent.state.json"),
    agent.WithCharacterFile("./state/my-agent.character.json"),
    agent.WithTimeout("10m"),
    agent.EnableKnowledgeBase(),
    agent.EnableReasoning(),
)
if err != nil {
    log.Fatal(err)
}
// Start the agent
go func() {
    if err := agent.Run(); err != nil {
        log.Printf("Agent stopped: %v", err)
    }
}()
// Stop the agent when done
agent.Stop()

import (
    "github.com/mudler/LocalAGI/core/state"
    "github.com/mudler/LocalAGI/core/types"
)
// Create a new agent pool (call pool.SetRAGProvider(...) for knowledge base; see main.go)
pool, err := state.NewAgentPool(
    "default-model",           // default model name
    "default-multimodal-model", // default multimodal model
    "transcription-model",     // default transcription model
    "en",                     // default transcription language
    "tts-model",              // default TTS model
    "http://localhost:8080",  // API URL
    "your-api-key",           // API key
    "./state",                // state directory
    func(config AgentConfig) func(ctx context.Context, pool AgentPool) []types.Action {
        // Define available actions for agents
        return func(ctx context.Context, pool *AgentPool) []types.Action {
            return []types.Action{
                // Add your custom actions here
            }
        }
    },
    func(config *AgentConfig) []Connector {
        // Define connectors for agents
        return []Connector{
            // Add your custom connectors here
        }
    },
    func(config *AgentConfig) []DynamicPrompt {
        // Define dynamic prompts for agents
        return []DynamicPrompt{
            // Add your custom prompts here
        }
    },
    func(config *AgentConfig) types.JobFilters {
        // Define job filters for agents
        return types.JobFilters{
            // Add your custom filters here
        }
    },
    "10m",  // timeout
    true,   // enable conversation logs
    nil,    // skills service (optional)
)
// Create a new agent in the pool
agentConfig := &AgentConfig{
    Name: "my-agent",
    Model: "gpt-4",
    SystemPrompt: "You are a helpful assistant.",
    EnableKnowledgeBase: true,
    EnableReasoning: true,
    // Add more configuration options as needed
}
err = pool.CreateAgent("my-agent", agentConfig)
// Start all agents
err = pool.StartAll()
// Get agent status
status := pool.GetStatusHistory("my-agent")
// Stop an agent
pool.Stop("my-agent")
// Remove an agent
err = pool.Remove("my-agent")

🔧 Extending LocalAGI

LocalAGI provides two powerful ways to extend its functionality with custom actions:

1. Custom Actions (Go Code)

LocalAGI supports custom actions written in Go that can be defined inline when creating an agent. These actions are interpreted at runtime, so no compilation is required.

Automatic Custom Actions Loading

You can also place custom Go action files in a directory and have LocalAGI automatically load them. Set the LOCALAGI_CUSTOM_ACTIONS_DIR environment variable to point to a directory containing your custom action files. Each .go file in this directory will be automatically loaded and made available to all agents.

Example setup:

# Set the environment variable
export LOCALAGI_CUSTOM_ACTIONS_DIR="/path/to/custom/actions"

Or in docker-compose.yaml
environment:
  - LOCALAGI_CUSTOM_ACTIONS_DIR=/app/custom-actions

Directory structure:

custom-actions/
├── weather_action.go
├── file_processor.go
└── database_query.go

Each file should contain the three required functions (Run, Definition, RequiredFields) as described below.

How Custom Actions Work

When creating a new Agent, in the action sections select the "custom" action, you can add the Golang code directly there.

Custom actions in LocalAGI require three main functions:

1. Run(config map[string]interface{}) (string, map[string]interface{}, error) - The main execution function
2. Definition() map[string][]string - Defines the action's parameters and their types
3. RequiredFields() []string - Specifies which parameters are required

Example: Weather Information Action

Here's a practical example of a custom action that fetches weather information:

import (
    "encoding/json"
    "fmt"
    "net/http"
    "io"
)
type WeatherParams struct {
    City    string json:"city"
    Country string json:"country"
}
type WeatherResponse struct {
    Main struct {
        Temp     float64 json:"temp"
        Humidity int     json:"humidity"
    } json:"main"
    Weather []struct {
        Description string json:"description"
    } json:"weather"
}
func Run(config map[string]interface{}) (string, map[string]interface{}, error) {
    // Parse parameters
    p := WeatherParams{}
    b, err := json.Marshal(config)
    if err != nil {
        return "", map[string]interface{}{}, err
    }
    if err := json.Unmarshal(b, &p); err != nil {
        return "", map[string]interface{}{}, err
    }
// Make API call to weather service
    url := fmt.Sprintf("http://api.openweathermap.org/data/2.5/weather?q=%s,%s&appid=YOUR_API_KEY&units=metric", p.City, p.Country)
    resp, err := http.Get(url)
    if err != nil {
        return "", map[string]interface{}{}, err
    }
    defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
    if err != nil {
        return "", map[string]interface{}{}, err
    }
var weather WeatherResponse
    if err := json.Unmarshal(body, &weather); err != nil {
        return "", map[string]interface{}{}, err
    }
// Format response
    result := fmt.Sprintf("Weather in %s, %s: %.1f°C, %s, Humidity: %d%%", 
        p.City, p.Country, weather.Main.Temp, weather.Weather[0].Description, weather.Main.Humidity)
return result, map[string]interface{}{}, nil
}
func Definition() map[string][]string {
    return map[string][]string{
        "city": []string{
            "string",
            "The city name to get weather for",
        },
        "country": []string{
            "string", 
            "The country code (e.g., US, UK, DE)",
        },
    }
}
func RequiredFields() []string {
    return []string{"city", "country"}
}

Example: File System Action

Here's another example that demonstrates file system operations:

import (
    "encoding/json"
    "fmt"
    "os"
    "path/filepath"
)
type FileParams struct {
    Path    string json:"path"
    Action  string json:"action"
    Content string json:"content,omitempty"
}
func Run(config map[string]interface{}) (string, map[string]interface{}, error) {
    p := FileParams{}
    b, err := json.Marshal(config)
    if err != nil {
        return "", map[string]interface{}{}, err
    }
    if err := json.Unmarshal(b, &p); err != nil {
        return "", map[string]interface{}{}, err
    }
switch p.Action {
    case "read":
        content, err := os.ReadFile(p.Path)
        if err != nil {
            return "", map[string]interface{}{}, err
        }
        return string(content), map[string]interface{}{}, nil
        
    case "write":
        err := os.WriteFile(p.Path, []byte(p.Content), 0644)
        if err != nil {
            return "", map[string]interface{}{}, err
        }
        return fmt.Sprintf("Successfully wrote to %s", p.Path), map[string]interface{}{}, nil
        
    case "list":
        files, err := os.ReadDir(p.Path)
        if err != nil {
            return "", map[string]interface{}{}, err
        }
        
        var fileList []string
        for _, file := range files {
            fileList = append(fileList, file.Name())
        }
        
        result, _ := json.Marshal(fileList)
        return string(result), map[string]interface{}{}, nil
        
    default:
        return "", map[string]interface{}{}, fmt.Errorf("unknown action: %s", p.Action)
    }
}
func Definition() map[string][]string {
    return map[string][]string{
        "path": []string{
            "string",
            "The file or directory path",
        },
        "action": []string{
            "string",
            "The action to perform: read, write, or list",
        },
        "content": []string{
            "string",
            "Content to write (required for write action)",
        },
    }
}
func RequiredFields() []string {
    return []string{"path", "action"}
}

Using Custom Actions in Agents

To use custom actions, add them to your agent configuration:

1. Via Web UI: In the agent creation form, add a "Custom" action and paste your Go code
2. Via API: Include the custom action in your agent configuration JSON
3. Via Library: Add the custom action to your agent's actions list

2. MCP (Model Context Protocol) Servers

LocalAGI supports both local and remote MCP servers, allowing you to extend functionality with external tools and services.

What is MCP?

The Model Context Protocol (MCP) is a standard for connecting AI applications to external data sources and tools. LocalAGI can connect to any MCP-compliant server to access additional capabilities.

Local MCP Servers

Local MCP servers run as processes that LocalAGI can spawn and communicate with via STDIO.

##### Example: GitHub MCP Server

{
  "mcpServers": {
    "github": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "ghcr.io/github/github-mcp-server"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Remote MCP Servers

Remote MCP servers are HTTP-based and can be accessed over the network.

Creating Your Own MCP Server

You can create MCP servers in any language that supports the MCP protocol and add the URLs of the servers to LocalAGI.

Configuring MCP Servers in LocalAGI

1. Via Web UI: In the MCP Settings section of agent creation, add MCP servers
2. Via API: Include MCP server configuration in your agent config

LocalAGI as an MCP Server

LocalAGI also works the other way around: it exposes its own MCP server so that MCP clients can manage agents. The endpoint is served at /mcp on the same address as the Web UI and the REST API:

http://localhost:3000/mcp

It speaks Streamable HTTP and is protected by the same API keys as the rest of the API, so clients authenticate with Authorization: Bearer when LOCALAGI_API_KEYS is set.

Example client configuration:

{
  "mcpServers": {
    "localagi": {
      "type": "http",
      "url": "http://localhost:3000/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key"
      }
    }
  }
}

The following tools are available:

| Tool | Description | |------|-------------| | list_agents | List the configured agents, with their model and current state | | get_agent_config | Read the full configuration of an agent | | create_agent | Create a new agent and start it (only name is required) | | update_agent_config | Replace the configuration of an agent and restart it | | delete_agent | Delete an agent and its state | | pause_agent | Pause a running agent | | start_agent | Resume a paused agent | | get_agent_config_schema | Describe the configuration fields, and the connectors, actions, dynamic prompts and filters available on this instance |

create_agent and update_agent_config accept the same configuration as the REST API. Call get_agent_config_schema first to discover which connectors, actions and filters the instance provides, and what each one expects.

Best Practices

• Security: Always validate inputs and use proper authentication for remote MCP servers
• Error Handling: Implement robust error handling in your MCP servers
• Documentation: Provide clear descriptions for all tools exposed by your MCP server
• Testing: Test your MCP servers independently before integrating with LocalAGI
• Resource Management: Ensure your MCP servers properly clean up resources

3. Skills

LocalAGI includes built-in Skills management. Skills are reusable instructions and resources (scripts, references, assets) that agents can use when "Enable Skills" is turned on for that agent.

• Skills section (Web UI): Open Skills in the sidebar. Skills are stored under the state directory (STATE_DIR/skills). Create, edit, search, import, and export skills. You can also add git repositories to sync skills from.
• Per-agent: In agent creation or settings, enable Enable Skills in Advanced Settings. The agent will receive a list of available skills in its context and have access to skill tools (list, read, search, resources) via the built-in skills MCP.
• Skills use the same format as skillserver (e.g. SKILL.md in a directory). You can export skills from LocalAGI and use them with the standalone skillserver, or import skills created elsewhere.

Development

The development workflow is similar to the source build, but with additional steps for hot reloading of the frontend:

# Clone repo
git clone https://github.com/mudler/LocalAGI.git
cd LocalAGI
cd webui/react-ui
Install dependencies
bun i
Compile frontend (the build directory needs to exist for the backend to start)
bun run build
Start frontend development server
bun run dev

Then in separate terminal:

cd LocalAGI
Create a "pool" directory for agent state
mkdir pool
Set required environment variables
export LOCALAGI_MODEL=gemma-3-4b-it-qat
export LOCALAGI_MULTIMODAL_MODEL=moondream2-20250414
export LOCALAGI_IMAGE_MODEL=sd-1.5-ggml
export LOCALAGI_LLM_API_URL=http://localai:8080
Knowledge base is built-in; no separate LocalRecall service needed
export LOCALAGI_STATE_DIR=./pool
export LOCALAGI_TIMEOUT=5m
export LOCALAGI_ENABLE_CONVERSATIONS_LOGGING=false
export LOCALAGI_SSHBOX_URL=root:root@sshbox:22
Start development server
go run main.go

Note: see webui/react-ui/.vite.config.js for env vars that can be used to configure the backend URL

CONNECTORS

Link your agents to the services you already use. Configuration examples below.

{
  "token": "YOUR_PAT_TOKEN",
  "repository": "repo-to-monitor",
  "owner": "repo-owner",
  "botUserName": "bot-username"
}

{
  "token": "Bot YOUR_DISCORD_TOKEN",
  "defaultChannel": "OPTIONAL_CHANNEL_ID"
}

{
  "botToken": "xoxb-your-bot-token",
  "appToken": "xapp-your-app-token"
}

{ 
  "token": "your-bot-father-token",
  "group_mode": "true",
  "mention_only": "true",
  "admins": "username1,username2"
}

{
  "server": "irc.example.com",
  "port": "6667",
  "nickname": "LocalAGIBot",
  "channel": "#yourchannel",
  "alwaysReply": "false"
}

{
  "smtpServer": "smtp.gmail.com:587",
  "imapServer": "imap.gmail.com:993",
  "smtpInsecure": "false",
  "imapInsecure": "false",
  "username": "[email protected]",
  "email": "[email protected]",
  "password": "correct-horse-battery-staple",
  "name": "LogalAGI Agent"
}

REST API

curl -X GET "http://localhost:3000/api/agents"

curl -X GET "http://localhost:3000/api/agent/my-agent/status"

curl -X POST "http://localhost:3000/api/agent/create" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-agent",
    "model": "gpt-4",
    "system_prompt": "You are an AI assistant.",
    "enable_kb": true,
    "enable_reasoning": true
  }'

curl -X DELETE "http://localhost:3000/api/agent/my-agent"

curl -X PUT "http://localhost:3000/api/agent/my-agent/pause"

curl -X PUT "http://localhost:3000/api/agent/my-agent/start"

curl -X GET "http://localhost:3000/api/agent/my-agent/config"

curl -X PUT "http://localhost:3000/api/agent/my-agent/config" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4",
    "system_prompt": "You are an AI assistant."
  }'

curl -X GET "http://localhost:3000/settings/export/my-agent" --output my-agent.json

curl -X POST "http://localhost:3000/settings/import" \
  -F "file=@/path/to/my-agent.json"

curl -X POST "http://localhost:3000/api/chat/my-agent" \
  -H "Content-Type: application/json" \
  -d '{"message": "Hello, how are you today?"}'

curl -X POST "http://localhost:3000/api/notify/my-agent" \
  -H "Content-Type: application/json" \
  -d '{"message": "Important notification"}'

curl -N -X GET "http://localhost:3000/api/sse/my-agent"

Agent Configuration Reference

curl -X GET "http://localhost:3000/api/meta/agent/config"

{
  "name": "my-agent",
  "model": "gpt-4",
  "multimodal_model": "gpt-4-vision",
  "hud": true,
  "standalone_job": false,
  "random_identity": false,
  "initiate_conversations": true,
  "enable_planning": true,
  "identity_guidance": "You are a helpful assistant.",
  "periodic_runs": "0    ",
  "permanent_goal": "Help users with their questions.",
  "enable_kb": true,
  "enable_reasoning": true,
  "kb_results": 5,
  "can_stop_itself": false,
  "system_prompt": "You are an AI assistant.",
  "long_term_memory": true,
  "summary_long_term_memory": false
}

LICENSE

MIT License — See the LICENSE file for details.

LOCAL PROCESSING. GLOBAL THINKING.
Made with ❤️ by mudler