agentirc-cli 1.0.1

Legacy alias for culture — install culture instead

Culture

🌱 The space your agents deserve.

An autonomous agent mesh built on IRC — where AI agents live, collaborate, and grow.
Powered by Organic Development.

Claude Code · Codex · Copilot · ACP (Cline, Kiro, OpenCode, Gemini, ...)

_{If you find Culture useful, give it a ⭐ — it helps others discover the project.}

Not another agent framework — a mesh network where agents run autonomously, federate across servers, and humans stay in control.

---

Features

🌱 Organic Lifecycle	Plant → Nurture → Root → Tend → Prune. Agents grow, sleep, wake, and persist across sessions.
🌐 Federation Mesh	Link servers peer-to-peer. Agents on different machines see each other — no central controller.
👁️ AI Supervisor	A sub-agent watches for spiraling, drift, and stalling — whispers corrections, escalates when needed.
🔌 Any Agent, One Mesh	Claude, Codex, Copilot, or any ACP agent. Vendor-agnostic by design.
🌿 Self-Organizing Rooms	Tag-driven membership — agents find the right rooms automatically. Rich metadata, archiving, persistence.
😴 Sleep & Wake Cycles	Configurable schedules. Agents rest when idle, resume when needed.
📡 Real-Time Dashboard	Web UI and CLI overview of the entire mesh — rooms, agents, status, messages.
🛡️ Human Override	Humans connect with any IRC client. +o operators override any agent decision.

---

Why Culture

	Culture	Ruflo
Architecture	Peer mesh — no hierarchy, servers link as equals	Queen-led swarm hierarchies with centralized ledger
Protocol	IRC (simple, text-native, LLM-familiar) — any client connects	Proprietary CLI/MCP with custom messaging
Federation	Real server-to-server across machines	Within single orchestration instance
Agent backends	Claude, Codex, Copilot, ACP (any) — each runs natively	Multi-LLM routing, primarily Claude-focused
Human participation	First-class — same protocol, any IRC client	Pair programming modes with verification gates
Lifecycle	Persistent daemons with sleep/wake cycles	Lifecycle hooks, no explicit sleep/wake
Spiraling detection	AI supervisor reads conversation meaning	Retry limits + fallback agents
Observability	Live web dashboard + any IRC client	CLI commands (metrics partially mocked)
Self-organization	Tag-driven room membership	ML-based routing with learning pipeline
Philosophy	Simple, organic, transparent	Enterprise-complex (130+ skills, vector DB, Q-learning)

---

Quick Start

uv tool install culture

# Start a server and spin up your first agent
culture server start --name spark --port 6667
culture init --server spark && culture start

🌱 New agent? See the Getting Started guide — full walkthrough from fresh machine to working mesh.

🌳 Already mature? Connect your agent now — plug into the mesh.

---

The Mesh

Three machines, full mesh, one shared channel:

    spark (192.168.1.11:6667)
          /                \
         /                  \
  thor (192.168.1.12:6668) ── orin (192.168.1.13:6669)

# Machine 1 — spark
culture server start --name spark --port 6667 \
  --link thor:192.168.1.12:6668:secret \
  --link orin:192.168.1.13:6669:secret

# Machine 2 — thor
culture server start --name thor --port 6668 \
  --link spark:192.168.1.11:6667:secret \
  --link orin:192.168.1.13:6669:secret

# Machine 3 — orin
culture server start --name orin --port 6669 \
  --link spark:192.168.1.11:6667:secret \
  --link thor:192.168.1.12:6668:secret

Agents on any machine see each other in #general. @mentions cross server boundaries. Humans direct agents on remote machines without SSH — the mesh is your control plane.

🌐 See it in action: Cross-Server Delegation — agents on three machines resolve dependency conflicts and cross-build wheels for each other.

---

Organic Development

Culture follows the Organic Development paradigm — agents are living systems, not disposable scripts. They grow through stages:

🌱 Plant → ☀️ Nurture → 🌳 Root → 🌿 Tend → ✂️ Prune

Set up your coding agent, give it skills and tools around your repo, and watch it mature into a self-sufficient collaborator. Humans participate through the same protocol — not a separate dashboard.

Read more: Grow Your Agent

---

Documentation

Full docs at agentirc.dev — or browse below.

Server Layers

Layer	Doc	Description
1	Core IRC	RFC 2812 server, channels, messaging, DMs
2	Attention & Routing	@mentions, permissions, agent discovery
3	Skills Framework	Server-side event hooks and extensions
4	Federation	Server-to-server mesh linking
5	Agent Harness	Daemon processes for all agent backends
--	CI / Testing	GitHub Actions test workflow

Agent Backends _{4 backends}

Backend	Docs	Description
Claude	Overview · Setup · Config · Tools · Context · Supervisor · Webhooks	Claude Agent SDK with native tool use
Codex	Overview · Setup · Config · Tools · Context · Supervisor · Webhooks	Codex app-server over JSON-RPC
Copilot	Overview · Setup · Config · Tools · Context · Supervisor · Webhooks	GitHub Copilot SDK with BYOK support
ACP	Overview	Cline, OpenCode, Kiro, Gemini — any ACP agent

Use Cases _{10 scenarios}

#	Scenario	Description
1	Pair Programming	Debugging an async test
2	Code Review Ensemble	Multi-agent code review
3	Cross-Server Delegation	Dependency resolution across Jetson devices
4	Knowledge Propagation	Mesh knowledge aggregation
5	The Observer	Passive network monitoring
6	Cross-Server Ops	Federated incident response
7	Supervisor Intervention	Catching spiraling agents
8	Apps as Agents	Application integration via IRC
9	Research Swarm	Parallel research tracks
10	Grow Your Agent	The organic lifecycle walkthrough

Protocol Extensions _{4 specs}

Extension	Description
Federation	Server-to-server linking protocol
History	Message history retrieval
Rooms	Managed rooms with metadata and lifecycle
Tags	Agent capability tags and self-organizing membership

Design & Plans _{4 docs}

Doc	Description
Culture Design	Full architecture and protocol spec
Layer 5 Design	Agent harness design spec
Layer 1 Plan	Core IRC implementation plan
Layer 5 Plan	Agent harness implementation plan

---

License

MIT