Skip to content

docs(tools): fix stale proxy connected_account_id docstring [PLEN-2345] - #62

Open
Zen (zen-agent) wants to merge 2 commits into
mainfrom
zen/plen-2345-proxy-docstring-5gi4le
Open

docs(tools): fix stale proxy connected_account_id docstring [PLEN-2345]#62
Zen (zen-agent) wants to merge 2 commits into
mainfrom
zen/plen-2345-proxy-docstring-5gi4le

Conversation

@zen-agent

@zen-agent Zen (zen-agent) commented Apr 29, 2026

Copy link
Copy Markdown

Description

PLEN-2345. The proxy endpoint stopped accepting empty auth context — it now returns 400 ExternalProxy_MissingAuthContext when neither connected_account_id nor custom_connection_data is provided (hermes#9582, shipped 2026-04-24 as part of the PLEN-2166 security fix).

The stale docstring claim — "if not provided, will use the default account for the project" — no longer matches runtime behavior. Callers following the docstring hit an undocumented 400 in production (broke custom Salesforce / Databricks / Google Docs tools).

Updates both the sync (ToolsResource.proxy) and async (AsyncToolsResource.proxy) variants in src/composio_client/resources/tools.py.

How did I test this PR

  • Diff inspection — verified both sync (line 386-389) and async (line 793-796) docstrings now read identically.
  • Generated-code policyCONTRIBUTING.md confirms manual patches in generated files are persisted across regenerations.
  • No code changes — docstring-only.

CI status

  • build — pass
  • ⚠️ lint, testpre-existing failures on main (commit 36e16687), unrelated to this PR:
    • lint flags [no-redef] errors in the generated src/composio_client/types/trigger_instance_list_active_response.py (5 fields).
    • test fails on tests/api_resources/tool_router/test_session.py because the fixture sends a workbench.sandbox_size property that the OpenAPI mock-server schema rejects (E3009 Unknown property).
      Both reproduce on main so they were not introduced here.

🤖 Generated with Claude Code

The proxy endpoint stopped accepting empty auth context (returns 400
``ExternalProxy_MissingAuthContext`` when neither ``connected_account_id``
nor ``custom_connection_data`` is provided), so the docstring's claim
that an omitted id falls back to "the default account for the project"
no longer matches runtime behavior — callers were hitting an
undocumented 400 in production.

Updates both the sync and async ``proxy()`` methods in
``composio_client/resources/tools.py``.

CONTRIBUTING.md notes that manual patches in generated files are
persisted across regenerations.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Co-authored-by: Karan Vaidya <karan@composio.dev>
Co-authored-by: Uday Sidagana <129588963+Uday-sidagana@users.noreply.github.com>
@zen-agent
Zen (zen-agent) force-pushed the zen/plen-2345-proxy-docstring-5gi4le branch from 20de705 to fc5ba4d Compare April 29, 2026 12:23

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the PLEN-2345 docstring follow-up. No blocking findings. The sync and async proxy docstrings now match the current auth-context requirement. I treated the failing lint/test jobs as pre-existing per the PR notes; the changed file is docstring-only and build is green.

Comment thread src/composio_client/resources/tools.py Outdated
Addresses jkomyno's review on PR #62. The generated client sources
were ASCII-only before this change; the previous commit introduced
two em dashes (sync + async ``proxy()`` docstrings). Replacing each
``provided —`` with ``provided. `` keeps the file consistent with
the rest of the generated tree and avoids surprising downstream
tooling that assumes ASCII.

Co-authored-by: Karan Vaidya <karan@composio.dev>
Co-authored-by: Uday Sidagana <129588963+Uday-sidagana@users.noreply.github.com>

Co-authored-by: karan <karan@composio.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants