Skip to content

Troubleshooting

Aleksandr Artamokhov edited this page Jun 26, 2026 · 1 revision

Troubleshooting

argus: command not found

  • Re-run installer or npm link from a local clone
  • Use node dist/index.js instead of argus during dev

doctor shows no providers

Add keys to .env or start Ollama:

ollama serve
ARGUS_LOCAL_BASE_URL=http://127.0.0.1:11434/v1 argus doctor

Economy stays OFF

Expected without wallet. To enable: ARGUS_CRYPTO_ENABLED=1 + ARGUS_WALLET_KEY in .env. Restart. See Economy.

BudgetExceededError

Task exceeded Token-Budget. Narrow the ask or raise limits in argus.config.json (know the cost).

WARDEN BLOCK on MCP

argus warden scan

Common causes: low LUMEN reputation, static-scan hit, tool-def drift. See WARDEN.

Telegram: "not owner"

Another user claimed the bot first. Set ARGUS_TELEGRAM_OWNER_ID to your numeric id or reset bot state per repo docs.

HTTP 401 on /ask

Send Authorization: Bearer $ARGUS_HTTP_TOKEN. Token must match .env.

MCP client can't connect

Run argus mcp — stdio only. Point Claude Desktop / Cursor MCP config at the binary + args from channels.md.

High latency / cost

  • Move triage to local tier
  • Lower maxSteps / maxUsdPerTask
  • Enable Anthropic cache_control (automatic on anthropic provider)

Install script fails

curl -fsSL https://magic-ai-factory.com/install | bash -x

Check Node 20+, network, and write permissions. Fallback: Install#Manual install.


Still stuck?

  1. argus doctor output
  2. Relevant log (argus-telegram.log if Telegram)
  3. Open an issue with redacted config

Related

Clone this wiki locally