fix: land multi-agent session path fix + regressions (#15103) by steipete · Pull Request #15448 · openclaw/openclaw

steipete · 2026-02-13T13:17:19Z

Follow-up landing for closed #15103.

What this includes:

Rebased session-path agentId fixes onto current main.
Regression tests for multi-agent/non-main transcript path resolution.
Changelog note with contributor credit.

Co-authored-by: Josh Lehman [email protected]
Thanks @jalehman.

Greptile Overview

Greptile Summary

This PR primarily threads agentId through status/usage/session-cost transcript path resolution so non-default agents can resolve absolute session transcript files without failing path validation. It also adds regression tests covering status transcript usage and gateway usage APIs for agent:<id>:<sessionId> keys.

One behavioral change in src/auto-reply/status.ts is that /status context usage now uses totalTokens (or input+output) directly instead of respecting the totalTokensFresh flag, which can cause stale/legacy cached totals to be displayed as if they were current.

Confidence Score: 4/5

Mostly safe to merge, but there is a correctness regression in /status token reporting semantics.
The agentId plumbing and added tests look coherent and targeted, but buildStatusMessage now ignores the existing totalTokensFresh staleness signal and will display stale cached totals as real context usage for affected sessions.
src/auto-reply/status.ts

_{Last reviewed commit: d2c66cf}

Co-authored-by: Josh Lehman <[email protected]>

cursor · 2026-02-13T13:17:24Z

PR Summary

Medium Risk
Touches session transcript path resolution and usage reporting across auto-reply and gateway APIs; mistakes could break status/usage visibility or accidentally point at the wrong agent’s session files.

Overview
Fixes multi-agent session transcript path resolution by consistently threading agentId through /status output, /usage cost, gateway sessions.usage (including timeseries and logs), and the underlying session cost/usage helpers so non-default agents can read absolute session files without failing path validation.

Updates auto-reply session initialization to pass agentId when forking session logs, and adjusts status token accounting to derive totalTokens directly (removing the stale “freshness” flag behavior). Adds regression tests covering non-main agent transcript usage/cost/timeseries/log retrieval, and documents the fix in CHANGELOG.md.

^{Written by Cursor Bugbot for commit d2c66cf. This will update automatically on new commits. Configure here.}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2c66cff0b

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-02-13T13:21:40Z

-  // it as a new session so that thread context (history/starter/fork) is applied.
-  const forceNewForThread = Boolean(ctx.IsFirstThreadTurn) && !resetTriggered;
-  if (!isNewSession && freshEntry && !forceNewForThread) {
+  if (!isNewSession && freshEntry) {


Preserve first thread turn as a new session

This branch now resumes any fresh store entry, but first thread turns can already have a freshly written entry because inbound handling pre-records session metadata before initSessionState runs (see Slack prepare.ts setting IsFirstThreadTurn and calling recordInboundSession). In that case, the first message of a new thread is treated as a resumed session, so new-thread setup like parent-session forking/context bootstrap is skipped, producing incorrect thread context on the first reply.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-02-13T13:21:40Z

  let inputTokens = entry?.inputTokens;
  let outputTokens = entry?.outputTokens;
-  let totalTokens = resolveFreshSessionTotalTokens(entry);
+  let totalTokens = entry?.totalTokens ?? (entry?.inputTokens ?? 0) + (entry?.outputTokens ?? 0);


Respect stale token freshness in status context usage

This assignment bypasses totalTokensFresh and always reports totalTokens (or input+output), so sessions marked with totalTokensFresh: false are now shown as having concrete context usage instead of unknown. That regresses status accuracy when only stale snapshots are available, leading /status to report misleading utilization values (including false high/100% usage).

Useful? React with 👍 / 👎.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-13T13:22:22Z

-  // it as a new session so that thread context (history/starter/fork) is applied.
-  const forceNewForThread = Boolean(ctx.IsFirstThreadTurn) && !resetTriggered;
-  if (!isNewSession && freshEntry && !forceNewForThread) {
+  if (!isNewSession && freshEntry) {


Slack first-thread-turn session logic silently removed

High Severity

The forceNewForThread guard — which forced new-session initialization on the first message in a Slack thread even when a fresh session entry already existed — was removed along with its explanatory comment. IsFirstThreadTurn is still set in the Slack prepare handler and defined in the templating context type, but nothing consumes it now. This means first thread messages in Slack will reuse existing fresh sessions instead of applying thread context (history, starter, fork).

greptile-apps

_{11 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-13T13:25:06Z

Additional Comments (1)

src/auto-reply/status.ts
Stale totals displayed

SessionEntry.totalTokensFresh is used to mark cached totalTokens as stale/unknown (see resolveFreshSessionTotalTokens in src/config/sessions/types.ts). buildStatusMessage no longer consults that flag and always uses entry.totalTokens (or input+output) as the context baseline, so entries with totalTokensFresh === false will still show a concrete context usage instead of unknown.

That makes /status misleading for any sessions that intentionally set totalTokensFresh to false (including legacy entries).

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/auto-reply/status.ts
Line: 344:351

Comment:
**Stale totals displayed**

`SessionEntry.totalTokensFresh` is used to mark cached `totalTokens` as stale/unknown (see `resolveFreshSessionTotalTokens` in `src/config/sessions/types.ts`). `buildStatusMessage` no longer consults that flag and always uses `entry.totalTokens` (or `input+output`) as the context baseline, so entries with `totalTokensFresh === false` will still show a concrete context usage instead of unknown.

That makes `/status` misleading for any sessions that intentionally set `totalTokensFresh` to false (including legacy entries).


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

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]> (cherry picked from commit 9904135) # Conflicts: # CHANGELOG.md # src/auto-reply/status.test.ts # src/auto-reply/status.ts

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]> (cherry picked from commit 9904135) # Conflicts: # CHANGELOG.md # src/auto-reply/status.ts # src/infra/session-cost-usage.test.ts # src/infra/session-cost-usage.ts

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

fix: land multi-agent session path fix + regressions (#15103)

d2c66cf

Co-authored-by: Josh Lehman <[email protected]>

steipete merged commit 9904135 into main Feb 13, 2026
12 checks passed

steipete deleted the codex/land-15103-20260213141641 branch February 13, 2026 13:17

openclaw-barnacle Bot added gateway Gateway runtime agents Agent runtime and tooling size: M maintainer Maintainer-authored PR labels Feb 13, 2026

chatgpt-codex-connector Bot reviewed Feb 13, 2026

View reviewed changes

cursor Bot reviewed Feb 13, 2026

View reviewed changes

greptile-apps Bot reviewed Feb 13, 2026

View reviewed changes

skyhawk14 pushed a commit to skyhawk14/openclaw that referenced this pull request Feb 13, 2026

fix: land multi-agent session path fix + regressions (openclaw#15103) (…

526d173

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

GwonHyeok pushed a commit to learners-superpumped/openclaw that referenced this pull request Feb 15, 2026

fix: land multi-agent session path fix + regressions (openclaw#15103) (…

8700850

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

primevalsoup mentioned this pull request Feb 15, 2026

resolveSessionFilePath doesn't pass agentId — breaks multi-agent session handling #17059

Closed

nathankjer mentioned this pull request Feb 17, 2026

[Bug]: resolve sessionfilepath ignores agent id for non-default agents #15285

Closed

vincentkoc added the dedupe:parent Primary canonical item in dedupe cluster label Feb 23, 2026

This was referenced Feb 23, 2026

fix(sessions): gracefully handle stale cross-agent session file paths #15793

Closed

fix(sessions): allow channel-routed session IDs and cross-agent paths #15176

Closed

github-actions Bot mentioned this pull request Mar 1, 2026

cherry-pick: upstream bugfix commits (2026-03-01-0443) hughdidit/DAISy-Agency#140

Closed

6 tasks

lovewanwan pushed a commit to lovewanwan/openclaw that referenced this pull request Apr 28, 2026

fix: land multi-agent session path fix + regressions (openclaw#15103) (…

a260dca

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

ogt-redknie pushed a commit to ogt-redknie/OPENX that referenced this pull request May 2, 2026

fix: land multi-agent session path fix + regressions (openclaw#15103) (…

9e6d5e7

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request May 9, 2026

fix: land multi-agent session path fix + regressions (openclaw#15103) (…

65977f3

…openclaw#15448) Co-authored-by: Josh Lehman <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix: land multi-agent session path fix + regressions (#15103)#15448

fix: land multi-agent session path fix + regressions (#15103)#15448
steipete merged 1 commit into
mainfrom
codex/land-15103-20260213141641

steipete commented Feb 13, 2026 •

edited by greptile-apps Bot

Loading

Uh oh!

cursor Bot commented Feb 13, 2026 •

edited

Loading

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Feb 13, 2026

Uh oh!

chatgpt-codex-connector Bot Feb 13, 2026

Uh oh!

cursor Bot left a comment

Uh oh!

cursor Bot Feb 13, 2026

Uh oh!

greptile-apps Bot left a comment

Uh oh!

greptile-apps Bot commented Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

steipete commented Feb 13, 2026 • edited by greptile-apps Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Overview

Greptile Summary

Confidence Score: 4/5

Uh oh!

cursor Bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Feb 13, 2026

Choose a reason for hiding this comment

Slack first-thread-turn session logic silently removed

Uh oh!

greptile-apps Bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot commented Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

steipete commented Feb 13, 2026 •

edited by greptile-apps Bot

Loading

cursor Bot commented Feb 13, 2026 •

edited

Loading