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 (Pay-per-use)Anthropic API bridge settings (incurs charges)

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

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

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\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.

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)

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.