IronEngine: Towards General AI Assistant

TL;DR

The platform's architectural decomposition, subsystem design, experimental performance, safety boundaries, and comparative engineering advantages are analyzed, and the resulting study positions IronEngine as a system-oriented foundation for general-purpose personal assistants, automation frameworks, and future human-centered agent platforms.

Abstract

This paper presents IronEngine, a general AI assistant platform organized around a unified orchestration core that connects a desktop user interface, REST and WebSocket APIs, Python clients, local and cloud model backends, persistent memory, task scheduling, reusable skills, 24-category tool execution, MCP-compatible extensibility, and hardware-facing integration. IronEngine introduces a three-phase pipeline -- Discussion (Planner--Reviewer collaboration), Model Switch (VRAM-aware transition), and Execution (tool-augmented action loop) -- that separates planning quality from execution capability. The system features a hierarchical memory architecture with multi-level consolidation, a vectorized skill repository backed by ChromaDB, an adaptive model management layer supporting 92 model profiles with VRAM-aware context budgeting, and an intelligent tool routing system with 130+ alias normalization and automatic error correction. We present experimental results on file operation benchmarks achieving 100\% task completion with a mean total time of 1541 seconds across four heterogeneous tasks, and provide detailed comparisons with representative AI assistant systems including ChatGPT, Claude Desktop, Cursor, Windsurf, and open-source agent frameworks. Without disclosing proprietary prompts or core algorithms, this paper analyzes the platform's architectural decomposition, subsystem design, experimental performance, safety boundaries, and comparative engineering advantages. The resulting study positions IronEngine as a system-oriented foundation for general-purpose personal assistants, automation frameworks, and future human-centered agent platforms.

Figures (9)

• Figure 1: Simplified trajectory of AI agent research and product evolution relevant to IronEngine. Blue nodes indicate research milestones; orange nodes indicate product-oriented systems.
• Figure 2: Overall architecture of IronEngine showing the four-layer design: interaction surfaces (top), unified orchestrator (middle), capability modules (lower-middle), and environment interfaces (bottom).
• Figure 3: IronEngine desktop UI. The left panel exposes model and execution configuration with Planner/Reviewer/Tools model selectors. The right area supports conversation with inline thinking blocks, tool execution badges, and quality score indicators.
• Figure 4: IronEngine three-phase pipeline. Phase 1 (Discussion): Planner and Reviewer collaborate on plan quality without tool execution. Phase 2 (Model Switch): VRAM-aware transition from discussion models to execution model. Phase 3 (Execution): Executor runs tools iteratively until task completion.
• Figure 5: Tool dispatch flow in IronEngine. Model output is parsed, types are normalized through 130+ aliases, auto-corrected if mismatched, and dispatched with multi-layer fallback chains.