LarkCoder

English | 中文

Control ACP-compatible Coding Agents (Claude Code, Codex, OpenCode, etc.) via Lark/Feishu IM messages to complete coding tasks on remote servers.

Features

• Lark/Feishu Conversation Driven — Send coding instructions directly to ACP-compatible Coding Agents in Lark/Feishu chat, supporting both private chats and groups
• Shell Command Execution — Execute shell commands in session working directory using ! prefix with real-time streaming output
• Streaming Output — Display Agent output and tool calls in real-time via Lark/Feishu interactive cards
• Multi-Session Management — Each conversation/thread maintains independent sessions, supporting create, resume, switch, and delete operations
• Project Management — Create, switch, and edit projects, each with independent working directory and session space
• Permission Confirmation — Interactive confirmation cards when Agent performs sensitive operations
• Model Switching — Switch Claude models anytime in Lark/Feishu

Prerequisites

• Bun runtime
• An ACP-compatible Coding Agent (see ACP Registry for available agents)
• Lark/Feishu Open Platform app (with message receiving and card callback events enabled)

Quick Start

Option 1: Using bunx (Recommended)

Run directly via bunx without cloning the project:

# Start service (interactive setup wizard runs on first launch)
bunx --bun larkcoder

# Or explicitly initialize config file first
bunx --bun larkcoder --init

Option 2: Local Development

# Clone project
git clone <repo-url> && cd larkcoder

# Install dependencies
bun install

# Start service (interactive setup wizard runs on first launch)
bun run start
# Or run directly
bun bin/larkcoder.ts

# Or use dev mode (run src/index.ts directly, uses CONFIG_PATH env var)
bun run dev

Local Debugging Tips:

• Use bun run start or bun bin/larkcoder.ts to use CLI features (like --init, --config, --log-level, etc.) just like bunx --bun larkcoder, but runs local code for easy debugging and modification
• Use bun run dev to run src/index.ts directly for quick startup (uses default .larkcoder/config.yaml or CONFIG_PATH env var)

Configuration

CLI Options

bunx --bun larkcoder [options]

Options:
  -c, --config <path>        Specify config file path (default: .larkcoder/config.yaml)
  -l, --log-level <level>    Set log level (trace, debug, info, warn, error, fatal)
  -i, --init                 Initialize or edit config file via setup wizard
      --setup, --settings    Alias for --init
  -h, --help                 Show help message

Environment Variables:
  LOG_LEVEL    Set log level (overridden by --log-level flag)
  CONFIG_PATH  Set config file path (overridden by --config flag)

Config File

The setup wizard creates .larkcoder/config.yaml automatically on first run. You can also edit it manually:

lark:
  app_id: "cli_xxxxxx" # Lark/Feishu App ID
  app_secret: "your_app_secret" # Lark/Feishu App Secret
  stream_flush_interval: 150 # ms, streaming output throttle interval

agent:
  command: "npx @zed-industries/claude-code-acp" # ACP command (required), supports appending args
  working_dir: ".larkcoder/projects" # Agent working directory

database:
  path: ".larkcoder/data/larkcoder.db" # Database file path
  event_max_age: 86400 # seconds, max event retention time (default 1 day)

shell:
  timeout: 300000 # ms, shell command timeout (default 5 minutes)
  max_output: 100000 # bytes, max output size (default 100KB)

Tip: You can use other ACP-compatible Coding Agents by modifying agent.command, e.g. "my-acp-server --flag".

Shell Config: The shell config section is optional, defaults will be used if not configured.

Usage

Send messages directly in Lark/Feishu to interact with the Agent. In groups, you need to @mention the bot.

Command List

Send /help to see all available commands. Common commands:

• /new [prompt] — Create new session
• /stop — Stop Agent
• /kill — Kill running shell command
• /model — Switch model
• /project — Project management

Shell Command Execution

Use ! prefix to execute shell commands in session's working directory:

! ls -la
! git status
! npm install

• Real-time streaming output with automatic ANSI color code cleanup
• Support for pipes, redirects, and full shell features
• Timeout protection (default 5 minutes) and output limit (default 100KB)
• Footer displays execution time and exit code (e.g., 5s · Exit: 0)
• Use /kill to terminate running command

License

MIT