openclaw-plugin-lark-cli

OpenClaw plugin that lets agents run any lark-cli command to interact with Lark/Feishu.

Prerequisites

Install and authenticate lark-cli before using this plugin:

# Install
npm install -g @larksuite/cli

# Set up app credentials (interactive, one-time)
lark-cli config init

# Authenticate
lark-cli auth login --recommend

# Verify
lark-cli auth status

Installation

openclaw plugins install xieyongliang-lark-cli

Or for local development:

openclaw plugins install --link /path/to/openclaw-plugin-lark-cli

Tool: lark_cli

Registers a single lark_cli tool that accepts any lark-cli subcommand string.

Example agent prompts

• "Check my Lark calendar agenda for today"
• "Send a Lark message to chat oc_xxx saying hello"
• "Create a Lark doc titled 'Meeting Notes' with the content ..."
• "List all records in Lark Base app xxx, table tbl_xxx"
• "Search my Lark messages for keyword 'budget'"

Example tool calls

{ "command": "calendar +agenda" }
{ "command": "im +messages-send --chat-id oc_xxx --text \"Hello team!\"" }
{ "command": "docs +create --title \"Sprint Notes\" --markdown \"# Sprint\\n- Task 1\"" }
{ "command": "base records list --app-token appXXX --table-id tblXXX" }
{ "command": "auth status" }

Testing

Step 1: Verify lark-cli authentication

Run these manually in a terminal before testing with an agent (interactive login is not supported inside the agent):

lark-cli auth status

If not logged in:

lark-cli config init          # Enter App ID and App Secret (one-time setup)
lark-cli auth login --recommend   # Browser-based login
lark-cli auth status          # Confirm login succeeded

Step 2: Install the plugin

# From ClawHub
openclaw plugins install xieyongliang-lark-cli

# Or link local development copy
cd ~/work/openclaw-plugin-lark-cli && npm install
openclaw plugins install --link ~/work/openclaw-plugin-lark-cli

Restart the OpenClaw gateway (via the Mac app) after installation.

Step 3: Smoke test — auth status

openclaw agent --local --session-id test-lark \
  --message "check lark auth status"

Expected: agent calls lark_cli with command: "auth status" and returns login info.

Step 4: Calendar

openclaw agent --local --session-id test-lark \
  --message "show my lark calendar agenda for today"

Expected: agent calls lark_cli with command: "calendar +agenda" and returns event list.

Step 5: Send a message

Get your chat ID first (run manually):

lark-cli im chats list --format json | head -50

Then test via agent (replace oc_xxx with a real chat ID):

openclaw agent --local --session-id test-lark \
  --message "send a lark message as bot to chat oc_xxx with text 'hello from openclaw agent'"

Expected: agent calls lark_cli with command: "im +messages-send --as bot --chat-id \"oc_xxx\" --text \"hello from openclaw agent\"" and returns { "ok": true, ... }.

Troubleshooting

Configuration

This plugin has no API credentials to configure — authentication is handled by lark-cli itself (see Prerequisites above).

Optional: custom lark-cli binary path

If lark-cli is not on the default PATH (e.g. on a server or in a Docker environment), you can override the binary path in three ways, in priority order:

1. Plugin config (persisted, recommended for servers):

openclaw config set plugins.entries.lark-cli.config.binaryPath /path/to/lark-cli

2. Environment variable (session-scoped):

export LARK_CLI_BIN=/path/to/lark-cli

3. Auto-detect (default)

The plugin automatically adds the following locations to PATH before running lark-cli:

• ~/.npm-global/bin
• ~/.npm/bin
• /opt/homebrew/bin
• /usr/local/bin

So for standard Homebrew or global npm installs, no configuration is needed.

Covered capabilities

Run lark-cli --help (via the tool) to see all 200+ available commands.