Configuration

AgentUX is configured through two interfaces: the Settings panel in Project Settings for UE-native properties, and the Config Files tab for editing YAML and Markdown configuration files directly.

On This Page


Settings Panel

Open Project Settings > Plugins > AgentUX to configure the plugin. Settings are organized into categories:

CategoryWhat It Controls
ServerWebSocket port, enable/disable
SecurityAuthentication, rate limits, batch size
GraphRAGConfig paths, Neo4j connection, ONNX model
ChatClaude CLI path, model, context budget
Chat > IdentitySystem prompt, home directory, additional dirs
Chat > MCP ServersAdditional MCP server config files
Chat > PermissionsAuto-approve MCP tools, allowed tool patterns
Bridge-v2 (API bridge)Anthropic API bridge for programmatic access without the CLI. Requires API key (pay-per-use). Most users skip this.
AgentUX Settings panel showing Connection Status, Server, GraphRAG, and Chat sections
The Settings panel top half shows Connection Status, Server, GraphRAG, and Chat sections. The Connection Status section displays live server state and GraphRAG node counts.
AgentUX Settings panel showing Chat Identity, Bridge, Security, and Knowledge Base sections
The Settings panel bottom half covers Chat Identity (system prompt, home directory), Bridge-v2 (API bridge for programmatic access), Security (auth, rate limits), and Knowledge Base (download and license).

Hover for help

Every setting has a tooltip. Hover over any property name to see a description, default value, and relevant security notes.

Path validation

File and directory path settings show a validation indicator below the field:

  • Green checkmark with Found: D:\full\path\to\file -- file exists at the resolved path
  • Yellow warning -- wrong file type or extension
  • Red X with Not found: D:\full\path\to\file -- file does not exist

The resolved absolute path is shown so you can easily locate the file in your file manager or external editor.

Browse buttons

All file and directory path properties include a browse button (...) that opens a system file/folder picker dialog.


Config Files Tab

Open Window > Tools > AgentUX > Config Files (or use the keyboard shortcut) to access the built-in configuration file editor.

Layout

  • Left panel: Tree view of discoverable configuration files, organized by category
  • Right panel: Text editor with line numbers for the selected file
  • Path bar: Shows the full absolute path to the selected file above the editor
Config Files editor showing file tree and empty editor panel
The Config Files editor. The file tree on the left organizes files by category. Click any file to open it in the editor on the right.

File categories

CategoryFilesEditable
Project Files.claude/CLAUDE.md, Bridge CLAUDE.mdYes
Bridge Memory Files*.md files in Memory DirectoryYes
GraphRAG TemplatesGraphRAG CLAUDE.mdYes
GraphRAG Configurationconfig.yamlYes
ReferenceAPI docs, handler summary, recipesRead-only

Editing workflow

  1. Click a file in the tree to load it
  2. Edit the content in the text editor
  3. Press Ctrl+S or click Save to write changes to disk
  4. The tab title shows an asterisk (*) when there are unsaved changes
Config Files tab title showing asterisk for unsaved changes
The tab title shows an asterisk (*) when there are unsaved changes. The Save and Restore Defaults buttons appear in the toolbar.
CLAUDE.md template loaded in the Config Files editor
The GraphRAG CLAUDE.md template loaded in the editor. This file teaches Claude how to use the UE-GraphRAG tools for API verification.

Read-only files (like API reference docs) open in view mode -- the save button is disabled and the path bar shows (read-only).

Locating files on disk

The path bar above the editor always shows the full absolute path to the currently selected file (e.g., D:\apps\Epic Games\UE_5.7\Engine\Plugins\Experimental\AgentUX\GraphRAG\config.yaml). You can select and copy this path to open the file in any external editor of your choice.


GraphRAG YAML Reference

The config.yaml file controls GraphRAG's Neo4j connection, embedding model, vector store, and query limits. Edit it in the Config Files tab or with any text editor at the path shown in the path bar.

config.yaml file open in the Config Files editor showing GraphRAG settings
The config.yaml file with all GraphRAG settings: Neo4j connection, ONNX embedding model, LanceDB vector store, and query limits.

Key sections

SectionKey SettingsNotes
neo4j uri, user, password, domain_label Password resolution: OS keyring → config file → NEO4J_PASSWORD env var
onnx model_path, tokenizer_path, dimensions ONNX embedding model for semantic search
lancedb path Vector index data directory
limits max_results Global cap on all MCP tool result counts (default: 500)
embedder embedding_instruction Instruction prefix for query embeddings

Password security

The Neo4j password is resolved in this order:

  1. OS keyring (recommended): pip install keyring, then store with:
    python -c "import keyring; keyring.set_password('graphrag-neo4j', 'neo4j', 'YOUR_PASSWORD')"
  2. config.yaml: neo4j.password field (less secure -- file should be in .gitignore)
  3. Environment variable: NEO4J_PASSWORD (for CI/containers)

TLS encryption

For encrypted Neo4j connections, change the URI scheme from bolt:// to bolt+s:// in config.yaml. This requires TLS to be configured on your Neo4j server.


Restoring Defaults

If you make a mistake or want to start fresh, the Restore Defaults button in the Config Files tab resets the selected file to its shipped default template.

How it works

  1. Select the file you want to restore (e.g., config.yaml)
  2. Click Restore Defaults in the toolbar
  3. A warning dialog appears showing:
    • The file being overwritten
    • The source template (e.g., config.dist.yaml)
    • The timestamped backup filename
  4. Click Yes to proceed
  5. Your current file is backed up (e.g., config.yaml.20260316-104500.bak)
  6. The default template replaces your file
  7. The editor reloads with the default content

Backups

Every restore creates a timestamped backup in the same directory as the original file. Multiple restores create multiple backups -- previous backups are never overwritten. To recover your settings, rename the backup file back to the original name.

When Restore Defaults is available

The button is enabled only when:

  • An editable file is selected (not read-only)
  • A default template exists for that file (e.g., config.dist.yaml for config.yaml)

History Tab

The History tab stores every chat session with full message history in a local SQLite database. Open it from Tools > AgentUX > History.

History tab showing past chat sessions with timestamps
Past chat sessions listed with timestamps and message counts. Click any session to review the full conversation.

Conversation Tabs

The Chat panel supports multiple concurrent conversations via a tab bar at the top of the window:

  • Click the + button to start a new conversation.
  • Click any tab to switch between open conversations.
  • Right-click a tab to rename it.
  • Up to 3 recent sessions load automatically when the editor starts, so you can resume where you left off.

Each tab maps to a database session. Messages persist across editor restarts.

Search

The search box in the toolbar uses full-text search to find messages across all sessions. Type a keyword and results update after a brief debounce. Search results intersect with any active role or date filters.

Filtering

Two dropdown filters narrow the session list:

History role filter dropdown showing user, assistant, system, tool_use, and tool_result options
Filter by role to isolate user messages, assistant responses, system messages, or tool calls.
History time filter dropdown showing last 7, 30, 60, and 90 day options
Filter by time range: last 7, 30, 60, or 90 days.

Managing History

The Clear History button provides four cleanup options:

  • Clear Selected Session deletes the currently highlighted session.
  • Clear Older Than removes sessions older than 7, 30, 60, or 90 days.
  • Clear All Except Current keeps only the active conversation.
  • Clear Entire History permanently deletes all sessions and messages.

All deletions require a confirmation dialog. Deleted data cannot be recovered.

Clear History dropdown showing Clear Older Than, Clear All Except Current, and Clear Entire History
Clear old sessions, keep only the current conversation, or wipe everything.

Storage

History is stored at [ProjectDir]/Saved/AgentUX/chat_history.db. The database uses SQLite with WAL mode for concurrent reads during streaming.


Model Selector

The Chat window includes a model selector dropdown in the top-right corner. Switch between Claude models without leaving the editor.

Model selector dropdown showing Claude Sonnet 4.6, Opus 4.6, Haiku 4.5, and older models
The model selector lists all available Claude models with context window sizes. The default model is set in Settings.

Settings Quick Reference

Server

SettingDefaultDescription
Port9877WebSocket server port
EnabledOnStart WebSocket server on editor launch

Security

SettingDefaultDescription
Require AuthenticationOnEnforce auth token on all connections
Max Requests Per Second100Per-connection rate limit (10-1000)
Max Batch Size50Max JSON-RPC batch array elements (1-500)

GraphRAG

SettingDefaultDescription
GraphRAG Config(auto-detect)Path to config.yaml
ONNX Model Path(auto-detect)Embedding model file
Neo4j URIbolt://localhost:7687Scheme + host + port
Neo4j Userneo4jDatabase username

Chat

SettingDefaultDescription
Claude CLI Path(auto-detect)Path to Claude Code executable
Auto-inject ContextOnInclude editor state in chat messages
Context Token Budget500Max tokens for context injection (100-2000)
Permission ModeDefaultRequire approval for tool use
Auto-approve MCP ToolsOnAllow Claude to use MCP tools without asking

For the complete list of settings with detailed descriptions, hover over each setting in the editor or see the Security page for security-specific settings.