whitlocktech/Agentic-Bridle
1
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Phase 3 — Upstream proxy layer and Gitea integration #5

New Issue
Open
opened 2026-08-08 19:36:20 +00:00 by wtclaude · 0 comments
wtclaude commented 2026-08-08 19:36:20 +00:00
Collaborator
Copy Link

Size: medium · Depends on: Phase 1 (permissions), Phase 2

Scope

  • Generic upstream-MCP client with connection pooling and health tracking
  • Tool namespacing, stable across restarts — proposed default gitea__create_pr (double underscore)
  • Per-agent tool filtering driven by the phase-1 permissions table
  • Credential injection per request; upstreams never hold their own tokens
  • Failure isolation per ADR-0009

Exit criterion

An agent completes a full Gitea PR workflow through Bridle while holding no Gitea token itself; killing the Gitea MCP container degrades only Gitea tools.

References

ADR-0009 (stable tool list on upstream failure), ADR-0008 (enforcement scope)

Review notes

  • Tool names become effectively permanent once agents depend on them — settle the convention before merging
  • Aggregating a large upstream tool set costs context in every session; per-agent filtering is what keeps that in check
  • Security review required (credential injection)

Open item to settle first

Tool namespacing convention.

**Size:** medium · **Depends on:** Phase 1 (permissions), Phase 2 ## Scope - Generic upstream-MCP client with connection pooling and health tracking - Tool namespacing, stable across restarts — proposed default `gitea__create_pr` (double underscore) - Per-agent tool filtering driven by the phase-1 permissions table - Credential injection per request; upstreams never hold their own tokens - Failure isolation per ADR-0009 ## Exit criterion An agent completes a full Gitea PR workflow through Bridle while holding no Gitea token itself; killing the Gitea MCP container degrades only Gitea tools. ## References ADR-0009 (stable tool list on upstream failure), ADR-0008 (`enforcement` scope) ## Review notes - Tool names become effectively permanent once agents depend on them — settle the convention before merging - Aggregating a large upstream tool set costs context in every session; per-agent filtering is what keeps that in check - Security review required (credential injection) ## Open item to settle first Tool namespacing convention.
wtclaude added this to the v1.0 — Agentic Bridle milestone 2026-08-08 19:36:20 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone v1.0 — Agentic Bridle
Projects
Clear projects
No project
Assignees
Clear assignees
wtclaude whitlocktech
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: whitlocktech/Agentic-Bridle#5
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?