Shared State
Create a two-way connection between your React Native UI and agent state.
What is shared state?
Shared state connects your app's UI with the agent's run. With shared state you can:
- Display the agent's current progress and intermediate results
- Update the agent's state through UI interactions
- React to state changes in real time across your app
When should I use this?
Use shared state when you want the agent and the user to work on the same app state. The UI shows what the agent writes. The agent reads what the user changes in the UI.
Building stateful agents?Persistent threads ship with CopilotKit Intelligence on the free Developer tier.Get CopilotKit Intelligence freeReading agent state
Map JSON content to a state snapshot
A .NET agent publishes state as a DataContent update with the
application/json media type. The MapContent mapping on
AGUIStreamOptions is what turns that content into a STATE_SNAPSHOT
event for the frontend. Register it next to AddAGUIServer:
using System.Text.Json;
using AGUI.Abstractions;
using AGUI.Server;
using Microsoft.Extensions.AI;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddAGUIServer();
// Turn the wrapper's JSON DataContent into a STATE_SNAPSHOT event
builder.Services.Configure<AGUIStreamOptions>(options => options.MapContent(content =>
{
if (content is not DataContent { MediaType: "application/json" } data) return null;
try
{
using var document = JsonDocument.Parse(data.Data);
return [new StateSnapshotEvent { Snapshot = document.RootElement.Clone() }];
}
catch (JsonException)
{
return null;
}
}));
var app = builder.Build();Read and write state in an agent wrapper
Wrap your agent in a DelegatingAIAgent. The state the UI sent arrives on
the AG-UI request, which TryGetRunAgentInput recovers from the chat
options. To update the UI, yield the new state as JSON DataContent:
internal sealed class StateStreamingAgent : DelegatingAIAgent
{
// ...
protected override async IAsyncEnumerable<AgentResponseUpdate> RunCoreStreamingAsync(
IEnumerable<AIChatMessage> messages,
AgentSession? session = null,
AgentRunOptions? options = null,
[EnumeratorCancellation] CancellationToken cancellationToken = default)
{
// Recover the state sent in the AG-UI request
JsonElement? currentState = null;
if (options is ChatClientAgentRunOptions { ChatOptions: { } chatOptions } &&
chatOptions.TryGetRunAgentInput(out RunAgentInput? input) &&
input?.State is { ValueKind: JsonValueKind.Object } state)
{
currentState = state;
}
// ... run the inner agent and build the new state snapshot
byte[] stateBytes = JsonSerializer.SerializeToUtf8Bytes(
parsedStateSnapshot,
this._jsonSerializerOptions.GetTypeInfo(typeof(JsonElement)));
// Emit state snapshot as DataContent
yield return new AgentResponseUpdate
{
Contents = [new DataContent(stateBytes, "application/json")]
};
}
}For a full agent that does this, see
SharedStateAgent.cs,
or the
SharedStateAgent sample
in the Agent Framework repository.
Subscribe a component to the agent's state with useAgent. Each time the agent changes its state, for example from a tool call, the hook re-renders your component with the new values.
import { Text, View } from "react-native";
import { useAgent, UseAgentUpdate } from "@copilotkit/react-native/headless";
type NotesState = {
notes?: string[];
preferences?: { tone?: string };
};
export function NotesCard() {
const { agent } = useAgent({
agentId: "default",
updates: [UseAgentUpdate.OnStateChanged],
});
const state = (agent.state ?? {}) as NotesState;
return (
<View style={{ padding: 16, gap: 4 }}>
{(state.notes ?? []).map((note) => (
<Text key={note}>• {note}</Text>
))}
</View>
);
}agent.state is a plain object. Read it like any other React data and render the parts you care about: notes the agent wrote, structured output, progress, or anything else the agent put there.
Writing agent state
The same agent has a setState method. Call it from a UI event, and the agent reads the new value on its next turn. The UI's writes steer the model.
import { Button } from "react-native";
// In NotesCard, below the list:
<Button
title="Prefer short answers"
onPress={() =>
agent.setState({
...state,
preferences: { ...state.preferences, tone: "concise" },
})
}
/>This makes shared state two-way. The UI can send the agent new inputs, such as preferences, selections, or partial work, without the chat.
The agent reads the new state on its next run. To run it right away, call copilotkit.runAgent({ agent }) (from useCopilotKit) after setState. Running through copilotkit also sends your frontend tools and context with the run. To tell the model what changed, add a message first:
const { copilotkit } = useCopilotKit();
agent.setState({ ...state, language: newLanguage });
agent.addMessage({
id: `user-${Date.now()}`,
role: "user",
content: `The language has been updated to ${newLanguage}.`,
});
await copilotkit.runAgent({ agent });See Programmatic Control for more ways to run the agent from code.
Rendering shared state in the UI
Because agent.state is plain React data, the UI layer is whatever you'd normally build. Nothing about it is chat-specific: useAgent works in any component under CopilotKitProvider, so you can render the state on your main screen, not just next to the chat. See Render agent state in your app for the full pattern.
Streaming partial state updates
By default, agent state only updates between backend checkpoints, so a long tool call shows up as one burst at the end. State streaming copies one tool argument into a state key while the model writes it, so the UI shows the answer token by token.
Missing snippet
state-streaming-middleware not found in ms-agent-dotnet::shared-state-streaming. Tag the source lines with // @region[state-streaming-middleware] / // @endregion[state-streaming-middleware].Available: frontend-use-coagent-stateSee State Streaming for the full walkthrough, including the useAgent subscription on the frontend.
Read-only context
When a value is UI-owned, and the agent should read it but never write it back, use useAgentContext instead of shared state. Examples are the current user, the selected record, or the open screen. It sends values one way, from the UI to the agent, and removes them when the component unmounts.
See Agent Read-Only Context for the full pattern.
How is this guide?