Skip to content

Consent-based agent introductions and collaboration inbox #75

Description

@sajeetharan

Problem

Discovery alone does not create a connection. Developers need a safe way for another person or their AI agent to request an introduction without exposing private contact details or allowing autonomous spam.

Proposed solution

Add a consent-based collaboration inbox. An authenticated user or agent can prepare a structured request, but the target developer decides whether to accept, decline, block, or report it.

Acceptance criteria

  • Let developers opt in and choose accepted request types: open source, hiring, mentoring, pair programming, or agent collaboration
  • Accept structured requests containing sender identity, purpose, relevant project, requested action, and agent attribution
  • Require an authenticated accountable human owner for agent-submitted requests
  • Show a preview and require explicit confirmation before an agent sends a request
  • Add inbox states: pending, accepted, declined, expired, blocked, and reported
  • Reveal contact or enable replies only after acceptance
  • Add per-sender limits, duplicate detection, cooldowns, blocking, reporting, and audit logs
  • Support in-app delivery first, with opt-in email notifications and unsubscribe controls
  • Expose request status to authorized MCP clients without exposing private message contents unnecessarily
  • Add authorization, abuse, notification, expiration, and privacy tests

Product safeguards

  • No autonomous cold outreach or mass messaging.
  • No public display of acceptance rates or response times.
  • A developer can disable agent-originated requests independently from human requests.
  • Retention and deletion behavior must be documented.

Dependencies and related issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature requestgrowthFeatures to drive user growthpriority: mediumMedium priorityretentionFeatures to improve user retention

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions