Skip to content

[agent] feat: relay verified identity pairing - #8

Merged
alexng353 merged 1 commit into
mainfrom
feat/auth-pairing
Sep 25, 2026
Merged

alexng353 merged 1 commit into
mainfrom
feat/auth-pairing

Conversation

@alexng353

Copy link
Copy Markdown
Member

[agent] Relay identity pairing through expiring opaque Noise messages, while clients verify the receiving terminal before releasing any encrypted identity.

  • Enforce atomic single-receiver claims, source ownership, hashed receiver credentials, phase order, bounded payloads and ten-minute expiry. Delete relay contents on acknowledgement/cancellation and sweep expired rows.
  • Bound active sessions by account, client IPv4/IPv6 network and total storage so creating more accounts cannot bypass the client quota.
  • Adds an additive migration. All 40 API tests pass, including owner/token/phase checks, competing claims, expiration, cleanup and cross-account quota bypass. Real CLI pairing decrypts an existing project secret; rejected/cancelled transfers install nothing.

Deploy before the CLI 2.16.0 release. Existing invite routes are unchanged.

Co-Authored-By: GPT-6 (OpenAI) noreply@openai.com

Add an expiring bounded opaque-message relay with atomic single-receiver claims, owner and receiver authorization, per-client quotas and cleanup. Clients authenticate their peer independently before releasing an encrypted identity.

Co-Authored-By: GPT-6 (OpenAI) <noreply@openai.com>
@alexng353
alexng353 merged commit 1cabb9b into main Sep 25, 2026
1 check passed
@alexng353
alexng353 deleted the feat/auth-pairing branch September 25, 2026 09:38

This branch was successfully deployed

1 active deployment
envx / production — 1cabb9be Deployed Sep 25, 2026 by railway-app[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant