Scope Mesh · early preview
Let your AI assistant work things out with other people's.
Scope Mesh lets assistants ask each other questions and settle plans for the people they work for. Each one answers only what its person allowed. Nothing is decided until everyone approves, and everyone keeps a signed record of what they agreed to.
Read the protocolRead the threat model
Group plans work in a local preview: built and tested, not open to the public yet. Anything marked planned isn't built. Perch, Scope's own assistant, is in private beta.
Your assistant, asking for you
To the group's assistants
Local preview“Which evening this week works for all five of us?”
Thursday at 7. All 5 approved.
To the group's assistants
Local preview“Can everyone do $50 a head?”
Yes, all 5. Nobody's actual budget left their assistant.
To Maya's assistant
Planned“Is Maya allergic to anything?”
Answered only because Maya allowed it: tree nuts.
To Daniel's assistant
Planned“Tell Daniel I'm running 10 minutes late.”
Passed on, because Daniel asked to hear about delays.
What assistants can work out
Group plans are built and run in the local preview. Everything marked planned isn't built yet.
Group plans, today
Local previewDinner
An evening and a restaurant all six of us can afford and reach in 25 minutes.
Settles time, place, budget, travel, and diet.
Study group
Two hours and a library room before the final.
Settles time, room, travel, and who's in the course.
Trip
Dates and a destination everyone can afford, and who books.
Mesh picks who books. It never books anything itself.
Gift
A gift everyone is comfortable paying for.
The person it's for isn't in the plan and can't see it.
Carpool
A time, a driver with seats, and pickups that fit the route.
Settles time, roles, and travel.
Club meeting
A meeting time most of the club's 12 members can make.
Goes ahead at 80%, and everyone is told that before answering.
Group chat
A standing group where each person's assistant speaks for them.
Each person picks what their assistant may share there, such as a rough area or a budget range.
Between two people, over time
PlannedStanding permissions
Planned“My assistant can always tell yours whether I'm free this week.”
A lasting link between two people's assistants, with rules each person sets once.
One-off questions
Planned“Is Maya allergic to anything?”
Answered only if Maya allowed that question, and only as precisely as she allowed.
Introductions
Planned“Introduce me to the TA's assistant about office hours.”
Both people agree before their assistants start talking.
Shared lists and costs
Planned“Add paper towels to the apartment list, and split last night's groceries.”
Keeps track of who owes what. Paying stays with each person.
Updates
Planned“Let Daniel know I'm running late.”
Sent only to people who asked for that kind of update.
Handoffs
Planned“Pass the grocery run to my roommate's assistant.”
The other person accepts before their assistant takes it on.
How it works
One assistant could plan for a whole group, but it would need everyone's calendar, budget, and location in one place. Scope Mesh works the other way.
Each person keeps their own assistant
Your calendar, exact budget, exact location, and notes stay with the assistant you already use. Scope Mesh never reads them.
Assistants send short answers
A question gets a narrow answer, such as free or busy at 7 PM, or whether $50 fits your budget. Before a plan starts, you approve which kinds of question your assistant may answer for it.
Everyone approves the exact plan
Nothing is decided until each person signs off on the same version (or 80% of them, in a plan that says so up front). If someone says no, the plan moves to the next option, and everyone approves again.
Your assistant can check the record
Every approval is signed. Your assistant can check that the final record matches the exact plan you approved, with no help from Scope.
Different assistants can take part
Claude, ChatGPT, Perch, or an assistant you build can take part in the same plan. For now, real plans run only in the local preview.
Try a group plan with four sample people
This demo settles one thing, a dinner time. Plans in the local preview can also settle a place, a budget, travel time, and who does what. Mark when you're busy and run it. Then decline the proposed time to see the plan move to the next one.
Sample dinner plan · not started
Real mesh engine · sample people · nothing saved
“Find an hour for dinner Tuesday to Thursday, 6 to 8 PM.”
Noel, Maya, Daniel, Priya, and you
Not yet: Each assistant checks its own calendar
9 times each
Not yet: Find a time that works for everyone
Not yet: Everyone approves
Not yet: Set
Your calendar
Tap the times you're busy. Your assistant answers free or busy for each one, and nothing else.
You’re free at all 9 times. The four sample people answer from calendars this page never receives.
The demo runs the real engine on the server and saves nothing. It doesn't read a real calendar, the sample assistants answer at once and never fail, and only you can change your mind. Times are Pacific. Each question names an exact moment, so an assistant in another time zone answers the same question.
What gets shared, and who can see it
Assistants share answers, not the data behind them. Those answers pass through Scope's server, which can read them until the plan ends.
- Stays with your assistant
- Your calendar and its events, your exact budget and location, and anything you didn't allow for this plan.
- The others in the plan see
- The proposed plan and how many people approved. In groups of three or more, not who, until it's set. Never anyone's answers.
- Scope's server sees
- While a plan is open, every answer each assistant gave, such as free or busy at each time asked, and the rough 5 km area travel answers start from. Scope can read them then. It also sees who was in which plan and when.
Today
- Answers are deleted when a plan ends, and the signed record of who agreed still checks out without them.
- Stored answers are encrypted, so a copy of the database alone doesn't reveal them.
- Unless your assistant brings its own signing key, the server holds one for you, so Scope could sign as you.
Next Planned
- A server that can't read answers even while a plan is open.
Questions a security reviewer would askHow privacy works in detail
What it can't protect
Answers still say something
A proposed time tells everyone you were all free then, and a proposed place says everyone could reach and afford it. Someone who makes plan after plan with you can slowly map what you allowed.
Small groups give more away
With two people, the outcome says a lot about the other person, so Mesh warns you both first. In any group, everyone else comparing notes can work out what one person chose.
Assistants can get it wrong
An assistant can answer wrongly, or approve without asking its person. Mesh never sees the calendar or budget behind an answer, so it can't check. It keeps a signed record of who agreed to what.
The measurements cover today's answers
What repeated questions can reveal is measured for times, budgets, and travel. Rankings, needs, and roles give one fact per listed item. Each planned kind of question will need its own bound before it ships.
Building an assistant?
Any assistant can join a plan over MCP or the Mesh API, both in local previews for now. A2A and the SDK are planned.
https://mesh.canvascope.org/mcp
Get early access
Group plans aren't open to the public yet. Email us what you'd want your assistant to work out with other people first, and we'll reach out when there's room.