chatccc 0.2.278 → 0.2.280

package/.agents/skills/create-chatccc-feishu-app/SKILL.md

@@ -5,7 +5,7 @@ description: Create, clone, or configure a Feishu enterprise self-built bot appl
 
 # Create a ChatCCC Feishu App
 
-Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the minimum requirement and the existing app named exactly lowercase `chatccc` as the configuration template.
+Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
 
 ## 1. Establish the target and authorization
 
@@ -21,13 +21,12 @@ Use the logged-in Feishu developer console to create and completely configure a
 3. Record its non-secret configuration:
    - app description and icon;
    - application capabilities, especially `机器人`;
-   - every granted permission and its identity type;
    - event and callback subscription modes;
    - every event and callback identifier;
    - version availability, external sharing choices, and release state.
 4. Never reveal, log, export to chat, or persist the template App Secret.
 
-Prefer current console data over a stale hard-coded list. At the time this workflow was verified, lowercase `chatccc` had 62 application-identity permissions, one user-identity permission, 12 application events, and one callback. Use those counts as a sanity check, not as a replacement for inspecting the template.
+Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
 
 ## 3. Create the target app
 
@@ -36,16 +35,17 @@ Prefer current console data over a stale hard-coded list. At the time this workf
 3. Click the final `创建` action only after confirmation.
 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
 
-## 4. Clone the complete ChatCCC configuration
+## 4. Configure the complete README-defined ChatCCC setup
 
 Perform the configuration in this order:
 
 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
-2. Clone permissions with `权限管理` > `批量处理` > `批量导入/导出权限`:
-   - export from lowercase `chatccc`;
-   - import into the target app;
-   - confirm all additions and verify both application-identity and user-identity totals;
-   - do not save the export JSON in the repository or chat.
+2. Configure permissions from the README, not from the lowercase template:
+   - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
+   - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
+   - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
+   - confirm all permission changes and complete any required administrator approval;
+   - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
    - `im.chat.disbanded_v1`
    - `im.chat.member.bot.added_v1`
@@ -62,7 +62,7 @@ Perform the configuration in this order:
 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
 5. Verify that every listed event shows a sufficient permission as `已开通`.
 
-The README minimum is the bot capability, relevant `im:` and `cardkit:` permissions, `im.message.receive_v1`, and `card.action.trigger`; a clone request requires the complete current template configuration, not only that minimum.
+The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
 
 ## 5. Create and publish a version
 
@@ -78,8 +78,8 @@ The README minimum is the bot capability, relevant `im:` and `cardkit:` permissi
 
 ## 6. Verify and hand off safely
 
-- Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, permission identity counts match, both subscription modes are long connection, event/callback identifiers match, and the version is published.
+- Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
 - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
-- Report the app name, App ID, capability, permission counts, event/callback counts, version, release state, and any remaining action.
+- Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
 - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
 - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.

package/.claude/skills/create-chatccc-feishu-app/SKILL.md

@@ -5,7 +5,7 @@ description: Create, clone, or configure a Feishu enterprise self-built bot appl
 
 # Create a ChatCCC Feishu App
 
-Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the minimum requirement and the existing app named exactly lowercase `chatccc` as the configuration template.
+Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
 
 ## 1. Establish the target and authorization
 
@@ -21,13 +21,12 @@ Use the logged-in Feishu developer console to create and completely configure a
 3. Record its non-secret configuration:
    - app description and icon;
    - application capabilities, especially `机器人`;
-   - every granted permission and its identity type;
    - event and callback subscription modes;
    - every event and callback identifier;
    - version availability, external sharing choices, and release state.
 4. Never reveal, log, export to chat, or persist the template App Secret.
 
-Prefer current console data over a stale hard-coded list. At the time this workflow was verified, lowercase `chatccc` had 62 application-identity permissions, one user-identity permission, 12 application events, and one callback. Use those counts as a sanity check, not as a replacement for inspecting the template.
+Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
 
 ## 3. Create the target app
 
@@ -36,16 +35,17 @@ Prefer current console data over a stale hard-coded list. At the time this workf
 3. Click the final `创建` action only after confirmation.
 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
 
-## 4. Clone the complete ChatCCC configuration
+## 4. Configure the complete README-defined ChatCCC setup
 
 Perform the configuration in this order:
 
 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
-2. Clone permissions with `权限管理` > `批量处理` > `批量导入/导出权限`:
-   - export from lowercase `chatccc`;
-   - import into the target app;
-   - confirm all additions and verify both application-identity and user-identity totals;
-   - do not save the export JSON in the repository or chat.
+2. Configure permissions from the README, not from the lowercase template:
+   - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
+   - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
+   - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
+   - confirm all permission changes and complete any required administrator approval;
+   - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
    - `im.chat.disbanded_v1`
    - `im.chat.member.bot.added_v1`
@@ -62,7 +62,7 @@ Perform the configuration in this order:
 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
 5. Verify that every listed event shows a sufficient permission as `已开通`.
 
-The README minimum is the bot capability, relevant `im:` and `cardkit:` permissions, `im.message.receive_v1`, and `card.action.trigger`; a clone request requires the complete current template configuration, not only that minimum.
+The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
 
 ## 5. Create and publish a version
 
@@ -78,8 +78,8 @@ The README minimum is the bot capability, relevant `im:` and `cardkit:` permissi
 
 ## 6. Verify and hand off safely
 
-- Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, permission identity counts match, both subscription modes are long connection, event/callback identifiers match, and the version is published.
+- Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
 - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
-- Report the app name, App ID, capability, permission counts, event/callback counts, version, release state, and any remaining action.
+- Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
 - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
 - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.

package/.cursor/skills/create-chatccc-feishu-app/SKILL.md

@@ -5,7 +5,7 @@ description: Create, clone, or configure a Feishu enterprise self-built bot appl
 
 # Create a ChatCCC Feishu App
 
-Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the minimum requirement and the existing app named exactly lowercase `chatccc` as the configuration template.
+Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
 
 ## 1. Establish the target and authorization
 
@@ -21,13 +21,12 @@ Use the logged-in Feishu developer console to create and completely configure a
 3. Record its non-secret configuration:
    - app description and icon;
    - application capabilities, especially `机器人`;
-   - every granted permission and its identity type;
    - event and callback subscription modes;
    - every event and callback identifier;
    - version availability, external sharing choices, and release state.
 4. Never reveal, log, export to chat, or persist the template App Secret.
 
-Prefer current console data over a stale hard-coded list. At the time this workflow was verified, lowercase `chatccc` had 62 application-identity permissions, one user-identity permission, 12 application events, and one callback. Use those counts as a sanity check, not as a replacement for inspecting the template.
+Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
 
 ## 3. Create the target app
 
@@ -36,16 +35,17 @@ Prefer current console data over a stale hard-coded list. At the time this workf
 3. Click the final `创建` action only after confirmation.
 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
 
-## 4. Clone the complete ChatCCC configuration
+## 4. Configure the complete README-defined ChatCCC setup
 
 Perform the configuration in this order:
 
 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
-2. Clone permissions with `权限管理` > `批量处理` > `批量导入/导出权限`:
-   - export from lowercase `chatccc`;
-   - import into the target app;
-   - confirm all additions and verify both application-identity and user-identity totals;
-   - do not save the export JSON in the repository or chat.
+2. Configure permissions from the README, not from the lowercase template:
+   - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
+   - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
+   - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
+   - confirm all permission changes and complete any required administrator approval;
+   - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
    - `im.chat.disbanded_v1`
    - `im.chat.member.bot.added_v1`
@@ -62,7 +62,7 @@ Perform the configuration in this order:
 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
 5. Verify that every listed event shows a sufficient permission as `已开通`.
 
-The README minimum is the bot capability, relevant `im:` and `cardkit:` permissions, `im.message.receive_v1`, and `card.action.trigger`; a clone request requires the complete current template configuration, not only that minimum.
+The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
 
 ## 5. Create and publish a version
 
@@ -78,8 +78,8 @@ The README minimum is the bot capability, relevant `im:` and `cardkit:` permissi
 
 ## 6. Verify and hand off safely
 
-- Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, permission identity counts match, both subscription modes are long connection, event/callback identifiers match, and the version is published.
+- Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
 - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
-- Report the app name, App ID, capability, permission counts, event/callback counts, version, release state, and any remaining action.
+- Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
 - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
 - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.

package/README.md

@@ -182,12 +182,15 @@ npm run dev
 
 1. 打开 [飞书开放平台](https://open.feishu.cn)，创建一个**企业自建应用**。
 2. 在「应用功能」里开启**机器人**能力。
-3. 在「权限管理」里开通 `im:` 和 `cardkit:` 前缀下的相关权限：
+3. 在「权限管理」里开通**所有权限名称以 `im:` 或 `cardkit:` 开头的权限**。不要只依赖事件页面自动推荐的权限；开通后应分别搜索这两个前缀并逐项确认：
 
 | 前缀 | 用途 |
 | --- | --- |
-| `im:` | 收发消息、创建和管理群聊、机器人发言 |
-| `cardkit:` | 卡片展示、流式更新、按钮和交互回调 |
+| `im:` | 全部开通，用于收发消息、创建和管理群聊、机器人发言等 |
+| `cardkit:` | 全部开通，用于卡片展示、流式更新、按钮和交互回调等 |
+
+> [!IMPORTANT]
+> 请额外单独搜索并确认已开通 `im:message.p2p_msg:readonly`（获取用户发给机器人的单聊消息）。这个权限在飞书开发者后台配置时容易遗漏；缺少它可能导致 ChatCCC 无法正常识别或处理私聊消息。
 
 <p align="center">
   <img src="images/img_readme_permission.png" alt="飞书应用权限配置" width="280" />
@@ -427,7 +430,7 @@ Codex 的默认模型和推理强度可继续由 `~/.codex/config.toml` 管理
 | `/cd` | 查看或设置后续新建会话的默认工作目录，不改变当前会话；飞书私聊自身始终使用系统用户目录 |
 | `/sessions` | 查看所有会话状态 |
 | `/session <数字>` | 将当前群聊切换到 `/sessions` 列表中的指定会话；飞书私聊不支持切换 |
-| `/usage` | 查看当前会话对应 Agent 的用量；Codex 显示 5h/7天窗口，Cursor 显示当前周期用量，CCC Agent 和 DSH 仅在官方 DeepSeek 端点时显示账户余额（其他兼容端点自动跳过） |
+| `/usage` | 查看当前会话对应 Agent 的用量；Codex 显示 5h/7天窗口，主动重置次数查询失败时会明确展示上次成功快照及其查询时间（缓存结果不提供重置按钮）；Cursor 显示当前周期用量，CCC Agent 和 DSH 仅在官方 DeepSeek 端点时显示账户余额（其他兼容端点自动跳过） |
 | `/git <子命令>` | 在当前会话工作目录执行 `git ...` 并回传输出 |
 | `/abd<内容>` | 去掉 `/abd` 前缀后把内容发给 Agent，并在消息末尾追加第一性原理需求澄清提示 |
 | `/plan <内容>` | 只读计划模式：仅允许读文件和 stop-stuck-loop 请求，不执行任何写操作 |

package/dist/src/codex-reset-credits-cache.js

@@ -0,0 +1,105 @@
+import { createHash, randomUUID } from "node:crypto";
+import { mkdir, readFile, rename, rm, writeFile } from "node:fs/promises";
+import { dirname, join } from "node:path";
+import { USER_DATA_DIR } from "./config.js";
+const CACHE_FILE = join(USER_DATA_DIR, "state", "codex-reset-credits.json");
+let mutationQueue = Promise.resolve();
+export function codexResetCreditsAccountKey(accountId, accessToken) {
+    if (accountId?.trim())
+        return `account:${accountId.trim()}`;
+    const digest = createHash("sha256").update(accessToken).digest("hex").slice(0, 24);
+    return `token-sha256:${digest}`;
+}
+function emptyCache() {
+    return { version: 1, accounts: {} };
+}
+function normalizeSnapshot(raw) {
+    if (!raw || typeof raw !== "object")
+        return null;
+    const value = raw;
+    const availableCount = Number(value.availableCount);
+    if (!Number.isFinite(availableCount) || typeof value.queriedAt !== "string" || !value.queriedAt.trim())
+        return null;
+    const credits = Array.isArray(value.credits)
+        ? value.credits.flatMap((credit) => {
+            if (!credit || typeof credit !== "object")
+                return [];
+            const item = credit;
+            if (typeof item.expiresAt !== "string" || !item.expiresAt.trim())
+                return [];
+            return [{
+                    grantedAt: typeof item.grantedAt === "string" && item.grantedAt.trim() ? item.grantedAt : null,
+                    expiresAt: item.expiresAt,
+                }];
+        })
+        : [];
+    return {
+        availableCount: Math.max(0, Math.trunc(availableCount)),
+        credits,
+        queriedAt: value.queriedAt,
+        locallyAdjusted: value.locallyAdjusted === true,
+    };
+}
+async function readCache() {
+    try {
+        const parsed = JSON.parse(await readFile(CACHE_FILE, "utf-8"));
+        const accounts = {};
+        if (parsed.accounts && typeof parsed.accounts === "object") {
+            for (const [key, raw] of Object.entries(parsed.accounts)) {
+                const snapshot = normalizeSnapshot(raw);
+                if (snapshot)
+                    accounts[key] = snapshot;
+            }
+        }
+        return { version: 1, accounts };
+    }
+    catch {
+        return emptyCache();
+    }
+}
+async function writeCache(cache) {
+    await mkdir(dirname(CACHE_FILE), { recursive: true });
+    const tempFile = `${CACHE_FILE}.${process.pid}.${randomUUID()}.tmp`;
+    await writeFile(tempFile, JSON.stringify(cache, null, 2), "utf-8");
+    try {
+        await rename(tempFile, CACHE_FILE);
+    }
+    catch {
+        await writeFile(CACHE_FILE, JSON.stringify(cache, null, 2), "utf-8");
+        await rm(tempFile, { force: true }).catch(() => { });
+    }
+}
+async function mutateCache(mutate) {
+    const operation = mutationQueue.then(async () => {
+        const cache = await readCache();
+        mutate(cache);
+        await writeCache(cache);
+    });
+    mutationQueue = operation.catch(() => { });
+    return operation;
+}
+export async function readCodexResetCreditsSnapshot(accountKey) {
+    return (await readCache()).accounts[accountKey] ?? null;
+}
+export async function saveCodexResetCreditsSnapshot(accountKey, snapshot) {
+    await mutateCache((cache) => {
+        cache.accounts[accountKey] = {
+            ...snapshot,
+            availableCount: Math.max(0, Math.trunc(snapshot.availableCount)),
+            locallyAdjusted: false,
+        };
+    });
+}
+export async function decrementCachedCodexResetCredits(accountKey) {
+    await mutateCache((cache) => {
+        const current = cache.accounts[accountKey];
+        if (!current)
+            return;
+        cache.accounts[accountKey] = {
+            ...current,
+            availableCount: Math.max(0, current.availableCount - 1),
+            credits: current.credits.slice(1),
+            locallyAdjusted: true,
+        };
+    });
+}

package/dist/src/feishu-api.js

@@ -6,6 +6,7 @@ import sharp from "sharp";
 import { APP_ID, APP_SECRET, BASE_URL, CHAT_LOGS_DIR, PROJECT_ROOT, USER_DATA_DIR, CLAUDE_SESSION_PREFIX, CURSOR_SESSION_PREFIX, CODEX_SESSION_PREFIX, CCC_SESSION_PREFIX, DSH_SESSION_PREFIX, ts, resolveDefaultAgentTool, toolDisplayName, config, } from "./config.js";
 import { getCursorUsageSummary } from "./cursor-usage.js";
 import { applyPrivacy } from "./privacy.js";
+import { codexResetCreditsAccountKey, decrementCachedCodexResetCredits, readCodexResetCreditsSnapshot, saveCodexResetCreditsSnapshot, } from "./codex-reset-credits-cache.js";
 import { buildHelpCard } from "./cards.js";
 // ---------------------------------------------------------------------------
 // Auth
@@ -366,9 +367,6 @@ async function getCodexAuth() {
         return null;
     }
 }
-async function getCodexAccessToken() {
-    return (await getCodexAuth())?.accessToken ?? null;
-}
 function codexAuthHeaders(auth) {
     const headers = {
         Authorization: `Bearer ${auth.accessToken}`,
@@ -399,26 +397,42 @@ function parseCodexResetCreditDetails(data) {
         }),
     };
 }
+const codexResetCreditsInFlight = new Map();
 async function fetchCodexRateLimitResetCredits(auth) {
-    try {
-        const resp = await fetch(CODEX_RESET_CREDITS_URL, {
-            headers: codexAuthHeaders(auth),
-        });
-        const text = await resp.text();
-        if (!resp.ok)
-            throw new Error(`HTTP ${resp.status}: ${text.slice(0, 160)}`);
-        return parseCodexResetCreditDetails(JSON.parse(text));
-    }
-    catch (err) {
-        console.warn(`[Codex] reset credits lookup failed: ${err.message}`);
-        return null;
-    }
+    const accountKey = codexResetCreditsAccountKey(auth.accountId, auth.accessToken);
+    const existing = codexResetCreditsInFlight.get(accountKey);
+    if (existing)
+        return existing;
+    const lookup = (async () => {
+        try {
+            const resp = await fetch(CODEX_RESET_CREDITS_URL, {
+                headers: codexAuthHeaders(auth),
+            });
+            const text = await resp.text();
+            if (!resp.ok)
+                throw new Error(`HTTP ${resp.status}: ${text.slice(0, 160)}`);
+            return {
+                details: parseCodexResetCreditDetails(JSON.parse(text)),
+                error: null,
+            };
+        }
+        catch (err) {
+            const error = err.message;
+            console.warn(`[Codex] reset credits lookup failed: ${error}`);
+            return { details: null, error };
+        }
+    })().finally(() => {
+        codexResetCreditsInFlight.delete(accountKey);
+    });
+    codexResetCreditsInFlight.set(accountKey, lookup);
+    return lookup;
 }
-export async function getCodexUsageSummary() {
+export async function getCodexUsageSummary(options = {}) {
     const auth = await getCodexAuth();
     if (!auth)
         throw new Error("missing ~/.codex/auth.json access token");
-    const resetCreditsPromise = fetchCodexRateLimitResetCredits(auth);
+    const includeResetCredits = options.includeResetCredits !== false;
+    const resetCreditsPromise = includeResetCredits ? fetchCodexRateLimitResetCredits(auth) : null;
     const resp = await fetch(CODEX_USAGE_URL, {
         headers: { Authorization: `Bearer ${auth.accessToken}` },
     });
@@ -443,24 +457,77 @@ export async function getCodexUsageSummary() {
         ?? (primaryWindow?.limitWindowSeconds === undefined ? primaryWindow : null);
     const weekly = windows.find((window) => isUsageWindowDuration(window, SEVEN_DAY_WINDOW_SECONDS))
         ?? (secondaryWindow?.limitWindowSeconds === undefined ? secondaryWindow : null);
-    const resetCredits = await resetCreditsPromise;
+    if (!includeResetCredits) {
+        return {
+            fiveHour,
+            weekly,
+            rateLimitResetCreditsAvailable: null,
+            rateLimitResetCredits: null,
+            rateLimitResetCreditsSource: "not_requested",
+            rateLimitResetCreditsQueriedAt: null,
+            rateLimitResetCreditsLocallyAdjusted: false,
+            rateLimitResetCreditsError: null,
+        };
+    }
+    const accountKey = codexResetCreditsAccountKey(auth.accountId, auth.accessToken);
+    const resetLookup = await resetCreditsPromise;
+    const embeddedAvailableCount = parseRateLimitResetCredits(data);
+    const liveAvailableCount = resetLookup.details?.availableCount ?? embeddedAvailableCount;
+    if (liveAvailableCount !== null) {
+        const queriedAt = new Date().toISOString();
+        const liveCredits = resetLookup.details?.availableCredits ?? [];
+        await saveCodexResetCreditsSnapshot(accountKey, {
+            availableCount: liveAvailableCount,
+            credits: liveCredits,
+            queriedAt,
+        }).catch((err) => {
+            console.warn(`[Codex] reset credits snapshot write failed: ${err.message}`);
+        });
+        return {
+            fiveHour,
+            weekly,
+            rateLimitResetCreditsAvailable: liveAvailableCount,
+            rateLimitResetCredits: liveCredits,
+            rateLimitResetCreditsSource: "live",
+            rateLimitResetCreditsQueriedAt: queriedAt,
+            rateLimitResetCreditsLocallyAdjusted: false,
+            rateLimitResetCreditsError: null,
+        };
+    }
+    const cached = await readCodexResetCreditsSnapshot(accountKey);
+    if (cached) {
+        return {
+            fiveHour,
+            weekly,
+            rateLimitResetCreditsAvailable: cached.availableCount,
+            rateLimitResetCredits: cached.credits,
+            rateLimitResetCreditsSource: "cache",
+            rateLimitResetCreditsQueriedAt: cached.queriedAt,
+            rateLimitResetCreditsLocallyAdjusted: cached.locallyAdjusted,
+            rateLimitResetCreditsError: resetLookup.error ?? "OpenAI returned no reset-credit data",
+        };
+    }
     return {
         fiveHour,
         weekly,
-        rateLimitResetCreditsAvailable: resetCredits?.availableCount ?? parseRateLimitResetCredits(data),
-        rateLimitResetCredits: resetCredits?.availableCredits ?? null,
+        rateLimitResetCreditsAvailable: null,
+        rateLimitResetCredits: null,
+        rateLimitResetCreditsSource: "unavailable",
+        rateLimitResetCreditsQueriedAt: null,
+        rateLimitResetCreditsLocallyAdjusted: false,
+        rateLimitResetCreditsError: resetLookup.error ?? "OpenAI returned no reset-credit data",
     };
 }
 export async function consumeCodexRateLimitResetCredit(redeemRequestId) {
     if (!redeemRequestId.trim())
         throw new Error("missing redeem_request_id");
-    const token = await getCodexAccessToken();
-    if (!token)
+    const auth = await getCodexAuth();
+    if (!auth)
         throw new Error("missing ~/.codex/auth.json access token");
     const resp = await fetch(CODEX_RESET_CONSUME_URL, {
         method: "POST",
         headers: {
-            Authorization: `Bearer ${token}`,
+            Authorization: `Bearer ${auth.accessToken}`,
             "Content-Type": "application/json",
         },
         body: JSON.stringify({ redeem_request_id: redeemRequestId }),
@@ -477,10 +544,17 @@ export async function consumeCodexRateLimitResetCredit(redeemRequestId) {
         throw new Error("missing or unknown reset result code");
     }
     const windowsReset = Number(data.windows_reset);
-    return {
+    const result = {
         code,
         windowsReset: Number.isFinite(windowsReset) ? Math.max(0, Math.trunc(windowsReset)) : 0,
     };
+    if (result.code === "reset") {
+        const accountKey = codexResetCreditsAccountKey(auth.accountId, auth.accessToken);
+        await decrementCachedCodexResetCredits(accountKey).catch((err) => {
+            console.warn(`[Codex] reset credits snapshot update failed: ${err.message}`);
+        });
+    }
+    return result;
 }
 async function resolveCodexAvatarUsage(usageHint) {
     if (usageHint !== undefined) {
@@ -489,7 +563,7 @@ async function resolveCodexAvatarUsage(usageHint) {
         return usageHint;
     }
     try {
-        const summary = await getCodexUsageSummary();
+        const summary = await getCodexUsageSummary({ includeResetCredits: false });
         if (!summary.weekly)
             throw new Error("missing weekly usage window");
         return summary;

package/dist/src/orchestrator.js

@@ -100,33 +100,69 @@ function formatCodexUsageSummary(usage, chatGptSubscription = null) {
         ].join("\n");
     };
     const formatResetCredits = () => {
+        const formatDateTime = (value) => {
+            const date = new Date(value);
+            if (!Number.isFinite(date.getTime()))
+                return value;
+            const pad = (part) => String(part).padStart(2, "0");
+            return [
+                date.getFullYear(),
+                "-",
+                pad(date.getMonth() + 1),
+                "-",
+                pad(date.getDate()),
+                " ",
+                pad(date.getHours()),
+                ":",
+                pad(date.getMinutes()),
+                ":",
+                pad(date.getSeconds()),
+            ].join("");
+        };
+        const failureReason = () => {
+            const raw = usage.rateLimitResetCreditsError?.replace(/\s+/g, " ").trim();
+            if (!raw)
+                return "OpenAI 未返回主动重置数据";
+            if (/HTTP 429/i.test(raw))
+                return "OpenAI 返回 HTTP 429（请求受限）";
+            if (/HTTP 404/i.test(raw))
+                return "OpenAI 返回 HTTP 404（接口暂不可用）";
+            return raw.length > 180 ? `${raw.slice(0, 180)}...` : raw;
+        };
+        const source = usage.rateLimitResetCreditsSource ?? "live";
+        if (source === "unavailable") {
+            return [
+                `**主动重置:** 本次查询失败（${failureReason()}）`,
+                "- 没有可用的历史缓存结果",
+            ].join("\n");
+        }
+        if (source === "cache") {
+            const lines = [
+                `**主动重置:** 本次查询失败（${failureReason()}）`,
+                `**上次缓存结果:** 剩余 ${usage.rateLimitResetCreditsAvailable ?? 0} 次`,
+            ];
+            if (usage.rateLimitResetCreditsQueriedAt) {
+                lines.push(`- 查询时间: ${formatDateTime(usage.rateLimitResetCreditsQueriedAt)}`);
+            }
+            if (usage.rateLimitResetCreditsLocallyAdjusted) {
+                lines.push("- 状态: 本地推算，待下次查询确认");
+            }
+            const credits = usage.rateLimitResetCredits ?? [];
+            if (credits.length > 0) {
+                lines.push("**缓存中的过期时间:**");
+                for (const credit of credits)
+                    lines.push(`- ${formatDateTime(credit.expiresAt)}`);
+            }
+            return lines.join("\n");
+        }
         if (usage.rateLimitResetCreditsAvailable === null)
             return "**主动重置:** 暂无数据";
         const lines = [`**主动重置:** 剩余 ${usage.rateLimitResetCreditsAvailable} 次`];
         const credits = usage.rateLimitResetCredits ?? [];
         if (credits.length > 0) {
-            const pad = (value) => String(value).padStart(2, "0");
-            const formatExpiresAt = (value) => {
-                const date = new Date(value);
-                if (!Number.isFinite(date.getTime()))
-                    return value;
-                return [
-                    date.getFullYear(),
-                    "-",
-                    pad(date.getMonth() + 1),
-                    "-",
-                    pad(date.getDate()),
-                    " ",
-                    pad(date.getHours()),
-                    ":",
-                    pad(date.getMinutes()),
-                    ":",
-                    pad(date.getSeconds()),
-                ].join("");
-            };
             lines.push("**过期时间:**");
             for (const credit of credits) {
-                lines.push(`- ${formatExpiresAt(credit.expiresAt)}`);
+                lines.push(`- ${formatDateTime(credit.expiresAt)}`);
             }
         }
         return lines.join("\n");
@@ -397,7 +433,11 @@ async function sendUsageSummary(platform, chatId, tool, avatarStatus = "idle", s
         await platform.sendText(chatId, content).catch(() => { });
     }
     else if (platform.kind === "feishu") {
-        await platform.sendRawCard(chatId, buildCodexUsageCard(content, usage.rateLimitResetCreditsAvailable));
+        const liveResetCredits = usage.rateLimitResetCreditsSource === undefined
+            || usage.rateLimitResetCreditsSource === "live"
+            ? usage.rateLimitResetCreditsAvailable
+            : null;
+        await platform.sendRawCard(chatId, buildCodexUsageCard(content, liveResetCredits));
     }
     else {
         await platform.sendCard(chatId, "Codex Usage", content, "blue");

package/dist/src/sim-platform.js

@@ -105,6 +105,10 @@ export const SimulatedPlatform = {
             weekly: { usedPercent: 0, remainingPercent: 100, resetAtEpochSeconds: null, resetAfterSeconds: null },
             rateLimitResetCreditsAvailable: null,
             rateLimitResetCredits: null,
+            rateLimitResetCreditsSource: "unavailable",
+            rateLimitResetCreditsQueriedAt: null,
+            rateLimitResetCreditsLocallyAdjusted: false,
+            rateLimitResetCreditsError: "Simulated platform has no reset-credit data",
         };
     },
     async consumeCodexRateLimitResetCredit(_redeemRequestId) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chatccc",
-  "version": "0.2.278",
+  "version": "0.2.280",
   "description": "Feishu bot bridge for Claude Code",
   "license": "Apache-2.0",
   "type": "module",