Skip to content

bug: orchestrator.py calls non-existent LLMInterface.initialize() #3974

Description

@mrveiss

Problem

Orchestrator tries to call self.llm_interface.initialize() on lines 412 and 1145, but LLMInterface class doesn't have an async initialize() method.

Root Cause

  • LLMInterface initialization happens completely in init() via helper methods like _init_configuration(), _init_hardware_detector(), etc.
  • No separate async initialize() method exists
  • Orchestrator falsely expects one (lines 412, 1145)

Impact

  • Orchestrator initialization fails (non-fatal error)
  • All backend workers show: "'LLMInterface' object has no attribute 'initialize'"
  • Creates repeated startup warnings but doesn't fully break the service

Fix

Remove the calls to self.llm_interface.initialize() since LLMInterface is already initialized in init

Files to Fix

  • autobot-backend/orchestrator.py line 412 (remove from asyncio.gather)
  • autobot-backend/orchestrator.py line 1145 (remove reinit call)

Activity

  1. self-assigned this
    on Apr 8, 2026
  2. mrveiss commented on Apr 8, 2026

    @mrveiss
    OwnerAuthor

    ✅ Issue already resolved. Verified: no LLMInterface.initialize() calls exist in codebase. Orchestrator correctly calls only memory_manager.initialize() and agent_manager.initialize(), with explicit comment noting LLMInterface init is not async-compatible. Merged in Dev_new_gui.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

backendbugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions