@zxh126/pi-qqbot 1.3.2 → 1.3.3

package/README.md

@@ -117,7 +117,7 @@ Some extension commands never print into the conversation — they call `ctx.ui.
 
 | Command | What happens |
 |---|---|
-| `/usage [range]`, `/cost [range]` | re-dispatched as `/qq usage <range>`: the bridge runs the original `/usage` command, then reads the **fresh** `customType: "usage-report"` entry — first from `sessionManager.getEntries()`, and if that view has not picked up the append yet, straight from the tail of the session file — and renders it as text (requests, tokens, cache ratio, cost, per-model). **Usage unchanged** — keep sending `/usage today`. |
+| `/usage [range]`, `/cost [range]` | re-dispatched as `/qq usage <range>`: the bridge runs the original `/usage` command, then **polls** for the fresh `customType: "usage-report"` entry for up to 2 s (the append lands ~100 ms *after* `sendUserMessage()` resolves, so a single read always misses it), falling back to the tail of the session file, and renders it as text (requests, tokens, cache ratio, cost, per-model). **Usage unchanged** — keep sending `/usage today`. |
 | `/usage rate <value>`, `/usage rate auto` | really executed (they write `~/.pi/agent/pi-usage-report.json` / refresh the cached rate); the bridge then reads those files back and reports the resulting rate, so an invalid value shows up as "unchanged" |
 | `/mcp`, `/llama` | answered: they need host-TUI selection dialogs / browser login, so nothing is dispatched |
 

package/docs/README.zh-CN.md

@@ -115,7 +115,7 @@ TUI/RPC 前端。在 QQ 里的表现就是「已派发，然后没下文」。
 
 | 命令 | 现在发生什么 |
 |---|---|
-| `/usage [范围]`、`/cost [范围]` | 改派为 `/qq usage <范围>`：桥接先重跑原 `/usage` 命令，再取**本次新写入**的 `customType: "usage-report"` 条目（先读 `sessionManager.getEntries()` 的增量；发现另一个扩展的 `appendEntry` 还没反映到该视图时，直接读会话文件尾部），渲染成文本回 QQ（请求数/总 token/缓存比/费用/按模型）。**用法不变**，照旧发 `/usage today` |
+| `/usage [范围]`、`/cost [范围]` | 改派为 `/qq usage <范围>`：桥接先重跑原 `/usage` 命令，再**轮询等待**本次新写入的 `customType: "usage-report"` 条目（`appendEntry` 比 `sendUserMessage()` 返回晚约 100 ms，只读一次必然落空），最多等 2 秒，仍未命中才退回读会话文件尾部；然后渲染成文本回 QQ（请求数/总 token/缓存比/费用/按模型）。**用法不变**，照旧发 `/usage today` |
 | `/mcp`、`/llama` | 直接回执：它们需要主机 TUI 的选择框 / 浏览器登录，不会派发 |
 | `/usage rate <值>`、`/usage rate auto` | 会真的执行（写 `~/.pi/agent/pi-usage-report.json` / 刷新汇率缓存），桥接再读回文件确认新汇率，无效值会体现在“汇率未变”上；只发 `/usage rate` 与 `/usage help` 则本地直接回执，不执行命令 |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zxh126/pi-qqbot",
-  "version": "1.3.2",
+  "version": "1.3.3",
   "type": "module",
   "description": "Bridge the Pi coding agent into QQ private chats, with remote tool-call approval",
   "license": "MIT",

package/slash.ts

@@ -382,6 +382,13 @@ export function pickerExpired(picker: PickerState | null): boolean {
 /** pi-usage-report 写入 session 的 custom entry 类型（耦合点，约定值） */
 const USAGE_ENTRY_TYPE = "usage-report";
 
+/**
+ * appendEntry 的写入比 `sendUserMessage` 的 resolve 晚（实测 promise 183ms 返回，
+ * entry 在之后 ~100ms 才出现在 getEntries 里），所以必须轮询而不是只读一次。
+ */
+const USAGE_WAIT_TIMEOUT_MS = 2000;
+const USAGE_POLL_INTERVAL_MS = 100;
+
 /** pi-usage-report 的配置/汇率缓存（读回来确认：命令真的生效了，而不是口头应下） */
 const USAGE_SETTINGS_FILE = "pi-usage-report.json";
 const USAGE_RATE_FILE = "pi-usage-report-rate.json";
@@ -483,7 +490,7 @@ function readUsageEntryFromFile(file: string | undefined, since: number): any |
 			} catch {
 				continue;
 			}
-			if (entry?.type !== "custom" || entry?.customType !== USAGE_ENTRY_TYPE) continue;
+			if (!isUsageEntry(entry)) continue;
 			const when = entryTime(entry?.data?.generatedAt ?? entry?.timestamp);
 			return Number.isFinite(when) && when >= since ? entry : undefined;
 		}
@@ -504,6 +511,28 @@ function localStamp(value: unknown): string {
 	return `${pad(date.getMonth() + 1)}-${pad(date.getDate())} ${pad(date.getHours())}:${pad(date.getMinutes())}`;
 }
 
+const isUsageEntry = (entry: any): boolean =>
+	entry?.type === "custom" && entry?.customType === USAGE_ENTRY_TYPE;
+
+const sleep = (ms: number) => new Promise<void>((resolve) => setTimeout(resolve, ms));
+
+/**
+ * 等本次 /usage 写的报告出现：每 100ms 查一次 getEntries（最多 2s），
+ * 全程未命中再试一次会话文件（custom entry 可能很晚才落盘）。
+ */
+async function waitForUsageEntry(
+	ctx: any,
+	opts: { before: Set<unknown>; since: number; file?: string },
+): Promise<any | undefined> {
+	const deadline = Date.now() + USAGE_WAIT_TIMEOUT_MS;
+	while (Date.now() < deadline) {
+		const fresh = [...sessionEntries(ctx)].reverse().find((entry: any) => isUsageEntry(entry) && !opts.before.has(entry?.id));
+		if (fresh) return fresh;
+		await sleep(USAGE_POLL_INTERVAL_MS);
+	}
+	return readUsageEntryFromFile(opts.file, opts.since);
+}
+
 /** 把 pi-usage-report 的 ReportData 渲染成 QQ 可读的纯文本 */
 function formatUsage(data: any): string {
 	if (!data?.totals) return "用量报告为空。";
@@ -687,12 +716,8 @@ export async function runBridge(
 				reply(`统计失败：${String((error as any)?.message ?? error).slice(0, 200)}`);
 				return;
 			}
-			// 先看 sessionManager 的增量，再退回读会话文件（appendEntry 可能还没同步到视图）
-			const entry =
-				[...sessionEntries(ctx)]
-					.reverse()
-					.find((e: any) => e?.type === "custom" && e?.customType === USAGE_ENTRY_TYPE && !before.has(e?.id)) ??
-				readUsageEntryFromFile(file, since);
+			// 先轮询 getEntries 的增量（appendEntry 晚于 await 返回），超时再退回读会话文件
+			const entry = await waitForUsageEntry(ctx, { before, since, file });
 			if (!entry) {
 				reply("没拿到用量报告：/usage 已执行但找不到报告数据（可重试一次；若反复出现请把 pi-qqbot.log 尾部发我）。");
 				return;