The daily firehose — everything the toolchain shipped today, already filtered.
// HOW THIS ISSUE IS MADE
We read every release from the 174 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.
Retrieve a specific run from a completed team session via the new AgentOS endpoint.
$ curl -X GET 'https://<agentOS-host>/sessions/<session-id>/runs/<run-id>' \
-H 'Authorization: Bearer <token>'
›Adds stream_events flag to Agent, Team, Workflow, and all run methods to emit all events when streaming a response (previously tool-call events were always yielded; non-RunContent events are now gated behind this flag).
›Adds update_session_state and aupdate_session_state methods on Agent and Team for direct, DB-persisted session state updates.
›Adds add_team_history_to_members config on Team to share team-level request/response history with member agents.
›Adds three new AgentOS session endpoints: POST /sessions (create a new empty session), GET /sessions/{id}/runs/{id} (get a run by ID), and PATCH /sessions/{id} (update an existing session).
›Adds PostHookStarted, PostHookCompleted, SessionSummaryCreationStarted, SessionSummaryCreationCompleted, and RunContentCompleted events for both Agent and Team, enabling fine-grained UI streaming control.
+3 moreshow less
›Workflow .arun now returns an AsyncIterator, consistent with Agent and Team, enabling event-by-event async streaming.
›Concurrent memory creation: automatic memory creation now starts in a background thread/task at the beginning of an Agent/Team run, reducing total run latency when memory generation is enabled.
›Improves get_run_output and get_last_run_output on Agent/Team to support retrieval of runs from member agents after team execution.
└──▷ BREAKING ON UPGRADE
!Workflow.arun(..., stream=True) now returns an AsyncIterator; callers must replace await workflow.arun(...) with async for event in workflow.arun(...).
!All events except RunContent events are now gated behind stream_events=True; tool-call events that were previously always yielded will no longer appear unless stream_events=True is set.
!stream_intermediate_steps is deprecated in favour of stream_events.
AutoGPT Platform v0.6.34 adds shared cache, language fallback for YouTube transcription, and LaunchDarkly payment flag
└──▷ GET THIS VERSION
$ git clone --branch autogpt-platform-beta-v0.6.34 https://github.com/Significant-Gravitas/AutoGPT.git
# already have the repo? check out this version:$ git checkout autogpt-platform-beta-v0.6.34
›Adds LaunchDarkly feature flag for the platform payment system, enabling controlled rollout of payment features.
›Implements shared cache functionality for agent execution.
›Adds language fallback support for the YouTube transcription block, improving resilience when a primary language transcript is unavailable.
›Adds extra information display for custom nodes in the new agent builder UI.
›Updates tooltip and alert styles in the builder UI.
$ git clone --branch v1.3.0 https://github.com/pydantic/pydantic-ai.git
# already have the repo? check out this version:$ git checkout v1.3.0
└──▷ USE IT
Catch truncated tool calls gracefully in CI pipelines where token budgets are tight.
python
from pydantic_ai.exceptions import IncompleteToolCall
try:
result = await agent.run(prompt)
except IncompleteToolCall as e:
print(f'Tool call was cut off by token limit: {e}')
Connect to Vertex AI using an API key instead of application-default credentials.
python
from pydantic_ai.providers.google import GoogleProvider
provider = GoogleProvider(api_key='YOUR_VERTEX_API_KEY')
›Raises IncompleteToolCall exception when a token limit is reached mid-generation of a tool call, giving callers a typed signal to handle truncated tool invocations.
›Adds http_client option to GoogleProvider and adds api_key support for Vertex AI; uses PydanticAI's cached httpx client by default.
›Uses gateway/<upstream_provider>: as the provider name prefix for Gateway model references.
›Adds AWS Bedrock support to the PydanticAI Gateway.
›Adds OVHcloud AI Endpoints as a new provider.
+4 moreshow less
›Makes AbstractBuiltinTool serializable and compatible with durable execution workflows.
›Includes eval report averages in OpenTelemetry span attributes.
›Includes all usage fields (beyond token counts) in OpenTelemetry span attributes.
›Ensures toolset spans (e.g. MCP sampling) are nested under the agent run span in traces.
Continue 1.30.0 adds background agents, local takeover, and a session-selector preview panel.
└──▷ GET THIS VERSION
$ git clone --branch @continuedev/[email protected] https://github.com/continuedev/continue.git
# already have the repo? check out this version:$ git checkout @continuedev/[email protected]
└──▷ TRY IT
Preview a past session's content before resuming it, useful for picking up the right context in a long-running investigation.
$ cn ls
›Adds a preview panel to the session selector, accessible via cn ls / /resume, to inspect session content before switching.
›Adds background agent creation and management, enabling agents to run without an active foreground session.
›Adds local takeover capability, allowing a local instance to take control of a background agent session.
›Reports cache write tokens from the Anthropic OpenAI adapter, surfacing prompt-caching cost data in token usage.
›Returns fetch errors back to the agent loop so agents can reason about and recover from network failures.
Copilot CLI gains parallel tool execution and temp directory access, both controllable via new flags.
└──▷ GET THIS VERSION
$ git clone --branch v0.0.349 https://github.com/github/copilot-cli.git
# already have the repo? check out this version:$ git checkout v0.0.349
└──▷ TRY IT
Run Copilot CLI in environments where parallel tool calls could cause unintended side effects and you want sequential, one-at-a-time confirmation.
$ copilot --disable-parallel-tools-execution
Run Copilot CLI in a restricted environment where the model should not be able to read or write the system temp directory.
$ copilot --disallow-temp-dir
›Adds --disable-parallel-tools-execution flag to control the new parallel tool calling behavior, where the model can invoke multiple tools simultaneously (each requiring individual confirmation).
›Adds --disallow-temp-dir flag to control the new default behavior of granting the model access to the system temp directory.
An open-source AI agent that brings the power of Gemini directly into your terminal.
gemini-cli v0.10.0 adds a code-guide command, interactive shell by default, smart edit enabled by default, GOOGLE_CLOUD_PROJECT_ID fallback, and failed-response retry.
└──▷ GET THIS VERSION
$ git clone --branch v0.10.0 https://github.com/google-gemini/gemini-cli.git
# already have the repo? check out this version:$ git checkout v0.10.0
└──▷ TRY IT
Use GOOGLE_CLOUD_PROJECT_ID as a fallback when GOOGLE_CLOUD_PROJECT is not set, avoiding auth failures in environments where only the _ID variant is configured.
$ GOOGLE_CLOUD_PROJECT_ID=my-project-123 gemini
›Adds code guide command for codebase investigation workflows.
›Enables interactive shell by default, improving command execution experience.
›Enables useSmartEdit by default for smarter, context-aware file edits.
›Supports GOOGLE_CLOUD_PROJECT_ID environment variable as a fallback for project configuration.
›Adds automatic retry with extra prompt on failed model responses.
+7 moreshow less
›Shortens the context overflow message when usage is below 75% of the limit.
›Generalizes path correction across tools for more reliable file targeting.
›Improves shell execution service reliability.
›Exposes Codebase Investigator settings to users via the settings dialog.
›Adds screen reader mode notification support.
›Supports extension pre-releases for early access to extension updates.
›Shows final install path in the extension consent dialog.
gemini-cli v0.11.0-preview.0 adds stream-JSON headless output, markdown toggle, Todo List tab, and up-arrow message editing.
└──▷ GET THIS VERSION
$ git clone --branch v0.11.0-preview.0 https://github.com/google-gemini/gemini-cli.git
# already have the repo? check out this version:$ git checkout v0.11.0-preview.0
└──▷ TRY IT
Stream structured JSON output in a headless/scripted pipeline to parse Gemini responses programmatically.
$ gemini --output-format stream-json -p "Summarize the security findings in report.txt"
Toggle between rendered Markdown and raw text while reviewing a response — useful when you need to copy raw syntax.
$ # While in the gemini-cli interactive session, press:
alt+m
List MCP servers to see which extension each one belongs to.
$ gemini mcp list
›Adds --output-format stream-json flag for headless mode to stream structured JSON output.
›Adds alt+m keyboard shortcut to toggle between rendered Markdown and raw text in the CLI.
›Adds a Todo List tab (TodoTray) to surface and track to-do items in the UI.
›Enables editing of queued messages using the up arrow key before they are sent.
›Displays extension names in gemini mcp list output for easier identification.
+7 moreshow less
›Blends educational tips with witty phrases during loading times.
›Adds 'Esc to close' visual hint to SettingsDialog and other dialogs.
›Improves directory autocomplete by not appending a trailing space after directory names.
›Suppresses slash command execution and suggestions while in shell mode.
›Wires up UI for ASK_USER policy decisions, enabling interactive permission prompts via the message bus.
›Adds activity monitor with event-driven telemetry snapshots.
›Updates shell tool call colors to visually distinguish confirmed actions.
└──▷ BREAKING ON UPGRADE
!The --all-files flag has been removed (deprecated flag dropped).
!Deprecated telemetry flags have been removed.
!Support for workspace extensions and migrations has been removed.
!The ctrl+t key binding for /mcp commands has been removed.
Composio @composio/[email protected] adds mandatory toolkit version validation for manual tool execution with new bypass flag and error types.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit version at SDK initialization so all execute() calls use a stable, date-stamped version instead of 'latest'.
›Adds dangerously_skip_version_check (Python) / dangerouslySkipVersionCheck (TypeScript) parameter to tools.execute() to optionally bypass version validation.
›Adds version parameter to tools.execute() for passing an explicit toolkit version string (e.g. '20251201_01') at call time.
›Adds toolkit_versions configuration key to the Tools constructor for instance-level toolkit version pinning (e.g. toolkit_versions={'github': '20251201_01'}).
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g. COMPOSIO_TOOLKIT_VERSION_GITHUB) as a third option for version pinning without code changes.
›Introduces ToolVersionRequiredError (Python) and ComposioToolVersionRequiredError (TypeScript) exceptions raised when tools.execute() is called with latest version and no skip flag, including error messages listing all four resolution options.
+1 moreshow less
›Manual tool execution via tools.execute() now validates toolkit versions before making API calls, preventing unexpected behavior from latest version drift.
└──▷ BREAKING ON UPGRADE
!Manual tool execution via tools.execute() now raises ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) when no explicit version is specified and dangerously_skip_version_check is not set — any existing code calling tools.execute() without a version will break on upgrade.
Composio OpenAI Agents 0.2.0 adds mandatory toolkit version validation for manual tool execution with four opt-out paths.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit version at SDK init so every subsequent execute() call is validated against a known-good release.
›Adds version validation to tools.execute(): manual tool execution now requires an explicit toolkit version, preventing silent breakage from latest version drift.
›New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript) flag on tools.execute() to bypass version validation when needed.
›New ToolVersionRequiredError exception (Python) and ComposioToolVersionRequiredError error (TypeScript) raised when a tool is executed against latest without the skip flag, each including resolution hints.
›Supports toolkit version pinning via toolkit_versions dict at Tools() initialization — e.g. toolkit_versions={'github': '20251201_01'} — resolved consistently across both execute() and _execute_tool().
›Supports toolkit version pinning via environment variables in the format COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> (e.g. COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01) as an alternative to code-level configuration.
+1 moreshow less
›Agentic framework integrations (LangChain, CrewAI, etc.) automatically set dangerously_skip_version_check=True internally, requiring no migration for those flows.
└──▷ BREAKING ON UPGRADE
!Manual calls to tools.execute() using latest (the implicit default) now raise ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) unless a version is specified via the version argument, toolkit_versions at init, an environment variable like COMPOSIO_TOOLKIT_VERSION_GITHUB, or dangerously_skip_version_check=True.
Composio @composio/[email protected] adds mandatory toolkit version pinning for manual tool execution with multiple opt-out paths.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin toolkit versions at SDK init so all tools.execute() calls in the session use a known-good version without per-call arguments.
›Adds dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript) to tools.execute() to bypass version validation when using latest toolkit versions.
›Adds ToolVersionRequiredError exception (Python) and ComposioToolVersionRequiredError error (TypeScript) raised when tools.execute() is called with latest version and no skip flag, with error messages listing all four resolution paths.
›Supports toolkit version pinning via COMPOSIO_TOOLKIT_VERSION_<TOOLKITNAME> environment variables (e.g., COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01) as an alternative to inline version arguments.
›Supports per-call version pinning via version argument to tools.execute(), e.g., tools.execute('GITHUB_CREATE_ISSUE', arguments={...}, version='20251201_01').
›Supports instance-level version pinning via toolkit_versions dict at Tools initialization, e.g., Tools(client, provider, toolkit_versions={'github': '20251201_01'}).
+1 moreshow less
›Manual tool execution via tools.execute() now validates toolkit versions before API calls; agentic framework integrations (LangChain, CrewAI, etc.) are unaffected as they automatically set dangerously_skip_version_check=True internally.
└──▷ BREAKING ON UPGRADE
!Calling tools.execute() manually with the latest toolkit version (the previous default) now raises ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) unless dangerously_skip_version_check=True / dangerouslySkipVersionCheck: true is passed or a specific version is supplied.
Composio @composio/[email protected] enforces toolkit version validation for manual tool execution, with new bypass flags and errors.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit to a specific version at initialization so all subsequent execute() calls use it without requiring per-call version arguments.
›Adds dangerously_skip_version_check (Python) / dangerouslySkipVersionCheck (TypeScript) optional parameter to tools.execute() to bypass version validation when needed.
›Adds ToolVersionRequiredError exception (Python) and ComposioToolVersionRequiredError error (TypeScript) raised when attempting to execute tools with latest version without the skip flag, including resolution suggestions.
›Manual tool execution via tools.execute() now requires explicit toolkit version specification, configurable via version argument, toolkit_versions at Tools() initialization, or COMPOSIO_TOOLKIT_VERSION_<TOOLKITNAME> environment variable.
›Supports instance-level version configuration via toolkit_versions dict at Tools() construction, applying consistently across execute() and _execute_tool() calls.
└──▷ BREAKING ON UPGRADE
!Manual calls to tools.execute() with latest toolkit version now raise ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) unless a specific version is supplied via the version argument, toolkit_versions config, the COMPOSIO_TOOLKIT_VERSION_<TOOLKITNAME> environment variable, or dangerously_skip_version_check=True.
Composio Cloudflare 0.2.0 adds mandatory toolkit version validation for manual tool execution with new skip flags and error types.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit version at the SDK level so all calls to that toolkit use a known-good version without per-call parameters.
›Adds dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript) to bypass toolkit version validation when executing tools manually.
›Adds version parameter to tools.execute() for passing an explicit toolkit version (e.g. '20251201_01') at call time.
›Adds toolkit_versions configuration key to Tools() initializer for instance-level version pinning (e.g. toolkit_versions={'github': '20251201_01'}).
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g. COMPOSIO_TOOLKIT_VERSION_GITHUB) as a third path for pinning toolkit versions.
›Introduces ToolVersionRequiredError (Python) and ComposioToolVersionRequiredError (TypeScript) exceptions raised when tools.execute() is called with the latest version without the skip flag, including resolution suggestions.
+1 moreshow less
›Manual tool execution via tools.execute() now validates toolkit versions before making API calls; agentic framework integrations (LangChain, CrewAI, etc.) are unaffected via automatic internal skip.
└──▷ BREAKING ON UPGRADE
!Manual calls to tools.execute() that previously relied on the implicit latest version will now raise ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) unless an explicit version is provided, toolkit_versions is set at initialization, a COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variable is present, or dangerously_skip_version_check=True is passed.
Composio Mastra 0.2.0 adds mandatory toolkit version validation for manual tool execution with opt-out flags and new error types.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit version at initialization so all manual tools.execute() calls use it without extra per-call arguments.
›Adds dangerouslySkipVersionCheck (TypeScript) / dangerously_skip_version_check (Python) parameter to tools.execute() to bypass version validation when needed.
›Adds toolkit_versions config at SDK initialization (e.g., Tools(client, provider, toolkit_versions={"github": "20251201_01"})) for instance-level version pinning.
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g., COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01) to pin toolkit versions without code changes.
›Introduces ToolVersionRequiredError (Python) and ComposioToolVersionRequiredError (TypeScript) errors with detailed resolution suggestions when latest version is used without the skip flag.
›Manual tool execution via tools.execute() now validates toolkit versions before API calls, with four documented resolution paths included in error messages.
└──▷ BREAKING ON UPGRADE
!Manual execution via tools.execute() now raises ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) when called with the latest toolkit version and no explicit version or dangerously_skip_version_check flag is provided.
Composio OpenAI SDK v0.2.0 adds mandatory toolkit version validation for manual tool execution with four opt-out paths.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit version at SDK initialization so every subsequent execute() call in the session uses a known-good version without extra per-call arguments.
›Adds explicit toolkit version requirement for manual tools.execute() calls to prevent unexpected behavior from latest version drift.
›New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript) flag lets callers bypass version validation when needed.
›Supports toolkit_versions dict at Tools() initialization (e.g. toolkit_versions={"github": "20251201_01"}) for instance-level version pinning applied to all subsequent calls.
›Supports per-call version parameter on tools.execute() (e.g. version="20251201_01") for one-off version overrides.
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g. COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01) as a third version-pinning path.
!Manual tools.execute() calls that rely on the latest toolkit version will now raise ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) on upgrade unless a version parameter, toolkit_versions config, COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> env var, or dangerously_skip_version_check=True is supplied.
Composio @composio/[email protected] adds mandatory toolkit version validation for manual tool execution with four opt-out paths.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a specific toolkit version at SDK initialization so every subsequent execute() call uses it without per-call version arguments.
›Adds version parameter to tools.execute() to require explicit toolkit version when executing tools manually, preventing unexpected behavior from latest version drift.
›Adds toolkit_versions config dict at Tools() initialization (e.g., toolkit_versions={"github": "20251201_01"}) for instance-level version pinning across all executions.
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g., COMPOSIO_TOOLKIT_VERSION_GITHUB) as a third path to pin toolkit versions without code changes.
›Adds dangerously_skip_version_check (Python) / dangerouslySkipVersionCheck (TypeScript) flag to tools.execute() to bypass version validation when needed.
›Introduces ToolVersionRequiredError (Python) and ComposioToolVersionRequiredError (TypeScript) exceptions with four concrete resolution suggestions when latest is used without the skip flag.
└──▷ BREAKING ON UPGRADE
!Manual tools.execute() calls that rely on the implicit latest toolkit version will now raise ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) unless a version is specified, toolkit_versions is configured at init, a COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> env var is set, or dangerously_skip_version_check=True is passed.
Composio @composio/anthropic 0.2.0 adds mandatory toolkit version validation for manual tool execution with escape hatches via flag, config, or env var.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a specific toolkit version per call in CI so a latest change never silently breaks your automation.
›Adds dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript) to tools.execute() to bypass version validation when needed.
›Adds version parameter to tools.execute() for explicit per-call toolkit version pinning (e.g. version='20251201_01').
›Adds toolkit_versions config key to Tools() constructor for instance-level version pinning across all executions.
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g. COMPOSIO_TOOLKIT_VERSION_GITHUB) to set toolkit versions without code changes.
›Introduces ToolVersionRequiredError (Python) and ComposioToolVersionRequiredError (TypeScript) exceptions raised when tools.execute() is called with latest version and no skip flag, including resolution suggestions.
└──▷ BREAKING ON UPGRADE
!Manual tool execution via tools.execute() now raises ToolVersionRequiredError (Python) / ComposioToolVersionRequiredError (TypeScript) when the toolkit version resolves to latest and dangerously_skip_version_check is not set — existing call sites that relied on implicit latest resolution will break and must add an explicit version, a toolkit_versions config, a COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> env var, or dangerously_skip_version_check=True.
Composio @composio/[email protected] adds mandatory toolkit version validation for manual tool execution with new skip flags and error types.
└──▷ GET THIS VERSION
$ git clone --branch @composio/[email protected] https://github.com/ComposioHQ/composio.git
# already have the repo? check out this version:$ git checkout @composio/[email protected]
└──▷ USE IT
Pin a toolkit version at SDK init so all subsequent execute() calls use it without per-call version arguments.
›Adds dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript) to tools.execute() to bypass version validation when needed.
›Adds toolkit_versions config key at SDK initialization (e.g. Tools(client, provider, toolkit_versions={...})) for instance-level toolkit version pinning.
›Supports COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variables (e.g. COMPOSIO_TOOLKIT_VERSION_GITHUB) to specify toolkit versions without code changes.
›Introduces ToolVersionRequiredError (Python) and ComposioToolVersionRequiredError (TypeScript) — raised when tools.execute() is called with latest version without the skip flag, with error messages covering 4 resolution options.
!Manual tools.execute() calls using the latest toolkit version now raise ToolVersionRequiredError (Python) or ComposioToolVersionRequiredError (TypeScript) unless dangerously_skip_version_check=True is passed or a version is explicitly specified via the version parameter, toolkit_versions config, or a COMPOSIO_TOOLKIT_VERSION_<TOOLKIT> environment variable.
THE AI TOOLCHAIN