Agents' next frontier: agent-to-agent and network effects — Jean-Denis Greze, Town
Read the talk
Agents’ next frontier: agent-to-agent and network effects
Jean-Denis Greze reframes agent collaboration as a search problem: how can the right information reach the next model call when it belongs to someone else? Five approaches move the privacy decision to different points in that process.
From a talk by Jean-Denis Greze
At a glance
Ideas worth remembering
Evaluate agent collaboration by whether it brings the right information into the consequential model call. Privacy limits that search even when context capacity is unlimited.
Custom tools can search broadly while returning limited results, such as relationship scores. Their privacy tradeoffs still require deliberate design and user acceptance.
A sweeper agent turns private work into proposed shared knowledge using retention policies and destination descriptions. Human approval and automatic policy enforcement offer different levels of disclosure control.
Searching before requesting consent can spare irrelevant owners an approval prompt, but it requires trusting broad internal access and controlling the final disclosure.
Begin automatic sharing with an accepted low-sensitivity zone. Persistent errors, prompt injection, disclosure mistakes, and audit needs remain part of the design as that zone grows.
The useful unit is the call with the right context
People get work done with other people. Assistants should benefit from the same connections: another person’s agent may hold the information needed to complete your task. Jean-Denis Greze, introducing himself as Town’s CTO after seven years as CTO at Plaid, starts from that opportunity and immediately questions its framing. “Agent to agent” tells us who communicates. It does less to explain what makes the result useful.
The alternative framing is search. Immediately before a model returns an answer or calls a tool, its context window needs the information required for that decision. A more capable model can do more with that information, but the surrounding system still has to find it and bring it into context. Collaboration matters when it improves that process. 1:13
Greze sketches a progression from humans manually filling the context window, to retrieval-augmented generation using a search tool, to agentic search using multiple tools to explore available content. Each changes how information arrives. The engineering target remains the consequential model call: does it have the content needed to choose the right action?
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The impossible agent that can see everything
Imagine a single agent with access to everyone’s email, every company’s records, and every government’s information. In Greze’s thought experiment, it can assemble all the relevant context before answering. This gives multi-agent systems a comparison point: how closely can they approach the information available to that agent? The optimal outcome is an idealization within this model of the problem, rather than a demonstrated guarantee that complete access makes an LLM correct.
Even an infinite context window would not make this agent acceptable. People do not grant strangers continuous access to their inboxes. Privacy and security restrict what can enter the search process before context length becomes relevant. Greze invokes the Coase theorem as an analogy: removing information barriers and transaction costs can improve negotiation outcomes, while real-world constraints prevent the frictionless ideal. Here, the constraint is permission to use information.
The five approaches that follow place that permission decision in different places. Some restrict the searchable data in advance. Others permit broad internal search and control what leaves it. Their usefulness depends both on the information they recover and on how much human work they require as models improve.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Restrict access, or restrict what a tool returns
The first strategy gives an agent broad access inside an existing trust boundary. An HR team agent might read the HR systems available to an employee, perhaps using the access level of the team’s most junior member. Everyone on the team can ask it questions. This fits a familiar SaaS security model, which helps explain its appeal to IT and security teams.
Its limitation is structural. Humans still choose the accessible data, and information outside that selection remains outside it. Better models may answer better within the permitted material, but they do not automatically dissolve the divisions between teams. Greze’s two tests are whether the system naturally needs fewer humans over time and whether model improvements expand what the approach can accomplish. A manually defined team silo fares poorly on both.
The second strategy builds tools that trade some information for a useful capability. Consider the question that returns throughout the talk: does anyone at the company know someone on Acme Corp’s finance team? Unrestricted search would read everyone’s Gmail, identify exchanges with Acme employees, inspect profiles, and find a connection to the CFO. That would also expose far more correspondence than the requester needs.
A narrower tool can accept a company domain and a target role, search the mail internally, and return ranked relationship-strength scores. The requesting agent receives a useful result without receiving the underlying emails. It then messages Bob on Slack about his connection to Jane, Acme’s CFO. Bob confirms the relationship and agrees to an introduction. The observable change is from a broad question about the company’s network to a specific, approved introduction; the tool supplies the discovery step, while Bob supplies consent for the next action.
- Relationship lookup: Broad mail access stays inside a purpose-built tool; the agent receives a limited relationship result and contacts the relevant colleague.
- Draft placement: Colleagues can put draft emails in someone’s inbox, reducing the clicks needed when sales staff would otherwise ask that person to write an introduction.
Town uses this kind of tool for some recurring user activities, with an opt-out. More participants make more connections available, creating the proposed network effect. But privacy is still a product decision: people must understand and accept the information a tool reveals. Humans design each tool and explain its behavior, so the approach remains largely manual rather than expanding automatically with model capability.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Search first, ask the person whose information matters
The fourth strategy keeps humans in the information path. Your agent asks another person’s agent about an Acme finance connection. That person approves searching their email, sees the result, and separately approves sending it back. Consent precedes both discovery and disclosure.
This becomes expensive when only a few people hold the answer. In the hypothetical hundred-person company, the question can trigger a hundred Slack requests for permission. Most people must respond simply to establish that their information is irrelevant. Human attention becomes part of the search cost.
The fifth strategy, the black box, changes the timing. A trusted LLM can search across private silos without asking each owner first, while its trace remains inaccessible to ordinary participants. It stops at the answer-sharing point or before a write tool call, identifies the information needed for that output or action, and requests approval from the people who own it. Greze presents this as a powerful design he has rarely seen in practice.
Return to Bob and Jane. The request goes to all the company’s agents, which search Gmail and other private stores automatically. The black-box agent receives twenty matching connections, compares their strength using the email contacts, and selects Bob. Only then does Bob receive a prompt asking whether his connection to Jane may be shared with Jean-Denis for an introduction. The change from the previous approach is visible: discovery still spans a hundred people’s information, but the approval request reaches the selected owner.
Where does human attention enter this search? The diagram places Bob’s approval after candidate discovery and ranking, before disclosure. That saves irrelevant approval requests by giving the internal search much broader access. The privacy decision has moved later; the need to trust the search system has grown.
The final output must contain only information approved for sharing. Even a narrow relationship answer can expose something sensitive: asking about a connection to a recruiter at another company could reveal that a colleague is interviewing there. Hiding the search trace does not remove that inference. The approval step and the content allowed through it need careful design.
The Acme introduction through a black box
Read the diagram as text
- Find an Acme CFO connection. requester — Jean-Denis asks the company-wide question.
- Search private silos. trusted-search — Company agents inspect Gmail and private information without individual search approvals.
- Twenty connections. trusted-search — The black-box agent receives the matching candidates.
- Select Bob. trusted-search — Compare connection strength using the email contacts.
- Ask Bob. owner — May his connection to Jane be shared for the introduction?
- Approved disclosure. requester — Share the approved relationship information with Jean-Denis.
- Find an Acme CFO connection → Search private silos: Distribute request to agents.
- Search private silos → Twenty connections: Return matching connections internally.
- Twenty connections → Select Bob: Compare strength.
- Select Bob → Ask Bob: Request selected owner’s consent.
- Ask Bob → Approved disclosure: Proceed after approval.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Start with a low-sensitivity zone
The proposed frontier is automatic judgment about when permission is necessary. Greze compares it to coding workflows that moved from approving every action, through “YOLO” execution, toward an auto mode that intervenes selectively. For information sharing, the corresponding design separates low-sensitivity material that may move automatically from material that needs human review or always requires approval.
Supplier meeting notes make the decision concrete. A user asks for notes from a weekly recurring call with a supplier and its finance team. In the proposed system, the model examines the notes, considers the requester’s role, and decides whether disclosure is acceptable without asking everyone involved. The presence of finance participants alone does not settle the decision; content and role inform the risk judgment.
This design gives model improvements somewhere useful to go. Better judgment, clearer policies, and carefully designed tools could expand the set of sharing decisions handled automatically, including decisions about when to involve a human. Greze’s recommendation is to define a low-sensitivity zone where the organization already accepts model discretion, then develop from there. Expansion remains conditional on those improvements; a more capable model does not itself grant permission to disclose more.
The desired outcome is less human coordination work as the system improves. Greze gives that ambition a pleasantly concrete destination: a beach in Hawaii with his kids. The architectural question underneath it is whether better models can take over more of the information-routing work, rather than leave humans maintaining the same silos and approving the same requests.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The harder network effect crosses company lines
Within a company, shared governance offers a starting point for agreement about access and disclosure. The larger opportunity is getting several companies to accept a common agent working across their private information. That requires a use case valuable enough for each participant to permit some cooperation while retaining restrictions on what may be accessed or shared.
Greze describes an unnamed finance company exploring this direction with investment banks. The potential benefit is sharing private information about private companies for activities such as lending, with agents helping decide what can be accessed. The example is exploratory and unnamed, so it supports a possible beachhead rather than a proven deployment. Its appeal is that another institution’s participation could make useful information available that no single participant holds alone.
The ending leaves a real question open: how comfortable should people become with agents deciding privacy? Greze expects more decisions to move in that direction, yet does not claim to trust a future in which agents make all of them. The opportunity and the hesitation belong together. Work across silos can become more useful as judgment improves, while every new connection still needs an acceptable answer to who may learn what.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
Related talks
- Agentic Search for Context Engineering
Continues the opening question of how search supplies useful context before an agent acts.
- Don't Build Agents, Build Skills Instead
Develops reusable procedural knowledge, one of the shared-space examples in this recording.
- Your company brain will leak secrets: how we stopped it for big banks — Tanmai Gopal, PromptQL
Offers a closely related topic for the disclosure risks of shared company knowledge and the closing investment-bank example.
Transcript & slides
Loading transcript and slides…