Add native agent work grants to the MCP gateway

ClaudiuSchuster commented

2026-10-22 22:41:20 +00:00

Owner

Adds five authenticated MCP tools for native agent work grants: discover and inspect a grant, independently confirm its exact proposal, submit an Issue proposal, and reconcile the same durable request key. Agents use their own credentials; preparation, human approval and withdrawal stay in the native browser flow. Ordinary agent activity remains unassigned.

The adapter validates complete native receipts and preserves full UTF-8 task and Issue text. It sends each write once, refuses redirects and forged authorization fields, and leaves uncertain delivery for same-key readback rather than silently retrying. Current bot identity, repository access and scope remain Core-owned checks. The four public tools are unchanged.

Validation:

468 focused test results passed across normal and optimized Python runs.
The full isolated native stack passed real SSH/HTTPS access, headers, adoption, existing PR-diff regressions and the new grant journey: 31 grants across two pages, actual human session approval, wrong bot/scope, a complete 144,000-byte UTF-8 Issue body and native actor readback, withdrawal, replay, deletion tombstones and current access loss.
All eight Git execution checks passed; source, six pinned images, neighboring services and cleanup were verified.
The first harness attempt stopped before header requests because an inherited Python image was missing from its immutable lock. A separately admitted attempt added that exact existing pin; product source and assertions were unchanged.

This is source integration. Deployment requires the matching native Core implementation, its database migration, a fresh fenced backup and a verified restore path; merging this PR does not deploy the gateway or grant anyone access.

Adds five authenticated MCP tools for native agent work grants: discover and inspect a grant, independently confirm its exact proposal, submit an Issue proposal, and reconcile the same durable request key. Agents use their own credentials; preparation, human approval and withdrawal stay in the native browser flow. Ordinary agent activity remains unassigned. The adapter validates complete native receipts and preserves full UTF-8 task and Issue text. It sends each write once, refuses redirects and forged authorization fields, and leaves uncertain delivery for same-key readback rather than silently retrying. Current bot identity, repository access and scope remain Core-owned checks. The four public tools are unchanged. Validation: - 468 focused test results passed across normal and optimized Python runs. - The full isolated native stack passed real SSH/HTTPS access, headers, adoption, existing PR-diff regressions and the new grant journey: 31 grants across two pages, actual human session approval, wrong bot/scope, a complete 144,000-byte UTF-8 Issue body and native actor readback, withdrawal, replay, deletion tombstones and current access loss. - All eight Git execution checks passed; source, six pinned images, neighboring services and cleanup were verified. - The first harness attempt stopped before header requests because an inherited Python image was missing from its immutable lock. A separately admitted attempt added that exact existing pin; product source and assertions were unchanged. This is source integration. Deployment requires the matching native Core implementation, its database migration, a fresh fenced backup and a verified restore path; merging this PR does not deploy the gateway or grant anyone access.

ClaudiuSchuster added 1 commit

2026-10-22 22:41:20 +00:00

Add native agent work grants to the MCP gateway

access-validation-contract / contract (pull_request) Successful in 3m19s

Details Explain this check

ci / ci (pull_request) Successful in 4m27s

Details Explain this check

6446719b78

ClaudiuSchuster merged commit ac1427f895 into main

2026-10-22 22:50:19 +00:00

ClaudiuSchuster deleted branch oss-oo/native-agent-work-grants-mcp-20261020

2026-10-22 22:50:19 +00:00