AI Agents for Air-Gapped Industrial Environments: Why goose?

* Hoseong Lee Engineer at Korea Aerospace Industry Research Institute ---------------------------------------- The explosive growth of AI agent technology has brought tools like OpenAI’s Claude Code, Grok Build, and Codex to the forefront. While the IT industry has rapidly adopted these advancements, the situation inside traditional manufacturing and heavy industry supply chains is fundamentally different. In sectors such as automotive, shipbuilding, aerospace, and finance — where stringent technical security and intellectual property protection are non-negotiable — organizations maintain strict air-gapped (closed network) environments. This complete isolation from external networks renders mainstream cloud-based chatbots and SaaS agents unusable. Does this mean we must abandon agent adoption in these isolated environments? Not at all. After field-testing multiple agent frameworks, I concluded that goose is currently the most practical and effective solution for air-gapped industrial settings. This article explains why, from a technical perspective. 1. THE CORE PARADIGM: AGENT = MODEL + HARNESS At present, the most accurate way to define an agent architecture is Model + Harness. An agent’s behavior ultimately depends on the combination of an AI model and the execution environment wrapped around it. In air-gapped environments, how these two components are combined determines success or failure. Model Selection Because SaaS models (GPT, Claude, Grok, Gemini, etc.) are unavailable, organizations must rely on on-premise enterprise models or open-weight models that can run inside the infrastructure. Given the relatively conservative budgets and validation processes typical in manufacturing, practical entry-level options are lightweight open-weight models such as Gemma or Qwen-series models. Harness Selection The harness includes the tool set, system prompt interface, and context management layer that acts as the model’s “hands and feet.” The key challenge for air-gapped agent adoption is finding the optimal harness that fully supports BYOK (Bring Your Own Key/Model) while maximizing the reasoning capability of relatively smaller open-weight models. 2. REVIEW OF MAJOR AGENT FRAMEWORKS I evaluated several agent frameworks for industrial applicability. Here are the key insights: * GitHub Copilot CLI: Provided clear visibility into how model size and type affect output quality within the same harness. The performance gap among SOTA models has narrowed due to overall capability improvements. * Claude Code / Codex / Grok Build / Antygravity: These vendor-optimized harnesses deliver excellent performance when paired with their own models. However, they are often too heavy and inefficient when used with different models in air-gapped environments. * Kiro: Incorporates Spec-Driven Development principles, requiring a design review phase before implementation. Its strong explainability makes it particularly trustworthy for engineering teams. * JetBrains Junie: Demonstrates how a well-optimized harness can extract high-quality results even from smaller built-in models (e.g., Gemini Flash). However, its token-based pricing model may lead to higher long-term costs compared to subsidized APIs. * Droid (Factory.ai): Features a sophisticated sub-agent system and optimized harness. It maintains strong performance even with open-weight models and includes a Readiness Report feature that helps non-developers handle CI/CD, security, and build quality issues. * OpenCode / Pi-Coding Agent: Representative open-source tools that allow flexible harness construction. Pi, in particular, follows an extreme minimal harness philosophy — using only essential tools and a very small system prompt to drastically reduce context consumption. While excellent for developers who want to design their own AGENTS.md, it has a relatively high initial learning curve. 3. WHY GOOSE? SELECTION CRITERIA FOR AIR-GAPPED ENVIRONMENTS After establishing strict evaluation criteria for industrial deployment, Goose stood out as the strongest match: Air-Gapped Agent Requirement Goose’s Approach Fully offline installation, no external login No external authentication required for installation or activation Cross-platform (Linux, Mac, Windows) Provides builds ready for diverse legacy manufacturing infrastructure No subscription licensing Completely free; runs entirely on internal on-premise resources BYOK (Bring Your Own Key/Model) support Native support for Ollama, OpenAI-compatible APIs, and other local/private providers Transparent harness engineering GUI access to edit core system prompts directly Model-agnostic (Generic Harness) Lightweight, universal harness without heavy optimization for any single model Enterprise trust & governance Contributed to the Agentic AI Foundation (AAIF) under the Linux Foundation 4. GOOSE’S DIFFERENTIATED TECHNICAL ARCHITECTURE 4.1 SYSTEM PROMPT TRANSPARENCY AND AIR-GAP HARDENING Goose exposes its core behavioral prompts (system, plan, compaction.md, etc.) through Settings > Prompts and allows direct editing. This transparency becomes a powerful advantage in air-gapped environments. In completely isolated networks, agents frequently attempt to install external packages (pip install, npm install) or make outbound API calls, wasting tokens and resources. With Goose, you can inject environmental constraints directly into the system prompt layer: – You are operating in a completely isolated internal network (Air-Gapped Environment). – Commands that attempt to install packages or libraries over the external internet will not work. – Solve problems using only internal repositories and pre-configured internal binaries. Managing control through per-project AGENTS.md files becomes extremely inefficient at enterprise scale. Goose enables centralized, organization-wide policy enforcement at the harness (system prompt) level — a far more scalable approach for consistent governance. 4.2 MCP (MODEL CONTEXT PROTOCOL) AND RECIPE-BASED DOMAIN AGENT EXTENSIBILITY While most frameworks optimize primarily for software coding, Goose adopts Anthropic’s Model Context Protocol (MCP) as a core architectural component. This is the key that enables evolution from coding agents into true domain agents usable by non-developer domain experts in manufacturing. Consider a typical automotive/manufacturing workflow: * Design phase: Structural designers create geometry in CATIA according to drawing guidelines. * Analysis phase: The CAD output is passed to structural analysis engineers who run safety tests in tools like Patran. * Iteration loop: Design → data transfer → analysis → feedback → redesign. In Goose, this entire workflow can be standardized as a portable YAML Recipe. A recipe can define sequential instructions and reference Subrecipes, allowing the agent to execute the agreed-upon flow without repeated manual prompting. Importantly, this workflow contains no traditional software coding. General-purpose coding harnesses become unnecessarily heavy here. Goose’s architecture allows all MCP Extensions to be disabled, reducing the agent to a pure reasoning engine (chatbot). You then attach only the domain-specific MCP tools required (e.g., a CATIA MCP Tool or Patran MCP Tool) under the control of a Recipe. (The MCP tool mentioned above is merely an example and may not actually exist) By stripping away unnecessary capabilities and composing only the precise MCP connectors needed for the domain, you can build highly focused, cost-efficient domain agents even when using smaller open-weight models with limited context windows. 5. CONCLUSION: WHY GOOSE IS THE REALISTIC PATH FORWARD Ultimately, Goose’s biggest advantage in air-gapped environments is its flexible architecture. Instead of forcing local open-weight models into a fixed set of features, Goose dynamically changes its harness based on the specific task. This maximizes context efficiency and gets the best possible performance out of smaller, on-premise models. Of course, setting up custom MCP extensions and harnesses for specific industrial workflows requires an initial learning curve and engineering effort. However, this is a necessary trade-off to run agents safely and stably under strict network constraints. Technical flexibility is important, but long-term reliability is just as critical for enterprises. Unlike many small open-source projects that stop being updated, Goose is officially managed by the Agentic AI Foundation (AAIF) under the Linux Foundation. This solid governance gives enterprise decision-makers the trust they need to pass strict internal security and compliance reviews. Cloud technology might reduce the need for strict air-gapping in the future, but today’s industrial operations cannot afford to wait. Delaying AI adoption due to security concerns will only hurt global competitiveness. With its local model support, transparent control, and MCP-based recipe orchestration, Goose is the most realistic and practical solution for isolated industrial environments today. ---------------------------------------- Hoseong Lee is a software engineer working in the aerospace sector focused on AI and ML applications for aerospace design. This article reflects the author’s personal technical perspective.