feat(status): add API call count to session status and usage footer by Qixingchen · Pull Request #48851 · openclaw/openclaw

Qixingchen · 2026-03-17T08:18:07Z

track API call count per run in embedded runner
persist per-run call count on session entries
show current-turn call count in /status output
show current-turn call count in response usage footer
keep calls semantics aligned with current-turn token usage
add/update unit tests for API call count display

Summary

Problem: Users cannot see how many API calls were made per turn, only token usage
Why it matters: Some providers charge per call; helps debug usage patterns and understand tool-call loops
What changed: Added callCount tracking in the embedded runner, persisted to session entry, displayed in both /status and response usage footer
What did NOT change: Token counting, cost calculation, existing status fields, cumulative session statistics

Change Type

Scope

Linked Issue/PR

Closes [Feature]: Add API call count to status/usage output #48779

User-visible / Behavior Changes

/status output now includes 📞 Calls: N in the usage line (current turn only)
Response usage footer now includes 📞 Calls: N when responseUsage is enabled (current turn only)
Call count reflects actual API calls in the current turn (including tool-use loops)
No config changes; no new settings

Security Impact

New permissions/capabilities? No
Secrets/tokens handling changed? No
New/changed network calls? No
Command/tool execution surface changed? No
Data access scope changed? No

Repro + Verification

Environment

OS: Linux (Ubuntu 22.04)
Runtime/container: Node.js v22
Model/provider: Any
Integration/channel: Any

Steps

Run /status command in any session with prior activity
Observe the usage line includes 📞 Calls: N
Enable responseUsage: full in config
Send a message and observe usage footer includes call count
Trigger tool calls and verify count increases per API call

Expected

🧮 Tokens: 154k in / 656 out · 💵 Cost: $0.40 · 📞 Calls: 3

Actual

Works as expected.

Evidence

Passing unit tests
- src/auto-reply/status.test.ts - "shows API call count from the latest run"
- src/auto-reply/reply/agent-runner-utils.test.ts - "formats response usage line with API call count"

Human Verification

Verified scenarios: Unit tests pass; code review completed
Edge cases checked: Zero calls, single call, multiple tool calls
What you did not verify: Live integration test (requires local build and gateway restart)

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.
I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

Backward compatible? Yes
Config/env changes? No
Migration needed? No

Failure Recovery

How to disable/revert this change quickly: Revert the commit
Files/config to restore: None
Known bad symptoms reviewers should watch for: None

Risks and Mitigations

None. This is a display-only feature with no side effects.

- track API call count per run in embedded runner - persist per-run call count on session entries - show current-turn call count in /status output - show current-turn call count in response usage footer - keep calls semantics aligned with current-turn token usage - add/update unit tests for API call count display

greptile-apps · 2026-03-17T08:20:28Z

Greptile Summary

This PR adds API call count tracking (callCount) per turn through the entire stack: embedded runner → session entry → /status display and response usage footer. The implementation is clean and well-tested, with one meaningful gap in followup-runner.ts where the new field is not forwarded to persistRunSessionUsage, causing followup-turn call counts to be silently dropped.

callCount is correctly incremented in UsageAccumulator and propagated through EmbeddedPiAgentMeta on both success and error paths.
agent-runner.ts correctly passes callCount to both persistRunSessionUsage and formatResponseUsageLine.
followup-runner.ts omits callCount from its persistRunSessionUsage call, so after a followup turn the session entry retains the stale callCount from the prior main turn instead of the followup's actual count.
The refactored usageCostLine builder in status.ts using filter(Boolean).join(" · ") is a clean improvement and remains functionally equivalent for the existing cases.
Test coverage for both the formatter and the status message is solid.

Confidence Score: 3/5

Safe to merge with one caveat: followup turns silently drop the call count, leading to stale display in /status.
All display and persistence logic in the main turn path is correct. The one gap is followup-runner.ts not forwarding callCount to persistRunSessionUsage, which produces a misleading call count in /status after any followup turn. It's a one-line fix but does affect correctness of the feature for a common code path.
src/auto-reply/reply/followup-runner.ts — missing callCount in the persistRunSessionUsage call at line 268.

Comments Outside Diff (1)

src/auto-reply/reply/followup-runner.ts, line 268-279 (link)

callCount not persisted for followup turns

persistRunSessionUsage is called here without callCount, so when a followup turn runs (e.g., triggered by a tool-call loop), the API call count for that turn is silently dropped. Because session-usage.ts only writes callCount when the param is present and > 0, the session entry will retain the stale callCount from the previous main turn instead of reflecting the followup turn's actual call count. This means /status will show a misleading (too-low or too-high) call count after any followup turn.

The same field is correctly passed in agent-runner.ts at line 479.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/auto-reply/reply/followup-runner.ts
Line: 268-279

Comment:
**`callCount` not persisted for followup turns**

`persistRunSessionUsage` is called here without `callCount`, so when a followup turn runs (e.g., triggered by a tool-call loop), the API call count for that turn is silently dropped. Because `session-usage.ts` only writes `callCount` when the param is present and `> 0`, the session entry will retain the stale `callCount` from the previous main turn instead of reflecting the followup turn's actual call count. This means `/status` will show a misleading (too-low or too-high) call count after any followup turn.

The same field is correctly passed in `agent-runner.ts` at line 479.



How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/auto-reply/reply/followup-runner.ts
Line: 268-279

Comment:
**`callCount` not persisted for followup turns**

`persistRunSessionUsage` is called here without `callCount`, so when a followup turn runs (e.g., triggered by a tool-call loop), the API call count for that turn is silently dropped. Because `session-usage.ts` only writes `callCount` when the param is present and `> 0`, the session entry will retain the stale `callCount` from the previous main turn instead of reflecting the followup turn's actual call count. This means `/status` will show a misleading (too-low or too-high) call count after any followup turn.

The same field is correctly passed in `agent-runner.ts` at line 479.

```suggestion
        await persistRunSessionUsage({
          storePath,
          sessionKey,
          usage,
          lastCallUsage: runResult.meta?.agentMeta?.lastCallUsage,
          promptTokens,
          modelUsed,
          providerUsed: fallbackProvider,
          contextTokensUsed,
          systemPromptReport: runResult.meta?.systemPromptReport,
          callCount: runResult.meta?.agentMeta?.callCount,
          logLabel: "followup",
        });
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: 0436875}

Copilot

Pull request overview

Adds per-turn API call count tracking to the embedded agent runner and surfaces it in user-facing status/usage output, complementing existing per-turn token usage reporting.

Changes:

Introduces callCount on embedded runner metadata and persists it onto SessionEntry.
Displays 📞 Calls: N in /status and in the response usage footer.
Adds/updates unit tests covering call count formatting in both outputs.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/config/sessions/types.ts	Adds `SessionEntry.callCount` to persist last-run (current turn) API call count.
src/auto-reply/status.ts	Includes `📞 Calls: N` in the `/status` usage line when available.
src/auto-reply/status.test.ts	Tests that `/status` includes call count from the latest run.
src/auto-reply/reply/session-usage.ts	Persists `callCount` onto session store entries.
src/auto-reply/reply/agent-runner.ts	Plumbs runner `callCount` into session persistence and usage-footer formatting.
src/auto-reply/reply/agent-runner-utils.ts	Extends usage footer formatting to include call count.
src/auto-reply/reply/agent-runner-utils.test.ts	Tests usage footer formatting with call count.
src/agents/pi-embedded-runner/types.ts	Adds `callCount` to embedded runner agent meta type.
src/agents/pi-embedded-runner/run.ts	Tracks and reports per-run API call count via the usage accumulator.

You can also share your feedback on Copilot code review. Take the survey.

src/auto-reply/reply/session-usage.ts

src/agents/pi-embedded-runner/run.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0436875ad3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

src/agents/pi-embedded-runner/run.ts

src/auto-reply/reply/session-usage.ts

Bot review feedback: callCount was missing in followup-runner.ts persistRunSessionUsage call, causing stale count after followup turns. This aligns with how usage/lastCallUsage are already handled there.

- Add callCount tracking in subscribeEmbeddedPiSession (incremented on each recordAssistantUsage call, i.e., each LLM API response with usage data) - Add attemptCallCount to EmbeddedRunAttemptResult - Pass callCount from attempt to run.ts and accumulate properly - Add tests for callCount accumulation scenarios This fixes the issue where callCount only counted attempts, not individual API calls within tool-call loops.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 50b4858035

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

src/agents/pi-embedded-subscribe.ts

Copilot AI review requested due to automatic review settings March 17, 2026 08:18

openclaw-barnacle bot added agents Agent runtime and tooling size: S labels Mar 17, 2026

Copilot started reviewing on behalf of Qixingchen March 17, 2026 08:18 View session

Copilot AI reviewed Mar 17, 2026

View reviewed changes

src/auto-reply/reply/session-usage.ts Show resolved Hide resolved

src/agents/pi-embedded-runner/run.ts Outdated Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Mar 17, 2026

View reviewed changes

src/agents/pi-embedded-runner/run.ts Outdated Show resolved Hide resolved

src/auto-reply/reply/session-usage.ts Show resolved Hide resolved

hoshi_lan added 2 commits March 17, 2026 16:37

fix: persist callCount in followup-runner to match token handling

b3b513e

Bot review feedback: callCount was missing in followup-runner.ts persistRunSessionUsage call, causing stale count after followup turns. This aligns with how usage/lastCallUsage are already handled there.

chatgpt-codex-connector bot reviewed Mar 17, 2026

View reviewed changes

src/agents/pi-embedded-subscribe.ts Show resolved Hide resolved

ademczuk mentioned this pull request Mar 18, 2026

fix(security): block build-tool and glibc env injection vectors in host exec sandbox #49702

Merged

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(status): add API call count to session status and usage footer#48851

feat(status): add API call count to session status and usage footer#48851
Qixingchen wants to merge 3 commits intoopenclaw:mainfrom
Qixingchen:feat/api-call-count

Qixingchen commented Mar 17, 2026 •

edited

Loading

Uh oh!

greptile-apps bot commented Mar 17, 2026 •

edited

Loading

Comments Outside Diff (1)

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

Qixingchen commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type

Scope

Linked Issue/PR

User-visible / Behavior Changes

Security Impact

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification

Review Conversations

Compatibility / Migration

Failure Recovery

Risks and Mitigations

Uh oh!

greptile-apps bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 3/5

Comments Outside Diff (1)

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Qixingchen commented Mar 17, 2026 •

edited

Loading

greptile-apps bot commented Mar 17, 2026 •

edited

Loading