larkway 0.3.6 → 0.3.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -5
- package/README.zh.md +11 -5
- package/dist/cli/index.js +5882 -5765
- package/dist/main.js +5755 -5733
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> Turn your Claude Code or Codex subscription into a Feishu (Lark) agent your whole team can @-mention.
|
|
4
4
|
|
|
5
|
-
[中文版](README.zh.md)
|
|
5
|
+
🌐 [larkway.dev](https://larkway.dev) · [中文版](README.zh.md)
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
@@ -12,6 +12,14 @@ You @ the bot in a Feishu thread. It runs on your machine — reading your real
|
|
|
12
12
|
|
|
13
13
|
---
|
|
14
14
|
|
|
15
|
+
## 💬 Join the community (Feishu)
|
|
16
|
+
|
|
17
|
+
See Larkway in action and talk through how to set it up for your team — scan to join the **Larkway 交流群** (QR never expires):
|
|
18
|
+
|
|
19
|
+
<img src="https://raw.githubusercontent.com/chuckwu0/larkway/main/assets/larkway-feishu-qr.jpg" width="260" alt="Larkway Feishu group QR" />
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
15
23
|
## Why
|
|
16
24
|
|
|
17
25
|
The engineers on your team know how a feature is actually implemented. Everyone else has to ask them. That friction compounds: a data analyst wondering whether a metric counts deleted records, a PM asking which API endpoint powers a chart, a QA engineer trying to reproduce a bug without context.
|
|
@@ -64,13 +72,11 @@ This boundary is intentional. Workflow changes go into your repository's agent g
|
|
|
64
72
|
|
|
65
73
|
## Quick start
|
|
66
74
|
|
|
67
|
-
>
|
|
75
|
+
> Install globally with npm:
|
|
68
76
|
>
|
|
69
77
|
> ```bash
|
|
70
|
-
> npm i -g
|
|
78
|
+
> npm i -g larkway
|
|
71
79
|
> ```
|
|
72
|
-
>
|
|
73
|
-
> Once published: `npm i -g larkway`
|
|
74
80
|
|
|
75
81
|
```bash
|
|
76
82
|
# 1. Check your environment
|
package/README.zh.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> 把你的 Claude Code 或 Codex 订阅变成全团队都能 @ 的飞书 Agent。
|
|
4
4
|
|
|
5
|
-
[English](README.md)
|
|
5
|
+
🌐 [larkway.dev](https://larkway.dev) · [English](README.md)
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
@@ -12,6 +12,14 @@
|
|
|
12
12
|
|
|
13
13
|
---
|
|
14
14
|
|
|
15
|
+
## 💬 交流群（飞书）
|
|
16
|
+
|
|
17
|
+
想看实际效果、聊聊怎么给你的团队搭 agent？扫码加入 **Larkway 交流群**（二维码永久有效）：
|
|
18
|
+
|
|
19
|
+
<img src="https://raw.githubusercontent.com/chuckwu0/larkway/main/assets/larkway-feishu-qr.jpg" width="260" alt="Larkway 交流群 飞书二维码" />
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
15
23
|
## 背景
|
|
16
24
|
|
|
17
25
|
工程师知道某个功能是怎么实现的，其他人不知道，只能问。这个摩擦不断叠加：数据分析师想弄清楚某个指标有没有过滤已删除的记录，PM 想知道某个图表背后调的是哪个 API，QA 工程师在没有上下文的情况下试图复现一个 bug。
|
|
@@ -64,13 +72,11 @@ lark.card ◄── agent 读仓库、跑 bash、改代码、
|
|
|
64
72
|
|
|
65
73
|
## 快速上手
|
|
66
74
|
|
|
67
|
-
>
|
|
75
|
+
> 全局安装：
|
|
68
76
|
>
|
|
69
77
|
> ```bash
|
|
70
|
-
> npm i -g
|
|
78
|
+
> npm i -g larkway
|
|
71
79
|
> ```
|
|
72
|
-
>
|
|
73
|
-
> 发布后可直接：`npm i -g larkway`
|
|
74
80
|
|
|
75
81
|
```bash
|
|
76
82
|
# 1. 检查环境
|