feat(contracts): define bounded embedded browser messages - #63
Draft
John-Ryan21337 wants to merge 1 commit into
Draft
John-Ryan21337 wants to merge 1 commit into
John-Ryan21337 wants to merge 1 commit into
Conversation
This was referenced Sep 11, 2026
Merged
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
Adds bounded schemas for embedded-browser tabs, viewport controls, redacted snapshots, action results, and thread/provider browser requests. This is an optional interface proposal extracted from the working Club Code browser. It does not register IPC, RPC, MCP tools, settings, or a browser UI.
Browser-specific identities and payloads have finite limits. Browser timestamps require valid canonical UTC values. Decoding never grants access: native ownership, origin sharing, request expiry, revocation, and target freshness remain runtime responsibilities.
Why
The complete browser spans native Electron views, the renderer, and provider tooling. A schema-only boundary lets maintainers review the interface before deciding whether to adopt those components. It has no prerequisite PR and is based on current
devat99fbaec89da429924171c89d66a8f3455e42d9b0.The full working implementation and feature adoption guide are in Club Code publication PR #66. Later native/browser and broker integrations depend on this interface; merging this PR alone does not provide browsing. It does not replace current Cafe provider versions or adapters.
Validation
9ba96db2.yarn fmt,yarn lint, and fullyarn typecheckpassed. Lint reports existing warnings.yarn build:desktop --forcepassed, with fresh nonempty desktop/server/web artifacts verified.Checklist
日本語:現行Cafe
dev向けのブラウザー通信スキーマです。UI・エンドポイント・権限は有効にしません。実装全体の採用を決める前に、境界と上限を個別に確認できます。後続のネイティブ表示・エージェント連携には別の実装が必要です。