DEV Community

Cover image for Bring Claude Code and Codex into Feishu/Lark group chat — with permission cards
Dongsheng
Dongsheng

Posted on

Bring Claude Code and Codex into Feishu/Lark group chat — with permission cards

#feishu #ai #opensource #productivity

If your team lives in Feishu / Lark, but coding agents live in personal terminals, you get lost context, verbal “is it OK to run that?”, and no shared session.

agent-feishu-channel bridges Claude Code and Codex sessions into a Feishu bot — a complete coding-agent workflow inside group chat.

Why this exists

Chat is where decisions happen. The agent should show up there with local-style controls: approve dangerous tools, keep sessions across restarts, and switch providers without rewiring the bot.

What it does

  • Dual providers: Claude or Codex; /provider per session
  • Permission brokering: sensitive calls become Feishu approval cards
  • Session persistence: survives restarts; auto-resume; /sessions and /resume
  • Queue & interrupt: messages queue while generating; ! interrupts
  • Interactive cards: streaming status and tool activity
  • Runtime config: /config set without restart
  • Context mitigation: early warnings and a 50MB hard-reset fallback

Quick start

Needs Node.js ≥ 20, a Feishu bot app at open.feishu.cn, and claude and/or codex on $PATH. Install with npm install -g agent-feishu-channel, then run afc init and fill in app_id, app_secret, and the access allowlist before running afc.

Migrating from claude-feishu-channel? The command is now afc (was cfc); state auto-renames and history is kept.

Commands and caveats

/new /stop /status /cost /context /compact /provider /mode /model /config set /project /cd /memory

Permission modes: default, acceptEdits, plan, bypassPermissions. You own Feishu credentials and the allowed_open_ids allowlist; don’t default to bypassPermissions in shared groups.

MIT. Issues: https://github.com/Blackman99/agent-feishu-channel/issues

Top comments (0)