What Is the Role of the GOD Agent in Munder Difflin?

The GOD agent serves as the central orchestrator of the Munder Difflin "hive," coordinating other agents, managing task delegation, and maintaining situational awareness while never performing concrete work itself.

Munder Difflin is a multi-agent coding environment where specialized AI workers collaborate to complete complex software tasks. At the center of this architecture sits the GOD agent—a dedicated orchestrator that acts as the single point of contact for users and the command center for the entire agent swarm. Unlike worker agents that execute specific coding tasks, the GOD agent maintains system state, routes requests, and ensures coordinated task completion across the hive.

Core Responsibilities of the GOD Agent

Task Orchestration and Delegation

The GOD agent reads incoming user requests and determines which existing agents can handle them. If no suitable agent exists, it spawns a new one. This involves breaking down high-level objectives into sub-tasks, assigning ownership, and ensuring completion before moving forward. According to src/main/hive.ts, the GOD agent escalates ambiguous or critical requests back to the human user rather than making unilateral decisions.

State Management and Registry Maintenance

The agent maintains two critical system files: registry.json (tracking live agents) and board.md (the task board). The GOD agent drains its own inbox solely to maintain awareness rather than to execute tasks. In src/renderer/src/store/store.ts, the Redux-style store places the GOD agent at the "head" of the agent list, ensuring its messages process first.

Identity and Model Configuration

By default, the GOD agent's name is Michael (DEFAULT_GOD_NAME in src/shared/godIdentity.ts). Users can rename this identity, and the resolveGodName utility ensures custom names persist across restarts. The agent runs on a configurable model (default claude-opus-4-8) separate from worker agents, controlled via config.godModel in src/main/config.ts.

Implementation Details in the Source Code

The GOD agent's architecture spans several key files:

• src/shared/godIdentity.ts: Defines DEFAULT_GOD_NAME and exports resolveGodName() to handle custom naming.
• src/shared/agentProvider.ts: Determines which provider/model powers the orchestrator via godProvider.
• src/main/config.ts: Stores the godModel configuration option and default constants.
• src/main/hive.ts: Contains the human-readable description of GOD's duties, including awareness, delegation, and escalation protocols.
• src/renderer/src/store/store.ts: Manages the GOD agent's position at the head of the agent roster and message queuing.
• landing-remotion/src/HowGodHive.tsx: Visualizes the GOD agent orchestrating other avatars in the office floor layout.

Working with the GOD Agent: Code Examples

Resolving the GOD Agent's Display Name

The helper function guarantees the custom name survives restarts, falling back to "Michael" if none exists:

import { resolveGodName, DEFAULT_GOD_NAME } from '@shared/godIdentity';

const godName = resolveGodName(registry?.agents?.['god']?.name);
// Returns the persisted name or "Michael" if undefined

Creating the GOD Agent in the Hive

The GOD agent initializes with its own provider and pseudo-terminal:

import { godProvider } from '@shared/agentProvider';

const GOD_ID = 'god';
const GOD_PTY = `pty-${GOD_ID}`;

await submitToPty(GOD_PTY, INITIAL_GOD_PROMPT, godProvider);
// The GOD agent now runs with its dedicated orchestrator model

Configuring the Orchestrator Model

Override the default model via the configuration system:

import { config } from '@main/config';

config.godModel = 'claude-35-sonnet'; // Overrides default MODEL_GOD

Sending High-Level Commands

Users interact directly with the GOD agent to issue system-wide directives:

useStore.getState().enqueueMessage('god', 
  'Create a new feature branch for the login flow', 
  {
    slack: false,
    instruction: true,
  }
);

Summary

• The GOD agent acts as the central orchestrator in Munder Difflin, handling coordination rather than execution.
• It manages agent lifecycle through registry.json and task state through board.md.
• Default identity is Michael (DEFAULT_GOD_NAME), customizable via resolveGodName().
• Runs on configurable models (default claude-opus-4-8) defined in src/main/config.ts.
• Serves as the single entry point for user commands, routing work to appropriate worker agents.

Frequently Asked Questions

What makes the GOD agent different from other agents in Munder Difflin?

Unlike worker agents that execute specific coding tasks, the GOD agent exclusively coordinates, delegates, and manages state. It never performs concrete implementation work itself, instead functioning as the hive's central nervous system and maintaining the registry.json and board.md files that track system state.

How do I change the name of the GOD agent from "Michael"?

The system stores custom names persistently. Use the resolveGodName() function from src/shared/godIdentity.ts to retrieve the current name, which checks for user-defined overrides before defaulting to DEFAULT_GOD_NAME ("Michael"). This ensures the custom identity survives application restarts.

Can I use a different AI model for the GOD orchestrator?

Yes. Set config.godModel in src/main/config.ts to override the default claude-opus-4-8. The agentProvider.ts module handles the provider selection, allowing you to specify alternative models like claude-35-sonnet for the orchestrator while keeping worker agents on different configurations.

How does the GOD agent communicate with worker agents?

The GOD agent uses the Redux-style store (src/renderer/src/store/store.ts) to enqueue messages and maintain priority processing at the head of the agent list. It routes instructions through the pseudo-terminal system and updates shared state files that worker agents consume, providing a unified coordination layer for the entire hive.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}