@devries-cameron20 / composio-1 / commits / 48bf5f909
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: update guides for SDK changes (#4726)

## Summary Automated docs update triggered by SDK source changes on `next`. - Claude reviewed the SDK diff and updated guides, FAQs, or examples that reference changed APIs or features. - The docs `@composio/*` dependencies were realigned to their latest published releases so Twoslash snippets and example apps validate against versions users can actually install. ## Review checklist - [ ] Changes accurately reflect the new SDK behavior - [ ] No unrelated docs were modified - [ ] Code examples are correct and complete - [ ] If a documented feature is not published yet, the Twoslash build will fail — wait for the release instead of working around it Generated by Claude Code via GitHub Actions. Co-authored-by: jkomyno <12381818+jkomyno@users.noreply.github.com>

sdkrelease[bot] committed Oct 1, 2026 at 16:50 UTC 48bf5f909d5c05962d7d3b225a40d1bfa190754f
2 files changed +8
docs/content/docs/extending-sessions/proxy-execute.mdx
+2
@@ -173,6 +173,8 @@ Don't set the `Authorization` header yourself through `parameters`. Composio inj
173 | `403 Forbidden` | The user's OAuth scopes or API key don't cover this endpoint. | Update the [auth config scopes](/docs/auth-configuration/custom-auth-configs) and have the user re-consent. |
174 | `429 Too Many Requests` | Upstream rate limit (GitHub, Google, and so on). | Honor the `Retry-After` header and back off. Composio doesn't retry automatically. |
175
176 +Composio sends a proxied call exactly once. A timeout, a connection error, or a `5xx` surfaces to you rather than being retried, because a retry after the upstream API already acted would repeat the write. Retry only when the endpoint is safe to call again. See [Retry failed executions deliberately](/docs/production-readiness#retry-failed-executions-deliberately).
177 +
178 ## Next
179
180 <Card icon={<Blocks />} title="Custom tools and toolkits" href="/docs/extending-sessions/custom-tools-and-toolkits" description="Define in-process tools and toolkits that run alongside Composio tools" />
docs/content/docs/production-readiness.mdx
+6
@@ -82,6 +82,12 @@ Run at least one safe, read-only call against a real connected account. Confirm
82
83 Do not treat a successful Connect Link alone as an end-to-end test. Authentication can succeed while a provider API, scope, or tool input still fails.
84
85 +### Retry failed executions deliberately
86 +
87 +The SDKs retry reads — fetching tools, listing toolkits, reading a session — when a request times out or comes back `408`, `409`, `429`, or `5xx`. They never retry an execution. `tools.execute`, `tools.proxy`, and every session `execute` and `proxyExecute` call is sent exactly once, because the backend doesn't deduplicate executions and a silent retry after a read timeout would repeat the side effect, such as sending the same email twice.
88 +
89 +A transient failure on an execution therefore reaches your code instead of being absorbed. Before retrying one, decide whether repeating that specific call is safe: a read is, `GMAIL_SEND_EMAIL` isn't. When it isn't, check [Logs](/reference/api-reference/logs) or the provider's own API to find out whether the first attempt landed.
90 +
91 ### Configure SDK logging
92
93 Pass `logger` and `logLevel` to the TypeScript `Composio` constructor to send SDK logs to your logging system. The logger must provide `error`, `warn`, `info`, and `debug` methods. Messages have credential-shaped values redacted before reaching the logger, including owned-client deprecation warnings. Logger configuration is process-wide: the last configured instance controls the SDK logger.