feat: 使用记录新增 effort 标识

[Hwwwww-dev]

[github-actions]

Thank you for this feature suggestion.

Analysis:

Based on my investigation of the codebase, adding an "effort" identifier to usage records is a feasible feature. Here is the current state and implementation considerations:

Current State:

The usage records are stored in the messageRequest table (src/drizzle/schema.ts, lines 426-551), which tracks request metadata including model, tokens, cost, cache usage, etc. However, there is currently no dedicated field for tracking the "effort" level used in requests.

Related Existing Code:

1. Codex Reasoning Effort - Already defined in src/types/provider.ts (lines 17-24):

   • Type: CodexReasoningEffortPreference with values: "inherit" | "none" | "minimal" | "low" | "medium" | "high" | "xhigh"
   • Provider-level override: codexReasoningEffortPreference field in providers table

2. Anthropic Adaptive Thinking Effort - Defined in src/types/provider.ts (lines 42-48):

   • Type: AnthropicAdaptiveThinkingEffort with values: "low" | "medium" | "high" | "max"
   • Config: AnthropicAdaptiveThinkingConfig with effort, modelMatchMode, and models fields

3. Codex API Response - src/app/v1/_lib/codex/types/response.ts (lines 28-31):

   • ReasoningConfig interface with effort?: "minimal" | "low" | "medium" | "high"

Implementation Considerations:

1. Schema Change: Would require adding a new column to messageRequest table, for example:

   • effortApplied: varchar('effort_applied', { length: 20 })
   • This would store the actual effort level used (not the provider preference, but the resolved value sent to the API)

2. Data Sources:

   • For Codex requests: Extract from reasoning.effort in the request body
   • For Anthropic requests: Extract from adaptive thinking configuration when applied

3. Frontend Display: The usage logs view (src/app/[locale]/dashboard/logs/) would need updates to display the effort column

4. Type Unification: Consider whether to use a unified effort type or separate fields for different API types (Codex vs Anthropic)

5. Existing Pattern: The specialSettings JSONB field (schema.ts line 476) already tracks applied overrides. One alternative approach is to extend SpecialSetting type (src/types/special-settings.ts) to include effort-related entries rather than adding a dedicated column.

Dependencies:

• Database migration (via bun run db:generate)
• Response handler updates (src/app/v1/_lib/proxy/response-handler.ts)
• Usage logs table UI updates (src/app/[locale]/dashboard/logs/_components/)
• i18n strings for 5 supported languages

---

Automated response from Claude AI