Problem

The OpenAI-compatible /v1/chat/completions endpoint always returns hardcoded zero token counts:

"usage": { "prompt_tokens": 0, "completion_tokens": 0, "total_tokens": 0 }

This makes it impossible for downstream consumers (pipeline runners, scripts, monitoring tools) to track per-request token consumption without using the full WebSocket session protocol.

Solution

Extract actual token counts from the agent command result (result.meta.agentMeta.usage) and return them in the HTTP response, using the existing normalizeUsage() utility from agents/usage.ts.

Changes

• src/gateway/openai-http.ts: Add resolveAgentUsage() function that extracts and normalizes token usage from the agent result, replacing the hardcoded zeros.

Impact

• Non-streaming /v1/chat/completions responses now include actual prompt_tokens and completion_tokens
• No breaking changes — the response shape is identical, just with real values
• Streaming responses are unaffected (usage tracking in SSE chunks is a separate concern)

Greptile Summary

Adds actual token usage reporting to the /v1/chat/completions endpoint by extracting usage data from agent command results and normalizing it using the existing normalizeUsage utility.

Changes:

• Imports normalizeUsage from agents/usage.ts
• Adds AgentCommandResult type that captures the meta.agentMeta.usage structure
• Implements resolveAgentUsage() function to extract and format token counts from agent results
• Replaces hardcoded zeros with resolveAgentUsage(result) in non-streaming responses

Note: Per PR description, streaming responses are intentionally excluded from this change.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is straightforward and well-isolated: it extracts existing usage data from agent results using the established normalizeUsage utility, with proper fallback to zero values when data is unavailable. The implementation correctly handles null/undefined values, and only affects non-streaming responses as intended. The type definitions are appropriate and consistent with existing patterns in the codebase.
• No files require special attention

_{Last reviewed commit: 25d2208}