You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Python: [Team][Investigation] Check Invocations adoption and customer scenarios #10025
Team-owned — not open for community pickup yet. Do not start implementation or submit a PR without explicit maintainer agreement.
Category
Other
Problem
Obtain usage metrics and concrete customer scenarios for Invocations. Use these as input to its support-status decision.
Evidence
Parent: #10009. Edited checklist; meeting 56:39–57:28. Relevant entry point: InvocationsHostServer in _invocations.py and its agent/native-workflow samples.
Desired Outcome
Investigation needed. Identify available adoption signals and real needs for agent hosting, native workflow hosting, custom protocols, and channel adapters. Record data limitations and distinguish sample/package usage from production adoption. Do not publish private customer or telemetry data; summarize shareable aggregate evidence and link approved internal evidence where appropriate. Feed the support-status decision; missing metrics alone do not prove zero demand.
Language
Python
Acknowledgements
I searched existing issues and did not find a duplicate.
I will wait for explicit maintainer agreement before starting implementation of a non-trivial change.
changed the title [-][Team][Investigation] Check Invocations adoption and customer scenarios[/-][+]Python: [Team][Investigation] Check Invocations adoption and customer scenarios[/+]on Nov 3, 2026
Activity
[-][Team][Investigation] Check Invocations adoption and customer scenarios[/-][+]Python: [Team][Investigation] Check Invocations adoption and customer scenarios[/+]eavanvalkenburg commentedon Nov 3, 2026
/plan