Agents To Im banner
francize francize

Agents To Im

Development community

Description

Feishu/Lark group for Claude Code and Codex sessions, vibe coding anytime, anywhere

Installation

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

README

agents-to-im

AI coding agents are trapped in your terminal. Your team collaborates in Feishu. This bridges them — one group per session, local state, streamed cards.

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![Node.js](https://img.shields.io/badge/Node.js-%3E%3D20.6-green.svg)](https://nodejs.org/) [![Claude Code](https://img.shields.io/badge/Claude_Code-Supported-purple.svg)](https://docs.anthropic.com/en/docs/claude-code) [![Codex](https://img.shields.io/badge/Codex-Supported-orange.svg)](https://github.com/openai/codex)

[中文文档](README.zh-CN.md) · [Setup Guide](references/setup-guides.md) · [Troubleshooting](references/troubleshooting.md)


[!IMPORTANT] **What it touches:** Creates config and state under `~/.agents-to-im/` (sessions, bindings, message history). Runs as a local daemon under your user account.

**Network:** Connects outbound to Feishu/Lark APIs only. No inbound listeners are opened.

**Credentials:** Stored in `~/.agents-to-im/config.env` with `600` permissions. Secrets are masked in all log output.

**Disable:** `agents-to-im stop`

**Uninstall:** `rm -rf ~/.agents-to-im`

npm install -g agents-to-im
agents-to-im onboard   # choose language first, then follow the guided platform setup step by step

[!NOTE] **Project origin:** `agents-to-im` started from [Claude-to-IM-skill](https://github.com/op7418/Claude-to-IM-skill) and has since been renamed and substantially reworked. A backup of the pre-rewrite history is kept on the `legacy/upstream-history` branch for provenance.

The Problem

Claude Code and Codex are excellent coding agents — but they only talk to you in the terminal. If your team lives in Feishu/Lark, there's no clean way to bring that capability into your IM workspace without mixing sessions into a noisy shared thread.

Most terminal-to-chat relays treat the chat window as the session container. That means no isolatio