↗
Share from where you are
Browser, email, photos, PDF viewer, notes, file manager, messaging app, desktop context menu, or browser extension.
SOURCE-NATIVE
SHARE EXTENSION · AGENT ROUTER · CONTEXT ENVELOPE · DELIVERY RECEIPT
STOP
COPYING THINGS
INTO AI.
Tap Share. Choose Pass To Agent. Pick the AI that should receive it. The router packages the URL, text, file, image, metadata, and your instruction into a clean handoff — so the right agent gets the right context without five copy/paste steps.
1 share actionfrom the app you are already in
Many agentsresearch · sales · code · personal
Context intactsource + content + instruction
Receiptknow what was actually delivered
● PASS TO AGENT · ROUTING GRAPH
INPUT → CONTEXT → POLICY → AGENT
ANY SOURCEbrowser · email · files · photos
ANY AGENTresearch · work · project · personal
CONTEXT ENVELOPEURL · selection · file · metadata
DELIVERY RECEIPTdestination · status · next action
ShareSOURCE
RouteINTENT
DeliverAGENT
ConfirmRECEIPT
The interaction already has an OS-native foundation: Android’s official Sharesheet is designed to send content to other apps, and Apple’s activity/share-extension system provides a system share surface for passing content to app extensions and services. Pass To Agent turns that familiar gesture into an AI destination router instead of asking users to open an AI app and manually reconstruct context.
The missing layer
AI HAS DESTINATIONS.
YOUR SHARE BUTTON DOESN’T KNOW THEM YET.
The user should not have to remember which app, thread, project, custom agent, or workflow owns a piece of context. Pass To Agent acts as the routing layer between ordinary device sharing and an increasingly fragmented collection of AI destinations.
⌁
Preserve context
Carry URL, title, selected text, attachment, screenshot, MIME type, source app, timestamp, and optional user note as one envelope.
CONTEXT
◇
Route by intent
“Research this,” “add to project,” “follow up,” “fix this,” “remember this,” and “compare this” can map to different destinations.
ROUTER
✓
Know it arrived
Return a delivery receipt with destination, accepted payload, any permission failure, queued task, and next action.
RECEIPT
Agent destinations
ONE SHARE TARGET.
THE RIGHT AI BEHIND IT.
The destination list is yours. Pick a built-in workflow, connect an authenticated agent, or create a custom route.
Choose destination
Your agent switchboard
Concept destinations only; no third-party integration is represented as live in this prototype.
AGENT DESTINATION
The handoff pipeline
PASS THE CONTEXT.
NOT JUST THE CONTENT.
A reliable AI handoff needs more than sending raw text to an endpoint.
Capture
Receive text, URL, image, file, or selection from the OS share system, browser extension, desktop action, clipboard, or API.
Normalize
Create a consistent context envelope: source, content type, metadata, attachment references, user note, and timestamp.
Choose intent
User picks an agent or asks the router to recommend one based on source, content, workspace, and saved routing rules.
Check permission
Verify destination authentication, payload scope, workspace, data sensitivity, and whether the agent is allowed to act or only read.
Deliver
Send through the destination’s supported transport: deep link, app extension, API, connector, automation, or standards-based interface.
Receipt
Return what accepted the handoff, what was sent, whether a task was created, and whether additional approval is required.
Smart Router
WHEN YOU DON’T KNOW WHICH AGENT SHOULD GET IT, THE ROUTER SHOULD.
The routing engine can recommend a destination from content type, source, keyword, workspace, saved rules, and requested outcome — while keeping the final handoff visible to the user.
Platform surfaces
PASS TO AGENT SHOULD APPEAR
WHERE “SHARE” ALREADY LIVES.
The product becomes useful when it behaves like infrastructure instead of another destination you have to remember to open.
iPhone / iPad
Share extension / activity view entry point. Receive supported shared content, show destination picker, and hand off through the containing app or authenticated service.
Android
Share target in the Android Sharesheet using the platform sharing/intents model for text, links, and supported files.
Browser Extension
Right-click or toolbar action for current page, selected text, image, tab group, or downloaded content.
Desktop
Context-menu / services integration, drag-and-drop target, clipboard action, and global shortcut for files and selections.
API / MCP / Connectors
Custom destinations can expose authenticated APIs or standards-compatible capabilities. MCP is relevant as an open standard for connecting AI applications to external tools/data, but Pass To Agent remains a routing product rather than “an MCP replacement.”
Permission model
THE ROUTER SHOULD NEVER SILENTLY UPGRADE A SHARE INTO AN ACTION.
Sending context to an AI is not the same as authorizing that AI to send email, update CRM, publish content, delete files, or execute code. Pass To Agent should keep data access and action authority separate.
✓Destination-specific authentication
✓Read vs write/action scopes
✓Sensitivity labels and routing policy
✓Explicit approval for high-impact actions
✓Delivery and action receipts
Privacy model
“PASS” SHOULD MEAN EXACTLY WHAT THE USER CAN SEE.
The preview should show the content envelope before delivery: what text, which file, which URL, which metadata, which destination, and whether the destination keeps memory or can call tools.
✓Envelope preview before send
✓Minimize metadata by default
✓Private local routing rules where possible
✓No invisible cross-agent memory sharing
✓Per-destination retention disclosure
Product integrity
ONE TAP SHOULD SAVE TIME.
NOT HIDE CONSEQUENCES.
The core design rule is simple: make routing faster without making permission less visible.
01
No fake integrations
The prototype does not claim current partnerships with ChatGPT, Claude, Gemini, Apple, Google, MCP maintainers, or any specific AI vendor.
02
No silent agent actions
A content handoff should default to reading/analysis unless the destination and user explicitly authorize a stronger action.
03
No mystery payload
Users should be able to preview exactly what is leaving the source app before it reaches the destination.
04
No one giant AI inbox
The product succeeds when it routes context to specialized agents/workspaces, not when it becomes another place where everything is dumped.
Product boundaries
THE SHARE BUTTON
FOR YOUR AI TEAM.
No indexed public product site surfaced in the current domain check. This is a greenfield product and website prototype.
No. The product is the routing layer before the chatbot or agent. It captures something you are already viewing and passes it to the destination that should handle it.
You can. Pass To Agent exists to remove the repeated steps: switching apps, finding the correct destination, pasting, re-explaining the source, attaching files, and describing what you want done.
Yes. Apple provides share/activity extension mechanisms and Android provides the Sharesheet / sharing intents for passing content to other apps. A production implementation would follow each platform’s current rules and supported content types.
MCP is an open standard for connecting AI applications to tools and data. It can be one useful integration layer for compatible destinations, but Pass To Agent’s product job is routing user-shared context to the correct destination, regardless of whether that destination uses MCP, a vendor API, a deep link, or another connector.
Yes as a recommendation, with user-visible routing rules and permission checks. Sensitive or high-impact routes should require confirmation rather than silently forwarding content or executing actions.
Pass To Agent
YOU ALREADY KNOW HOW TO SHARE.
NOW SHARE TO INTELLIGENCE.
One familiar action. The right context envelope. The right AI destination. A receipt when it arrives.