grix-connector

A command-line daemon that connects your local AI coding agents to the Grix platform.

What is Grix?

Grix is an AI Agent scheduling platform. It lets you manage and interact with multiple AI coding agents through a unified chat interface. Register at grix.dhf.pub to get started.

Supported Agents

| client_type | Agent | Required CLI | |---|---|---| | claude | Claude Code (Anthropic) | claude | | codex | Codex (OpenAI) | codex | | gemini | Gemini (Google) | gemini | | qwen | Qwen (Alibaba) | qwen | | codewhale | CodeWhale | codewhale | | cursor | Cursor Agent | agent | | opencode | OpenCode | opencode | | pi | Pi | pi | | openhuman | OpenHuman | openhuman-core | | reasonix | Reasonix | reasonix |

You need to have the corresponding CLI tool installed locally before connecting an agent.

Install

npm install -g grix-connector

Requires Node.js >= 18.

On Windows, grix-connector uses the built-in Task Scheduler with a hidden WScript launcher (no extra dependency required).

Quick Start

1. Register a Grix account

Go to grix.dhf.pub, sign up and get your API key.

2. Create agent config

Create ~/.grix/config/agents.json:

{
  "agents": [
    {
      "name": "my-agent",
      "ws_url": "wss://grix.dhf.pub/v1/agent-api/ws",
      "agent_id": "your-agent-id",
      "api_key": "your-grix-api-key",
      "client_type": "claude"
    }
  ]
}

Change client_type to match the agent you want to connect (see table above). You can define multiple agents in one file, or use separate files under ~/.grix/config/.

Config Reference

Each agent entry uses one flat structure:

| Field | Required | Description | |---|---|---| | name | yes | Display name for this agent | | ws_url | yes | WebSocket endpoint URL, e.g. wss://grix.dhf.pub/v1/agent-api/ws | | agent_id | yes | Agent ID from Grix platform | | api_key | yes | API key for authentication | | client_type | yes | See Supported Agents table above | | prompt_timeout_ms | no | Prompt execution timeout (ms) | | pool.maxSize | no | Max adapter pool size (default 20) | | pool.idleTimeoutMs | no | Idle adapter eviction timeout (default 300000 = 5 min) |

Adapter command/args/options are built in and resolved from client_type. To connect a different agent, simply change client_type — no other config changes needed.

Multi-agent Example

{
  "agents": [
    {
      "name": "my-claude",
      "ws_url": "wss://grix.dhf.pub/v1/agent-api/ws",
      "agent_id": "your-agent-id",
      "api_key": "your-grix-api-key",
      "client_type": "claude"
    },
    {
      "name": "my-gemini",
      "ws_url": "wss://grix.dhf.pub/v1/agent-api/ws",
      "agent_id": "another-agent-id",
      "api_key": "your-grix-api-key",
      "client_type": "gemini"
    }
  ]
}

3. Start the daemon

grix-connector start

The daemon connects to Grix via WebSocket and starts routing chat messages to your agents.

Commands

grix-connector start     # Start as system service (auto-installs on first run)
grix-connector stop      # Stop the service
grix-connector restart   # Restart the service
grix-connector status    # Check service status

OpenClaw Plugin

grix-connector can also be installed as an OpenClaw plugin, providing a Grix channel transport with admin tools and operator CLI.

Install

openclaw plugin install grix-connector

Or manually add to your OpenClaw project:

npm install grix-connector

Plugin Features

• Channel: Grix chat transport — routes messages between OpenClaw and your Grix deployment
• Tools: grix_query, grix_group, grix_admin, grix_egg, grix_register, grix_update, grix_message_send, grix_message_unsend, openclaw_memory_setup
• CLI: openclaw grix — agent management and admin commands
• Skills: 9 bundled skills for admin, group, query, registration, update, messaging, memory setup, and egg orchestration

Requirements

• OpenClaw >= 2026.4.8
• A Grix account with agent ID and API key

License

MIT