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

Description and use

Integrating Claude Code and Codex into Feishu/Lark chat with permission cards preserves context, manages permissions, and maintains persistent sessions.

Problem

Teams using Feishu/Lark lack integrated coding agent context, leading to lost context, verbal approvals, and no shared session.

Outcome

The workflow enables seamless coding agent interactions within Feishu/Lark, preserving context, managing permissions, and maintaining session continuity.

Workflow

• Install Node.js ≥20 and the agent-feishu-channel package via npm.
• Create a Feishu bot app at open.feishu.cn and obtain app_id and app_secret.
• Run afc init to configure the bot, setting app credentials and the allowed_open_ids allowlist.
• Ensure claude and/or codex executables are on $PATH.
• Start the bot with afc and interact using slash commands such as /new, /stop, /status, /provider, /config set, etc.
• Use permission cards for sensitive calls; approve or reject via the Feishu UI.
• Leverage session commands (/sessions, /resume) to persist and resume work across restarts.
• Switch providers with /provider per session without rewiring the bot.
• Interrupt or queue messages using ! and observe interactive status cards.
• Adjust runtime configuration on the fly with /config set.
• Monitor context warnings and use the 50MB hard‑reset fallback if needed.

Evidence

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

Source

Permission brokering: sensitive calls become Feishu approval cards

Source