feat(cli): surface crew-vs-platform config ownership (init + doctor) [5.7.0] - #91
Closed
abhishekmishragithub wants to merge 1 commit into
Closed
feat(cli): surface crew-vs-platform config ownership (init + doctor) [5.7.0]#91abhishekmishragithub wants to merge 1 commit into
abhishekmishragithub wants to merge 1 commit into
Conversation
Make the crew ownership boundary obvious in the SDK/CLI, off the back of a real customer confusion (dashboard tools + redaction on a crew agent). - New shared ownership matrix (cli/lib/ownership.py): crew owns only the LLM turn; platform owns voice/STT/redaction/first-message/timeouts, read fresh per call. - `agent-crew init` prints the ownership summary after linking. - New `agent-crew doctor [--agent-id]`: flags no-live-build, non-single_prompt workflow, PII redaction ON, and dashboard Tools transfer_call (inert for crew). Verified live: correctly flags redaction ON + confirms the live build. - Deprecate SDKSystemUpdateOutputAgentSettingsEvent (not applied by the platform; emits DeprecationWarning, removal in a future release). Docs counterpart shipped separately. Version 5.7.0.
This was referenced Aug 6, 2026
Collaborator
Author
|
Superseded by the consolidated release PR release/5.10.0 (single review + single version bump). Branch kept. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surfaces the crew ownership boundary in the SDK/CLI, off a real customer confusion (a crew agent with
transfer_calltoggled in the dashboard + PII redaction on).What
cli/lib/ownership.py): a crew owns only the LLM turn (prompt, messages,@function_tools, end/transfer/speak/mute); the platform owns voice/STT/PII redaction/first-message/timeouts, read fresh per call.agent-crew initprints the ownership summary after linking.agent-crew doctor [--agent-id]— inspects an agent and flags: no live crew build, non-single_promptworkflow, PII redaction ON (rewrites the transcript), andtransfer_callenabled in the dashboard Tools panel (inert for crew agents).SDKSystemUpdateOutputAgentSettingsEvent(emitsDeprecationWarning) — the platform never applies crew-sent output-agent settings; removal in a future release.Verified
doctorrun live against a real agent: correctly flagged "PII redaction is ON" and confirmed the live build.pytest tests/custom— 101 passed, 1 skipped (no regressions); newtest_crew_ownership_cli.py= 3 passed.buildscommand are unrelated and present onmain.)Notes for review
AGENT_SDK_OWNERSHIP.md.deploypre-flight lint (heuristic scan of user code) — left out to avoid false positives;doctorcovers the same ground more reliably.Draft — merging bumps the version and auto-publishes. Hold for your review.