Issue Report: Agent Zero (AgentX) - Persistent Cloud Dependency in Docker / Agent Zero = doch ein Nepp bezüglich lokaler Cloud?

Title: [Bug/Design Flaw] Strict Offline Mode Impossible: Cloud Defaults Override Local Docker Config

System Environment:

OS: Ubuntu Server
Hardware: 128 GB RAM | RTX GPU
Backend: Local Ollama instance (no external API keys)
Deployment: Docker / Docker Compose

Description: Despite the project claiming to support local execution, I am unable to run the agent in a strictly offline environment (air-gapped/local network only). The system appears to prioritize hardcoded cloud defaults (OpenRouter/LiteLLM) over the local configuration provided in docker-compose.yml.

Technical Findings:

Configuration Precedence: It seems the internal SQLite database state overrides environment variables defined in docker-compose.yml. Even after changing providers to ollama, the system attempts to fetch legacy cloud paths.
Hardcoded "Memory" Dependency: The "Recall Memories" module seems to have hardcoded dependencies on external providers. The agent attempts to load this module before checking the offline status, resulting in a crash loop when no internet connection is available.
Error Handling: We cannot instruct the agent to disable these features via chat because the crash occurs during the initialization/pre-flight check of the intelligence module.

Steps Taken to Resolve (All Failed):

Set CHAT_MODEL_PROVIDER=ollama in environment variables.
Performed a full database purge (rm -rf /data/db).
Reset Docker volumes (docker-compose down -v) to force a clean slate.
Attempted to force MEMORY_AUTO_RECALL=false.

Conclusion: The current architecture forces external API calls and does not respect a purely local configuration. Is there a documented way to completely strip the "Memory" module's external dependencies for a 100% offline Docker deployment?

0 comments

Agent Zero

skool.com/agent-zero

Agent Zero AI framework

Leaderboard (30-day)

+47

+38

+26

+22

+16