WORKSPACE
What context enters the run?
Local inputs and mounted resources shape what the agent can reach.
Read the research track →Google · Research family · October 2026
Which authority crosses the agent boundary?
Agents carry context through workspaces, sessions, cached state, and tools. Across six Google VRP submissions, Kronowave investigated which authority reaches the next action when that context changes hands.
6submissions
Six submissions across Google agent and developer surfaces share a single research thread: identify the context an action inherits, then compare it with the authority the caller actually supplied.
SESSION
Whose state survives a handoff?
Hosted sessions keep working after one request has ended.
Read the research track →CACHE
Which identity does reused state carry?
Cached objects can outlive the context in which they were created.
Read the research track →TOOL
Which authority reaches the external action?
Tool routing and connections determine the final effect.
Read the research track →The question underneath the work
Who authorizes the next action after context moves?
An agent may begin with one caller and continue through another execution component. The important record is the authority that arrived at the final effect.
WORKSPACE
What context enters the run?
Local inputs and mounted resources shape what the agent can reach.
SESSION
Whose state survives a handoff?
Hosted sessions keep working after one request has ended.
CACHE
Which identity does reused state carry?
Cached objects can outlive the context in which they were created.
TOOL
Which authority reaches the external action?
Tool routing and connections determine the final effect.
How we worked
Keep source, control, and effect on the same line.
The submissions use pinned implementations, healthy reference runs, changed-condition comparisons, and effect receipts to answer one authority question at a time.
01 · Pin
Fix the source
Identify the implementation and runtime under examination.
02 · Control
Run the normal path
Establish the expected authority and healthy effect.
03 · Vary
Change one context
Observe a specific handoff, reuse, or routing boundary.
04 · Read
Check the result
Tie the effect to the actual caller and execution context.
Workspace context · 01
What did this run actually bring with it?
Agent input may include a local workspace, mounted material, and an execution environment.
Research track 01
Workspace context
The research distinguishes the caller’s intended scope from the context made available to the running agent.
Research record
Expected scope
The workspace and resources associated with the authorized run.
Observed scope
The context the runtime used when processing the action.
The point
A useful boundary record names both the initiating authority and the resources the run could exercise.
Session context · 02
A session carries decisions forward.
Hosted execution can retain work and state across individual requests.
Research track 02
Session context
The research follows session identity through continuation and checks which earlier authority the later action inherited.
Research record
Session entry
The initiating request and its authority.
Session continuation
The actor and state associated with a later effect.
The point
A long-lived session needs an account of who is authorizing each consequential continuation.
Cached state · 03
Reused objects need a clear owner.
A cache or retained object may be consulted after the surrounding context changes.
Research track 03
Cached state
The research compares the object’s origin with the authority active when it is used again.
Research record
State creation
The context that produced or stored the object.
State reuse
The context and effect that followed its later use.
The point
The owner of retained state is part of the authority of the action it helps produce.
Tool routing · 04
The final tool call settles the question.
Agent plans can pass through adapters, connections, and provider tools.
Research track 04
Tool routing
The research ties the selected route to the identity and effect recorded at the receiving boundary.
Research record
Requested action
The authority and destination the caller intended.
Recorded action
The identity and result at the tool or provider.
The point
Trace the authority to the system that performed the action.
What the research says together
State is part of authority.
Intent has to survive the trip.
An agent system has to preserve who can act as state moves between components. These Google submissions examine that continuity at four different kinds of boundary.
Evidence
The record behind the work.
Six submissions to Google’s VRP anchor this family with source-pinned experiments, healthy controls, changed-condition comparisons, and execution receipts. The public synthesis shows the authority questions while the submitted reports carry the reproductions.
Work with Kronowave
Which agent action matters to your next decision?
Tell us about the workflow you are shipping. We will start with the action you need to understand.
48-hour Rapid Scan →