Skip to content

Commit f7249fb

Browse files
committed
/status: show usage fetch errors instead of silently hiding
Improves UX by showing why usage info is missing. - Display provider API errors (e.g., timeout, auth failure) - Show structured errors from usage summary responses - Users no longer left wondering if usage tracking is broken - Better debugging signal for rate-limit/API issues
1 parent 055a8b7 commit f7249fb

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

src/auto-reply/reply/commands-status.ts

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,9 @@ export async function buildStatusReply(params: {
9494
agentDir: statusAgentDir,
9595
});
9696
const usageEntry = usageSummary.providers[0];
97-
if (usageEntry && !usageEntry.error && usageEntry.windows.length > 0) {
97+
if (usageEntry && usageEntry.error) {
98+
usageLine = `📊 Usage: (unavailable: ${usageEntry.error})`;
99+
} else if (usageEntry && usageEntry.windows.length > 0) {
98100
const summaryLine = formatUsageWindowSummary(usageEntry, {
99101
now: Date.now(),
100102
maxWindows: 2,
@@ -104,8 +106,9 @@ export async function buildStatusReply(params: {
104106
usageLine = `📊 Usage: ${summaryLine}`;
105107
}
106108
}
107-
} catch {
108-
usageLine = null;
109+
} catch (err) {
110+
const errorMessage = err instanceof Error ? err.message : "unknown error";
111+
usageLine = `📊 Usage: (error: ${errorMessage})`;
109112
}
110113
}
111114
const queueSettings = resolveQueueSettings({

0 commit comments

Comments
 (0)