feat(orchestration): control Paseo tools by provider - #2776
Open
mcowger wants to merge 3 commits into
Open
Conversation
Contributor
|
| Filename | Overview |
|---|---|
| packages/protocol/src/provider-config.ts | Adds the persisted provider-level Paseo tool policy with backward-compatible optional defaults. |
| packages/protocol/src/paseo-tool-manifest.ts | Defines the shared manifest used to identify and group core and browser tools. |
| packages/server/src/server/agent/paseo-tool-policy.ts | Centralizes provider-policy resolution and individual tool enablement checks. |
| packages/server/src/server/agent/agent-manager.ts | Resolves and snapshots the selected provider's policy when creating or restoring sessions. |
| packages/server/src/server/agent/tools/paseo-tools.ts | Filters native Paseo tool registration according to the resolved session policy. |
| packages/app/src/screens/settings/paseo-tools-policy-sheet.tsx | Adds the searchable policy editor, master and bulk controls, browser gating, and immediate persistence. |
| packages/app/src/screens/settings/providers-section.tsx | Integrates provider tool configuration into the provider actions menu with daemon capability handling. |
| docs/data-model.md | Documents provider policy persistence, defaults, global override behavior, and session snapshot semantics. |
| docs/providers.md | Documents policy-filtered native and MCP catalog integration for provider implementations. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart LR
Config[Provider tool policy] --> Resolve[Resolve provider and global policy]
Global[Host-level injection switch] --> Resolve
Resolve --> Session[Snapshot policy for session]
Session --> Native[Native Paseo catalog]
Session --> MCP[MCP Paseo catalog]
Browser[Browser tools availability] --> Native
Browser --> MCP
Reviews (9): Last reviewed commit: "fix(orchestration): avoid policy PR conf..." | Re-trigger Greptile
mcowger
force-pushed
the
feat-per-provider-tool-control
branch
3 times, most recently
from
August 3, 2026 12:33
04b534c to
54b2e49
Compare
webplode
pushed a commit
to webplode/paseo-doctrine-downstream
that referenced
this pull request
Aug 4, 2026
Port getpaseo/paseo#2776 onto current main and add a mutually exclusive, fail-closed allowedTools policy for role-scoped catalogs.
mcowger
force-pushed
the
feat-per-provider-tool-control
branch
from
August 6, 2026 23:22
54b2e49 to
4a36b01
Compare
mcowger
force-pushed
the
feat-per-provider-tool-control
branch
from
August 14, 2026 16:09
3f3a5dd to
fbb7a99
Compare
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.
Summary
Add per-provider controls for the Paseo tools exposed to coding agents, while preserving the existing host-level kill switch.
Changes
Testing
npm run build:clientnpm run typechecknpm run lintnpm run format:checkCI note
30814069282) had Playwright shard 4/4 fail while installing Chromium: Playwright's CDN returned HTTP 403 (service not available in your location). The shard failed before tests ran; this was an environment/download failure, not a product test failure.