agent-nexus

One Command. All Your AI Agents United.

Shared memory + Telegram remote control for Claude Code, Codex, and Gemini CLI -- installed in 60 seconds.

English | 简体中文

The Problem

You have Claude Code, Codex, maybe Gemini CLI. They're powerful individually. But right now:

• They don't share memory. Tell Claude your coding style, Codex has no idea.
• They can't be controlled remotely. Step away from your desk? Your agents are unreachable.
• Setting up shared infrastructure is painful. Clone this, configure that, edit three different config files...

You could spend an afternoon installing RecallNest for shared memory, telegram-ai-bridge for remote control, and manually wiring MCP configs for each tool.

Or:

npm i -g @aliceljy/agent-nexus && agent-nexus init

What Happens When You Run init

$ agent-nexus init

  Detecting environment...
  ✅ Bun
  ✅ Claude Code
  ✅ Codex CLI
  ⬚ Gemini CLI (not installed, skipping)

  📝 Credentials

  Telegram Bot Token: ********
  Your Telegram User ID: 123456
  Jina API Key: jina_****

  🔌 Configuring MCP...

  📋 Backed up ~/.claude.json
  ✅ Claude Code MCP configured
  ✅ Codex MCP configured
  ✅ Bridge config generated

  ✅ agent-nexus setup complete!
  Run: agent-nexus start

That's it. Your Claude Code and Codex now share one brain. Your phone is now the remote.

Before / After

| | Before agent-nexus | After agent-nexus | |---|---|---| | Memory | Each agent starts from zero every session | All agents share persistent memory via RecallNest | | Remote control | Must be at your desk | Full control from Telegram on your phone | | Setup time | 30+ min (clone, configure, debug MCP paths...) | 60 seconds | | Config files to edit | 3-5 (per tool, per service) | 0 (auto-injected) | | Processes to manage | Start each service manually | agent-nexus start / stop |

Install

npm i -g @aliceljy/agent-nexus

Requires Bun >= 1.3 and at least one of: Claude Code, Codex CLI, or Gemini CLI.

Usage

agent-nexus init      # Interactive wizard -- detects tools, collects keys, writes all configs
agent-nexus start     # Start RecallNest + Telegram bridge in background
agent-nexus stop      # Stop all services
agent-nexus status    # Health check with memory stats

How It Works

                    agent-nexus init
                         |
          +--------------+--------------+
          |              |              |
     ~/.claude.json  ~/.codex/     ~/.gemini/
     (MCP injected)  config.toml   settings.json
          |              |              |
          v              v              v
     Claude Code     Codex CLI    Gemini CLI
          |              |              |
          +------+-------+------+------+
                 |              |
            RecallNest    telegram-ai-bridge
            (memory)      (remote control)
                 |              |
            LanceDB         Telegram
          (your brain)    (your phone)

agent-nexus doesn't replace anything. It's the glue that makes your existing tools work as a team.

What Gets Installed

| Component | What It Does | Already Have It? | |-----------|-------------|-----------------| | RecallNest | Shared memory across all agents (MCP + HTTP API) | Keeps yours, adds if missing | | telegram-ai-bridge | Telegram remote control for AI agents | Keeps yours, adds if missing | | MCP configs | RecallNest auto-registered in each tool | Non-destructive merge (backup first) |

Prerequisites

• Bun >= 1.3
• At least one AI CLI tool:
  • Claude Code
  • Codex CLI
  • Gemini CLI
• A Telegram bot token (free, from @BotFather)
• A Jina API key (free tier available at jina.ai)

Config

All configuration lives in one place: ~/.agent-nexus/config.json

{
  "telegram": { "botToken": "...", "ownerId": 123456 },
  "memory": { "jinaApiKey": "...", "dbPath": "~/.recallnest/data/lancedb" },
  "agents": { "claude": true, "codex": true, "gemini": false }
}

Ecosystem

agent-nexus is the installer for a larger ecosystem of AI agent tools:

| Project | Role | Stars | |---------|------|-------| | RecallNest | Shared memory layer (LanceDB + hybrid retrieval) | | | telegram-ai-bridge | Telegram remote control + multi-agent orchestration | | | Claude Code Studio | Multi-session collaboration platform for Claude Code | |

License

MIT