Agentra LabsAgentra Labs DocsPublic Documentation

Operations

Operations: Autonomic + Backup

Safeguard runtime artifacts, MCP configs, and autonomic behaviors after installation.

Why this page matters

Install is step one. Reliability comes from artifact protection, configuration backup, and predictable operational defaults.

What you should protect

  • ~/.brain.amem (default AgenticMemory brain file)
  • MCP client configs (for example ~/.claude/mcp.json when present)
  • Runtime artifacts you generate (.avis, .acb) in your workspace paths
  • Runtime logs/health snapshots when enabled

Fast backup workflow (macOS/Linux)

1

Create backup folders

Prepare backup directories

Keeps runtime and config backups separated by purpose.

mkdir -p "$HOME/.agentra-backups/memory"
mkdir -p "$HOME/.agentra-backups/mcp"
mkdir -p "$HOME/.agentra-backups/artifacts"
2

Backup the memory brain file

Backup ~/.brain.amem

Timestamped backup file for safe rollback and migration.

cp "$HOME/.brain.amem" "$HOME/.agentra-backups/memory/brain-$(date +%F-%H%M%S).amem"
3

Backup MCP config

Backup Claude MCP config (if present)

Use the same pattern for other MCP client config files you discover.

if [ -f "$HOME/.claude/mcp.json" ]; then
cp "$HOME/.claude/mcp.json" "$HOME/.agentra-backups/mcp/claude-mcp-$(date +%F-%H%M%S).json"
fi
4

Backup workspace artifacts

Backup .avis and .acb outputs

Adjust path to where your project writes runtime artifacts.

find "$PWD" -type f ( -name "*.avis" -o -name "*.acb" ) -maxdepth 4 -print0 | xargs -0 -I {} cp "{}" "$HOME/.agentra-backups/artifacts/"

Restore workflow

Restore memory brain

Stop active clients first, then restore the selected backup.

cp "$HOME/.agentra-backups/memory/<backup-file>.amem" "$HOME/.brain.amem"

Restore MCP config

Restore your chosen MCP config backup and restart the desktop client.

cp "$HOME/.agentra-backups/mcp/<backup-file>.json" "$HOME/.claude/mcp.json"
Verification after restore

Run a binary check and one MCP tool call to confirm runtime state is healthy after restore.

Discover MCP files after install

If you are unsure where client MCP config lives, scan common locations:

Find likely MCP config files

Searches common home/config paths for MCP and desktop config names.

find "$HOME" -maxdepth 5 ( -name "*mcp*.json" -o -name "claude_desktop_config.json" -o -name "settings.json" ) 2>/dev/null | head -n 80

Find Agentra MCP entries in configs

Quickly identify files already containing Agentra runtime entries.

rg -n "agentic-memory|agentic-vision|acb-mcp|agentra" "$HOME/.claude" "$HOME/.config" "$HOME/Library/Application Support" 2>/dev/null

Autonomic and backup controls (Codebase runtime)

These environment variables are available for codebase operational posture:

  • ACB_AUTONOMIC_PROFILE (desktop, cloud, aggressive)
  • ACB_STORAGE_MIGRATION_POLICY (auto-safe, strict, off)
  • ACB_AUTO_BACKUP
  • ACB_AUTO_BACKUP_RETENTION
  • ACB_AUTO_BACKUP_DIR
  • ACB_COLLECTIVE_CACHE_MAINTENANCE_SECS
  • ACB_HEALTH_LEDGER_DIR (or AGENTRA_HEALTH_LEDGER_DIR)
  • ACB_HEALTH_LEDGER_EMIT_SECS
  • ACB_SLA_MAX_REGISTRY_OPS_PER_MIN

Default health ledger location:

  • ~/.agentra/health-ledger
Operational guardrail

Treat backup directories as sensitive: they may contain memory context, runtime artifacts, and configuration details. Use encrypted storage for long-term retention.