Agentra LabsAgentra Labs DocsPublic Documentation

Operations

Troubleshooting Matrix

Diagnose installation, MCP connection, and runtime startup issues quickly.

Quick diagnostic pass

1

Verify binaries are installed

Binary checks

Confirms your shell can resolve all expected binaries.

which amem
which agentic-memory-mcp
which agentic-vision-mcp
which acb
which acb-mcp
2

Check runtime command responses

Entry-point checks

Each command should return usage/help without crashing.

amem --version
agentic-memory-mcp --help
agentic-vision-mcp serve --help
acb-mcp serve --help
3

Inspect MCP config references

Config inspection

Look for command paths and stale binary references.

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

Symptom matrix

SymptomLikely causeFix
curl .../install/<target> | bash returns 404install route not deployed or wrong domainverify https://agentralabs.tech/install/<target> in browser and redeploy web if needed
installer falls back to source unexpectedlyrelease artifact unavailable for platformcontinue fallback build, then validate binary path
command not found after successful installbinary dir not in PATHadd runtime bin dir to shell profile and restart terminal
MCP client cannot start serverconfig points to old pathupdate config to actual path from which <binary>
tools not visible in desktop clientclient not restarted after mergerestart the desktop client completely

Escalation bundle

When reporting issues, include:

  • OS + architecture
  • exact install command used
  • full terminal output
  • client name (Claude Desktop, Codex Desktop, Cursor, etc.)
  • output of which and --version commands
Fastest recovery pattern

If behavior is inconsistent, back up config, reinstall using hosted installer, re-run path checks, then restart client.