Shared State
Create a two-way connection between your UI and agent state.
What is shared state?
Shared state connects your 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 application
When should I use this?
Use shared state when you want the agent and the user to collaborate through the same application state. The agent's outputs are reflected in the UI, and user updates in the UI are reflected in the agent's execution.
Building stateful agents?Persistent threads ship with CopilotKit Intelligence on the free Developer tier.Get CopilotKit Intelligence freeReading agent state
Install the CopilotKit LangGraph SDK
npm install @copilotkit/sdk-jsWire CopilotKit state into your graph
Shared state requires that your graph's state annotation extends
CopilotKitStateAnnotation's spec. That's what gives the runtime a
place to forward state updates from agent.setState(...).
export interface Preferences {
name?: string;
tone?: "formal" | "casual" | "playful";
language?: string;
interests?: string[];
}
const AgentStateAnnotation = Annotation.Root({
...CopilotKitStateAnnotation.spec,
preferences: Annotation<Preferences | undefined>,
notes: Annotation<string[]>,
});
export type AgentState = typeof AgentStateAnnotation.State;See src/agent/shared-state-read-write.ts for the bidirectional
pattern: a set_notes tool emits a Command({ update: ... }) to
push agent-authored state, and a preferences-injecting chat node
reads UI-authored state every turn.
Subscribe a component to the agent's state with useAgent. Any time the agent mutates its state, for example via a tool call, the composable updates its reactive agent ref and your UI re-renders with the new values.
<script setup lang="ts">
import { computed } from "vue";
import { useAgent, UseAgentUpdate } from "@copilotkit/vue/v2";
type WorkspaceState = {
notes?: string[];
preferences?: { tone?: string };
};
const { agent } = useAgent({
agentId: "workspace",
updates: [UseAgentUpdate.OnStateChanged],
});
const state = computed(
() => (agent.value?.state ?? {}) as WorkspaceState,
);
</script>
<template>
<ul>
<li v-for="note in state.notes ?? []" :key="note">{{ note }}</li>
</ul>
</template>The returned agent.value.state is a plain object. Read it like any other reactive application data and render the parts you care about: agent-written notes, structured outputs, progress indicators, or anything else the agent has put there.
Writing agent state
The same agent object exposes setState. Calling it from a UI event handler pushes the new value into shared state, and the agent reads it back on its next turn. The UI's writes visibly steer the model.
<script setup lang="ts">
function setTone(tone: string) {
const current = agent.value;
if (!current) return;
const previous = (current.state ?? {}) as WorkspaceState;
current.setState({
...previous,
preferences: { ...previous.preferences, tone },
});
}
</script>
<template>
<button @click="setTone('concise')">Prefer concise answers</button>
</template>The UI can also send the agent new inputs, such as preferences, selections, or partial work, without the chat.
Rendering shared state in the UI
Because agent.state is plain data exposed through a Vue ref, the UI layer is ordinary Vue. The example above wires the agent's outputs into a list and feeds user edits back through setState.
Nothing about this is chat-specific: useAgent works in any component under CopilotKitProvider, so you can render shared state in your main view or canvas, not just inside the chat panel. See Render agent state in your app for the full main-view pattern.
<script setup lang="ts">
import { CopilotChat, CopilotKitProvider } from "@copilotkit/vue/v2";
import SharedWorkspace from "./components/SharedWorkspace.vue";
</script>
<template>
<CopilotKitProvider runtime-url="/api/copilotkit">
<SharedWorkspace />
<CopilotChat agent-id="workspace" />
</CopilotKitProvider>
</template>Streaming partial state updates
By default, shared state only updates between backend checkpoints, so a long-running tool call appears as one big burst at the end. State streaming copies a tool argument into a state key while the model writes it, so the UI can watch the answer assemble token-by-token. The sample below is the LangGraph (Python) version.
const streamingConfig = copilotkitCustomizeConfig(config, {
emitIntermediateState: [
{
stateKey: "document",
tool: "write_document",
toolArgument: "document",
},
],
});
const response = await modelWithTools.invoke(
[systemMessage, ...state.messages],
streamingConfig,
);See State streaming for the full walkthrough, including the corresponding 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, such as current user, selected record, or scroll position, reach for useAgentContext instead of full shared state. It publishes values as a one-way UI-to-agent channel that auto-unregisters on unmount.
useAgentContext is a separate read-only capability; it does not replace the bidirectional agent.state / agent.setState(...) contract above.
See Agent read-only context for the full pattern.
How is this guide?