services

A set of project rules that separates three services: the Bot runtime that connects Feishu to coding agents, the desktop Console that manages them, and the web Console. It also defines how they start, use ports, and run multiple Bots.

In plain words
What is it for?
Use it when explaining or troubleshooting service startup, Console windows, ports, Bot connections, profiles, or Fleet mode, where several independent processes may be involved.
Why use it?
It prevents confusion about which process to start when dealing with extra windows, ports, or Bots. It clarifies that opening the Console does not itself start a Bot.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/zhourong12/cursor-bridge/services
Clone the repo
git clone --depth 1 https://github.com/zhourong12/cursor-bridge

Made for: Cursor.

Per session 1,389 This file is loaded in full into every session.
When invoked 1,389 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01389 $0.01389
Opus 5 $0.00694 $0.00694
Sonnet 5 $0.00278 $0.00278
Haiku 4.5 $0.00139 $0.00139

Measured yesterday against content hash f33cc7b32095, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

services scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/services.mdc · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

三类服务(必须区分,禁止混为一谈)

本仓库有 三个独立服务。它们职责、进程、端口、启动入口 各不相同
回答用户「怎么启动」「为什么两个窗口」「连了几个 bot」时,先判断用户指的是哪一类。


1. Bridge Bot 运行时(飞书 ↔ Agent)

说明
是什么 真正连飞书、跑 Cursor/Claude Agent、处理 /scheduleBot 进程
不是什么 不是管理网页;没有给用户点的 Console 窗口;不占 3928 管理端口
进程 每个 Profile 一个 nodelark-channel-bridge run 或后台 daemon)
数据 ~/.lark-channel/fleet.jsonregistry/processes.json

启动方式(二选一或并存多个 profile)

模式 适用 入口
单 Bot 前台 开发调试、只跑 active profile start.batnpm run lark-bridge:cursor
单 Bot 重启 src/ restart.batnpm run lark-bridge:restart
Fleet 多 Bot 多个 Profile 同时在线 fleet-restart.batnpm run lark-bridge:fleet-restart

Fleet 说明:

  • 配置在 ~/.lark-channel/fleet.jsonautoStartbots
  • fleet startprofile 拉起多个 Bot 进程,不是 多开端口、也不是多开 Console
  • 启动后终端应看到各 Bot 连接信息;汇总:lark-channel-bridge fleet status --all

与 Console 关系:Bot 可单独跑;Console 只是管理 Bot/Fleet,不会代替 fleet startlark-bridge:cursor 自动起 Bot。


2. Bridge Console · Electron(桌面管理壳)

说明
是什么 本地 管理界面:概览、Bot 绑定、Fleet、进程、定时任务、日志
不是什么 不是飞书 Bot;打开它 不会 自动连接飞书
端口 内嵌 HTTP 3928(仅本机)
窗口 1 个 Electron 窗口

启动

.\run-console.cmd
# 或 npm run console:run
# 开发:npm run console(electron desktop/electron-main.cjs)

打包:npm run pack:consolerelease/win-unpacked/Bridge Console.exe


3. Bridge Console · Web(浏览器管理)

说明
是什么 与 Electron 同一套 Admin API + 静态页,用 浏览器 打开
不是什么 不是第三个 Bot;不是「多开一个飞书连接」
端口 HTTP 3928(与 Electron Console 共用,同时只能有一个监听)
窗口 1 个 浏览器标签/窗口(脚本 --open 自动打开)

启动

.\console-web.bat
# 或 npm run console:web:build

登录:http://127.0.0.1:3928/?token=<admin-token>(token 在 ~/.lark-channel/admin-token


互斥与常见误区

误区 正确说法
「开了 Console = Bot 已上线」 错误。Console 只是管理 UI;Bot 需 Bot 运行时Fleet 单独启动
「3928 / 3930 各开一个 = 两个 Bot」 错误。那是 Console 管理端口;多端口 = 多个 Console 实例,不是多个 Bot
「Electron + 浏览器 = 两个 Bot」 错误。是 Console Electron + Console Web 各一个界面;应 二选一
「Fleet 多 Bot = 多个 Console」 错误。Fleet = 多个 Bot 进程;Console 仍然只需 一个(Electron 或 Web)

Read the full file on GitHub · 119 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 119 lines · 1,389 tokens per session scan A f33cc7b32095

Subscribe to this mod's changes

services is a cursor rule published in the GitHub repository zhourong12/cursor-bridge (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,389 tokens to every session, about $0.0069 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.