Repository navigation
Add Link wallet support with Eve 0.66.3 - #149
Merged
Merged
Conversation
10 tasks
This branch was successfully 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.
Adds Link wallet connection and purchasing through the official Eve extension, pinned to Eve 0.66.3 and
@stripe/link-integrations-eve0.2.4.Existing phone users connect Link from
/link, linked from workspace Connections. Better Auth stores encrypted OAuth grants, refreshes them under a database lock, and revokes them on disconnect. Link configuration remains optional for deployments; the setup page explains the required environment variables and callback URL.For browser purchases, the coordinator creates and checks a Link spend request through the extension, then passes its approved ID to the browser worker. The worker retrieves card details server-side, checks caller and browser ownership, current approval, merchant origin, amount, currency, and expiry, and uses the existing Kernel-backed Chromium autofill. Its result contains only a receipt. The coordinator's retrieval override omits credential expansion, and both agents have instructions for approval, continuation, submission, and uncertain outcomes. Payment fills no longer automatically retry another control after an error.
Review the OAuth ownership and refresh boundary, status-only extension override, and worker checks before card injection. The browser bridge currently supports one-time card forms on the approved merchant origin. Cross-origin payment frames, recurring requests, Shared Payment Tokens, and Link Pay Tokens are unsupported. Autofill completion is not evidence that an order succeeded.
Validation:
pnpm check— 764 tests across 88 files; lint, type checking, formatting, and Knip passed.DATABASE_URL=postgresql://postgres:postgres@127.0.0.1:54329/open_instinct KERNEL_API_KEY=build-only BETTER_AUTH_URL=http://localhost:3000 pnpm build— passed.pnpm exec eve build --skip-sandbox-prewarm— passed; compiled output selects the status-only override and worker fill tool.Link HTTP and browser CDP boundaries are mocked in regression tests. No live Link payment was performed; local Link OAuth credentials are not configured. Sandbox image prewarming was skipped.