docs: Python SDK v1.6.0 + tee permissions + plan-mode-in-SDK clarification + GitLab marketplace + Salesforce beta - #1288
Merged
Conversation
…ation + GitLab marketplace + Salesforce beta Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
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
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.
Night shift report
WHY THIS MATTERS: Four distinct things landed today, each worth knowing. The Python SDK hit v1.6.0 with new API surface (url_sources for web fetch, Managed Agents auto mode tool permissions, signed compaction blocks beta, async credential token providers, and a retry-after fix that now correctly honors values above 60 seconds). On the permissions front, two behavioral changes arrived:
teeis now covered by Edit allow/deny rules (v2.1.269+), and!negation patterns in deny/ask lists can carve out exceptions within the same file — both are net-new capabilities that change what rules do. The plan-mode docs got a significant disambiguation: plan mode's bypass-permission relaxations only apply in interactive terminal sessions, explicitly not in SDK sessions, headless-pruns, or the VS Code chat panel — SDK users settingallowDangerouslySkipPermissions: truewithpermissionMode: 'plan'now have a clear contract (edits still go tocanUseTool). And the plugin marketplace added GitLab: org admins can now sync a marketplace from gitlab.com or a self-managed GitLab instance via a new GitLab configuration in Organization Settings.HIGHLIGHTS:
url_sourceson web fetch tool, auto mode tool permissions for Managed Agents, signed compaction blocks (beta),thinking_mismatch_allowedin input_transformations (beta), async credential token providers, retry-after fix for values >60s, async client connection error retriesteenow covered by permissions (v2.1.269+):make | tee build.logand similar pipelines checkteewrite targets against Edit allow/deny rules and protected paths — same ascat/sed/redirections;Bash(tee *)alone doesn't bypass a working-directory restriction!negation patterns in deny/ask rules:Read(*.env)+Read(!sample.env)blocks all.envfiles exceptsample.env; carve-outs are limited to same-source rules and can't reopen a subdirectory blocked as a whole-pheadless runs, and VS Code chat panel;allowDangerouslySkipPermissions: true+permissionMode: 'plan'in SDK still routes tocanUseTool!rule restriction: embedding-host parent settings can't carve paths out of managed deny rules with!negation patternsCreated by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning