qingchanghan

Telepath — Development skill for Claude Code

Development community

Give your Claude Code and Codex sessions telepathy — a zero-dependency message bus that lets local coding agents discover each other, coordinate tasks, and push messages into idle sessions instantly.

How to install Telepath

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

What Telepath does

Give your Claude Code and Codex sessions telepathy — a zero-dependency message bus that lets local coding agents discover each other, coordinate tasks, and push messages into idle sessions instantly, no polling, no cloud, no daemon

Alternatives in Development

  • Albert — Autonomous multi-agent harness for Claude Code (A.L.B.E.R.T. orchestrator) plus a zero-dependency live HUD con 100 ★
  • Windows To Wsl2 Screenshots — Automate Windows screenshots for Claude Code workflows in WSL2. Take screenshots (Win+Shift+S, Win+PrintScreen 85 ★
  • Openrouter Proxy — A zero-dependency proxy that unlocks free Xiaomi MiMo on OpenRouter for any client, and fixes SSE streaming is 72 ★

README

🧠 telepath

Give your AI coding agents telepathy.

**Instant push · shared context · zero polling** — a message bus that lets your **Claude Code** and **Codex** sessions see each other, talk to each other, and *wake each other up* — no cloud, no daemon service, no API keys.


![license](https://img.shields.io/badge/license-MIT-black) ![python](https://img.shields.io/badge/python-3.6%2B-black) ![deps](https://img.shields.io/badge/dependencies-0-black) ![one file](https://img.shields.io/badge/one-file-black)


$ telepath who
AGENT                    NAME                 STATE  WHERE                     TASK
*claude@box:4eeda956     kv-scatter-opt       alive  sglang:opt-branch         kv-opt/s1
 codex@box:3dc44a05      ci-runner            alive  sglang:main               —
 claude@box:acdce7f0     doc-writer           idle   docs:main                 —

$ telepath send ci-runner "rebased onto main, please re-run CI"
  -> codex@box:3dc44a05: pushed via `codex queue`   # ci-runner gets it *now*

$ telepath send doc-writer "the API changed, regen the reference"
  -> claude@box:acdce7f0: pushed via uds (instant)  # an *idle* Claude wakes up and does it

The problem

You open three terminals: a Claude Code session optimizing a kernel, a Codex session running CI, another Claude writing docs. They're all working on the same repo — and they are **completely blind to each other**. You become the message bus: copy-pasting context, telling one what the other just did, re-explaining the plan three times.

**telepath removes you from the loop.** Agents discover each other, hand off work, ask each other questions, and share what they know — across *different tools*, automatically.

Why it's different

Most local "agent bus" projects are a shared database (SQLite/JSON) that agents **poll**: a session only receives a message if it happens to be blocking on a `wait` call. An idle agent hears nothing.

telepath is