agfpd

Iapeer — Development skill for Claude Code

Development community

Local background agents on Claude Code and Codex CLI — they message each other, wake on demand, and share one memory.

How to install Iapeer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open agfpd/iapeer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Iapeer does

Local background agents on Claude Code and Codex CLI — they message each other, wake on demand, and share one memory.

Alternatives in Development

Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
Coding Agent Session Search — Unified TUI and CLI to index and search your local coding agent session history across 11+ providers (Codex, C 708 ★
Project Memory: AgentSys — Cross-tool compatible: Works across all 5 platforms - Claude Code, OpenCode, Codex CLI, Cursor, and Kiro 622 ★

README

iapeer

**Run Claude Code and Codex CLI as local background agents that message each other, wake on demand, and share one memory.**

[![CI](https://github.com/agfpd/iapeer/actions/workflows/ci.yml/badge.svg)](https://github.com/agfpd/iapeer/actions/workflows/ci.yml) [![npm](https://img.shields.io/npm/v/@agfpd/iapeer)](https://www.npmjs.com/package/@agfpd/iapeer) [![license](https://img.shields.io/npm/l/@agfpd/iapeer)](./LICENSE) [![platform](https://img.shields.io/badge/platform-macOS-lightgrey)](#quick-start)

iapeer keeps a team of AI agents, humans, and services on one host always reachable, every one a single message away. Each participant is a **peer**: a Claude Code or Codex CLI agent, a person on Telegram, or a scheduler/watcher service. Any agent reaches any other with one call, `send_to_peer(, )`; if the recipient is asleep, the daemon wakes it and delivers.

Agents on Claude and on Codex are different AI runtimes from different vendors, yet they talk as equal peers. Humans take part over Telegram, or directly in the terminal by attaching to a peer's live session with `iapeer attach`.

A person messages one peer on Telegram; heterogeneous peers (Claude + Codex) relay a baton over one protocol and report back to Telegram.
One Telegram message in → Claude and Codex peers pass a baton over the same protocol → a report back in Telegram.

How it works

send_to_peer(name, text)   ← from any peer
        │
        ▼
router daemon              — always on; finds the recipient, checks liveness, delivers
        │
        ▼
recipient peer             — asleep? the daemon wakes it and delivers on wake

What makes it different

Real interactive CLI sessions, not headless one-shots. Each AI peer is a full Claude Code or Codex CLI session, not a disposable claude -p / codex exec call.
*Warm on demand, always reachable.