x-cli-session-id request header support so @composio/cli can tag every request with its local cwd-scoped session id (already generated by the CLI in consumer-short-term-cache.json and attached to analytics events as cli_session_id).requestInfo.cliSessionId on the server async context from both the Hono req_id middleware (via get_request_source) and the Next.js App Router with_route middleware.StandardizedSessionInfo with an optional cli_session_id field (snake_case + camelCase aliases) so it persists into the existing ClickHouse session_info JSON blob. No schema migration required.enrichSessionInfo reads cli_session_id off the server context when the caller's sessionInfo doesn't already carry one — so every path that funnels through executeTool → insertToolExecutionLogs (direct execute, meta tools, MULTI_EXECUTE, recipes) picks it up automatically via AsyncLocalStorage.Today the CLI generates a stable per-cwd session id and sends it as cli_session_id on analytics events, but tool execution logs are completely blind to it — there's no way to look at the logs UI / retool and filter tool executions back to a single CLI session (one user, one repo, one workflow). This wires the existing CLI session id through to the execution log row.
Companion CLI PR: ComposioHQ/composio#3430
/api/v3.1/tool_router/session/{id}/execute from the CLI with the new header and verify the resulting ClickHouse tool log row has session_info.cli_session_id setcli_session_id absent🤖 Generated with Claude Code
Based on git blame analysis of 7 file(s):
| Contributor | Contribution | Files |
|---|---|---|
| Himanshu Dixit | 40% | 7 |
| Zen Agent | 15% |
| 4 |
| sjd9021 | 9% | 1 |
| Dhawal Upadhyay | 7% | 1 |
| Himanshu Dixit | 6% | 3 |
Based on git history, Himanshu Dixit or Zen Agent would be good reviewer(s) for this PR.
🤖 Based on git blame with recency weighting (recent edits count more).
The author of this PR, CryogenicPlanet, is not an activated member of this organization on Codecov. Please activate this user on Codecov to display this PR comment. Coverage data is still being uploaded to Codecov.io for purposes of overall coverage calculations. Please don't hesitate to email us at support@codecov.io with any questions.