muse-code-sdk 1.4.12__tar.gz → 1.4.13__tar.gz

{muse_code_sdk-1.4.12 → muse_code_sdk-1.4.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: muse-code-sdk
-Version: 1.4.12
+Version: 1.4.13
 Summary: Muse Code SDK for MSP: asyncio-first facade over the generated wire types (muse-code-msp), with a thin sync wrapper.
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/meta-models/muse-code-sdk
@@ -15,7 +15,7 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: pydantic==2.13.5
-Requires-Dist: muse-code-msp==1.4.12
+Requires-Dist: muse-code-msp==1.4.13
 Dynamic: license-file
 
 # `muse-code-sdk`
@@ -84,6 +84,47 @@ async def main() -> None:
 asyncio.run(main())
 ```
 
+To run a session and the child agents it starts without approval prompts,
+start it under the built-in `:unrestricted` permission profile. Current
+releases admit every child of such a session without prompts; a child admitted
+with a narrower authority would stay gated at it.
+
+That profile is described, verbatim, as "No filesystem sandbox or approval
+prompts; local commands have direct network access; project trust is
+unchanged." It also sets the approval reviewer to none. Use it only for a
+trusted workspace and trusted prompts. Never use it where the prompts or the
+sandbox are what protects you.
+
+Start it with that profile, and pass the same profile when you resume it.
+Paste inside `main()` above, indented, before `await client.close()`, with the same client:
+
+```python
+from muse_code import ResumeSessionOptions, StartSessionOptions
+
+session = await client.start_session(StartSessionOptions(
+    workspace_root="/path/to/repo",  # an absolute path
+    permission_profile=":unrestricted",
+))
+saved_session_id = session.session_id
+# ... later, in the same client:
+session = await client.resume_session(ResumeSessionOptions(
+    session_id=saved_session_id,
+    permission_profile=":unrestricted",
+))
+```
+
+On start, `require_permission_profile=True` makes the client prove that the
+pick was applied, and raise `PermissionProfileNotApplied` if it cannot (a
+failed `session/read` read-back raises its own error). A host
+that does not report the committed selection fails that proof even when the
+pick was applied (seen with Muse Code 1.4.12). Resume has no
+`require_permission_profile`, so the client never verifies the pick there.
+
+`approval_mode` alone is not enough: it changes the session's own approval
+mode, but its child agents are capped by the session's permission profile.
+Under a prompting profile (such as `:ask-me`, whose approval is `on_request`),
+the children still ask.
+
 ## Documentation
 
 - Guides, cookbook recipes, and the protocol reference:

{muse_code_sdk-1.4.12 → muse_code_sdk-1.4.13}/README.md

@@ -64,6 +64,47 @@ async def main() -> None:
 asyncio.run(main())
 ```
 
+To run a session and the child agents it starts without approval prompts,
+start it under the built-in `:unrestricted` permission profile. Current
+releases admit every child of such a session without prompts; a child admitted
+with a narrower authority would stay gated at it.
+
+That profile is described, verbatim, as "No filesystem sandbox or approval
+prompts; local commands have direct network access; project trust is
+unchanged." It also sets the approval reviewer to none. Use it only for a
+trusted workspace and trusted prompts. Never use it where the prompts or the
+sandbox are what protects you.
+
+Start it with that profile, and pass the same profile when you resume it.
+Paste inside `main()` above, indented, before `await client.close()`, with the same client:
+
+```python
+from muse_code import ResumeSessionOptions, StartSessionOptions
+
+session = await client.start_session(StartSessionOptions(
+    workspace_root="/path/to/repo",  # an absolute path
+    permission_profile=":unrestricted",
+))
+saved_session_id = session.session_id
+# ... later, in the same client:
+session = await client.resume_session(ResumeSessionOptions(
+    session_id=saved_session_id,
+    permission_profile=":unrestricted",
+))
+```
+
+On start, `require_permission_profile=True` makes the client prove that the
+pick was applied, and raise `PermissionProfileNotApplied` if it cannot (a
+failed `session/read` read-back raises its own error). A host
+that does not report the committed selection fails that proof even when the
+pick was applied (seen with Muse Code 1.4.12). Resume has no
+`require_permission_profile`, so the client never verifies the pick there.
+
+`approval_mode` alone is not enough: it changes the session's own approval
+mode, but its child agents are capped by the session's permission profile.
+Under a prompting profile (such as `:ask-me`, whose approval is `on_request`),
+the children still ask.
+
 ## Documentation
 
 - Guides, cookbook recipes, and the protocol reference:

{muse_code_sdk-1.4.12 → muse_code_sdk-1.4.13}/pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "muse-code-sdk"
-version = "1.4.12"
+version = "1.4.13"
 description = "Muse Code SDK for MSP: asyncio-first facade over the generated wire types (muse-code-msp), with a thin sync wrapper."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -18,7 +18,7 @@ license-files = ["LICENSE"]
 # `pip install muse-code-sdk` must import, and the release bump moves this
 # package's version and its muse-code-msp pin together; pydantic bumps stay
 # reviewed PRs (test_publish_shape pins the pairing).
-dependencies = ["pydantic==2.13.5", "muse-code-msp==1.4.12"]
+dependencies = ["pydantic==2.13.5", "muse-code-msp==1.4.13"]
 classifiers = [
     # Alpha states the withheld promise: publication is permitted, but the
     # stability promise and conformance claim stay withheld — experimental

{muse_code_sdk-1.4.12 → muse_code_sdk-1.4.13}/src/muse_code/__init__.py

@@ -80,7 +80,7 @@ __all__ = [
 ]
 
 EXPECTED_SCHEMA_FINGERPRINT: Final[str] = (
-    "sha256:cfdb6d2525601b9bac76584ccb0610ab3a5539b5e4f51141f079b99b39fcb4e0"
+    "sha256:7fddaf646dbc317e5fcac0785e135eb04df14fbb0db1863089dfd6da21730e5b"
 )
 """The stable schema-bundle fingerprint this SDK was built against.
 
@@ -92,7 +92,7 @@ Python SDK reds this lane instead of drifting silently.
 # The lockstep rule: the release train bumps pyproject.toml, the
 # distribution-metadata authority; this constant is aligned at publication
 # time.
-__version__: Final[str] = "1.4.12"
+__version__: Final[str] = "1.4.13"
 
 # The facade is imported last so the constants above are already bound: the
 # spawn path reads ``EXPECTED_SCHEMA_FINGERPRINT`` (lazily, at initialize

{muse_code_sdk-1.4.12 → muse_code_sdk-1.4.13}/src/muse_code_sdk.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: muse-code-sdk
-Version: 1.4.12
+Version: 1.4.13
 Summary: Muse Code SDK for MSP: asyncio-first facade over the generated wire types (muse-code-msp), with a thin sync wrapper.
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/meta-models/muse-code-sdk
@@ -15,7 +15,7 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: pydantic==2.13.5
-Requires-Dist: muse-code-msp==1.4.12
+Requires-Dist: muse-code-msp==1.4.13
 Dynamic: license-file
 
 # `muse-code-sdk`
@@ -84,6 +84,47 @@ async def main() -> None:
 asyncio.run(main())
 ```
 
+To run a session and the child agents it starts without approval prompts,
+start it under the built-in `:unrestricted` permission profile. Current
+releases admit every child of such a session without prompts; a child admitted
+with a narrower authority would stay gated at it.
+
+That profile is described, verbatim, as "No filesystem sandbox or approval
+prompts; local commands have direct network access; project trust is
+unchanged." It also sets the approval reviewer to none. Use it only for a
+trusted workspace and trusted prompts. Never use it where the prompts or the
+sandbox are what protects you.
+
+Start it with that profile, and pass the same profile when you resume it.
+Paste inside `main()` above, indented, before `await client.close()`, with the same client:
+
+```python
+from muse_code import ResumeSessionOptions, StartSessionOptions
+
+session = await client.start_session(StartSessionOptions(
+    workspace_root="/path/to/repo",  # an absolute path
+    permission_profile=":unrestricted",
+))
+saved_session_id = session.session_id
+# ... later, in the same client:
+session = await client.resume_session(ResumeSessionOptions(
+    session_id=saved_session_id,
+    permission_profile=":unrestricted",
+))
+```
+
+On start, `require_permission_profile=True` makes the client prove that the
+pick was applied, and raise `PermissionProfileNotApplied` if it cannot (a
+failed `session/read` read-back raises its own error). A host
+that does not report the committed selection fails that proof even when the
+pick was applied (seen with Muse Code 1.4.12). Resume has no
+`require_permission_profile`, so the client never verifies the pick there.
+
+`approval_mode` alone is not enough: it changes the session's own approval
+mode, but its child agents are capped by the session's permission profile.
+Under a prompting profile (such as `:ask-me`, whose approval is `on_request`),
+the children still ask.
+
 ## Documentation
 
 - Guides, cookbook recipes, and the protocol reference:

muse_code_sdk-1.4.13/src/muse_code_sdk.egg-info/requires.txt

@@ -0,0 +1,2 @@
+pydantic==2.13.5
+muse-code-msp==1.4.13

muse_code_sdk-1.4.12/src/muse_code_sdk.egg-info/requires.txt

@@ -1,2 +0,0 @@
-pydantic==2.13.5
-muse-code-msp==1.4.12