@claude[bot]agent1mo ago
Claude finished @Sushmithamallesh's task in 1m 18s —— View job
Docs review
- Read review criteria from
docs/.claude/agents/docs-reviewer.md - Inspect diff vs
origin/next - Apply checklist to changed files
- Post review
Verdict: Looks good ✅
Both files check out against the live SDK. A developer copying these would not get stuck.
docs/content/docs/configuring-sessions.mdx (new "Updating a session" section)
session.update()exists in both SDKs:- TS —
ts/packages/core/src/models/ToolRouterSession.ts:570(update(config: ToolRouterUpdateSessionConfig)) - Python —
python/composio/core/models/tool_router_session.py:829(def update(*, toolkits, tools, tags, auth_configs, connected_accounts, ...))
- TS —
- Field names in the TS example (
toolkits,authConfigs,connectedAccounts) matchToolRouterUpdateSessionConfigSchemaatts/packages/core/src/types/toolRouter.types.ts:614. - Python kwargs (
toolkits,auth_configs,connected_accounts) match the signature. - The summary line listing accepted fields (toolkits, auth configs, connected accounts, workbench, multi-account, manage connections, tags, tools, preload) is complete vs. the schema — nothing missing or invented.
- Twoslash prelude (
// ---cut---) is set up correctly so the snippet compiles.
docs/content/docs/common-faq.mdx (FAQ answer rewrite)
- The new guidance — store session ID + reuse with
composio.use(), callsession.update()for config changes, create a new session for fundamentally different setups — matches whatdocs/content/docs/users-and-sessions.mdx:110-173already teaches and what the SDK exposes (composio.use()atts/packages/core/src/models/ToolRouter.ts:283). Previous answer ("callcreate()each time") was outdated now thatupdate()exists.
No fixes needed. · Branch