feat(advanced): support a CompositeBackend workspace and filesystem permissions - #1113
Open
mariadhakalUipath wants to merge 1 commit into
Open
mariadhakalUipath wants to merge 1 commit into
mariadhakalUipath wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Compiled subagents can bypass supplied filesystem permissions, contrary to documented inheritance.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Adds CompositeBackend workspace support and optional filesystem permissions for advanced agents.
Changes:
- Resolves composite defaults for memory and attachments.
- Forwards filesystem permissions to agents and subagents.
- Adds regression tests and bumps version to
0.18.15. - Blocking issue: compiled subagents may bypass supplied permissions.
| File | Summary |
|---|---|
uv.lock |
Updates locked package version. |
tests/agent/advanced/test_permissions.py |
Tests permission enforcement and inheritance. |
tests/agent/advanced/test_memory_injection.py |
Tests composite memory behavior. |
tests/agent/advanced/test_create_advanced_agent_graph.py |
Tests input attachment resolution. |
tests/agent/advanced/test_conversational_advanced_agent_graph.py |
Tests message attachment resolution. |
src/uipath_langchain/agent/advanced/agent.py |
Implements workspace resolution and permission forwarding. |
pyproject.toml |
Bumps package version. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| memory=list(memory) or None, | ||
| middleware=[*middleware, payload_handler], | ||
| skills=list(skills) if skills else None, | ||
| permissions=list(permissions) if permissions else None, |
…ermissions Memory and input and message attachments were enabled only for a FilesystemBackend, so a CompositeBackend silently lost memory and faulted on input attachments. Each graph builder now treats a CompositeBackend's default as the workspace, once, and uses it for memory and attachments. The deep agent still receives the full composite, so routed mounts stay visible to it. The graph builders also accept deepagents FilesystemPermission rules and forward them to create_deep_agent. Its filesystem tools enforce them for the main agent, its subagents, and calls bridged from the code interpreter. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
mariadhakalUipath
force-pushed
the
feat/composite-backend-support
branch
from
September 23, 2026 20:29
149f846 to
bcb668d
Compare
|
This branch has not been deployed
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.
What changed?
Advanced agents can now be given a deepagents
CompositeBackendand filesystem permissions.FilesystemBackend. ACompositeBackendtherefore silently lost memory, and a run with an input attachment failed withNotImplementedError. Each graph builder now treats a composite'sdefaultas the workspace, once, where the backend comes in, and uses it for memory and attachments. The deep agent still receives the full composite, so routed mounts (e.g./skills/) stay visible to it.permissionsparameter.create_advanced_agent,create_advanced_agent_graphandcreate_conversational_advanced_agent_graphaccept deepagentsFilesystemPermissionrules and forward them tocreate_deep_agent. Its filesystem tools enforce them for the main agent, its subagents, and calls bridged from the code interpreter.0.18.15.Needed by uipath-agents-python for UiPath Skills: the skills folder is mounted read-only at
/skills/next to the workspace, via aCompositeBackendplus a deny-write rule.Are there any breaking changes?
None.
permissionsis optional, and non-composite backends behave as before.