# Agent Read-Only Context

> Send UI values to the agent as a one-way, read-only channel with useAgentContext.

## What is this? [#what-is-this]

Sometimes you want the agent to *know* something about the current UI, like the signed-in user, the open screen, or a recent activity log, but you don't want the agent to change it. That's what `useAgentContext` is for: a one-way **UI → agent** channel for read-only context.

Unlike full shared state, where the agent can write state back to the UI, `useAgentContext` values are pure inputs. The agent sees them on every turn, but it has no setter and no tool to write them back.

## When should I use this? [#when-should-i-use-this]

Use `useAgentContext` instead of full shared state when:

- The value is **UI-owned** and means nothing to the agent beyond "what the user is looking at right now".
- The agent should read but never write (user identity, feature flags, selected record, open screen).
- You want the value to go away when the component unmounts. For example, the "current record" context disappears when the user leaves that screen.

Think of it as "props for the agent".

If the agent must also write the value, use **[shared state](/react-native/pydantic-ai/shared-state)**. To stream agent-written state to the UI during a run, see [State Streaming](/react-native/pydantic-ai/shared-state/streaming).

## How it works in code [#how-it-works-in-code]

<Callout type="warn" title="Pydantic AI does not pass context to your agent">
  Pydantic AI's AG-UI adapter passes `messages`, `tools`, and `state` to your
  agent. It does **not** pass `context`, and it does not warn when it drops the
  entries. An agent that never received your entries still answers confidently
  about them. This is deliberate: entries are client-submitted, so Pydantic AI
  leaves it to you to decide what to trust. Read them off `run_input` and hand
  them to the agent yourself. See Pydantic AI's
  [AG-UI Context guide](https://pydantic.dev/docs/ai/integrations/ui/ag-ui/#context).
</Callout>

<Steps>
  <Step>
    ### Pass the entries to the agent through `deps`

    The entries arrive on `RunAgentInput.context`. Build the adapter in two
    steps so you can reach `run_input`, pass the entries into `deps`, and
    expose them to the model through a tool.

    ```python title="agent.py"
    import json
    from dataclasses import dataclass

    from ag_ui.core import Context
    from pydantic_ai import Agent, RunContext
    from pydantic_ai.ui.ag_ui import AGUIAdapter
    from starlette.applications import Starlette
    from starlette.requests import Request
    from starlette.responses import Response
    from starlette.routing import Route


    @dataclass
    class AppContextDeps:
        """The entries the frontend shared on this run."""

        context: list[Context]


    agent = Agent(
        "openai:gpt-6-luna",
        instructions="You are a helpful assistant that can help emailing colleagues.",
        deps_type=AppContextDeps, # [!code highlight]
    )


    # [!code highlight:10]
    @agent.tool
    def colleagues(ctx: RunContext[AppContextDeps]) -> list[dict]:
        """The current user's colleagues, as the app shared them."""
        for entry in ctx.deps.context:
            if entry.description == "The current user's colleagues":
                # `useAgentContext` JSON-stringifies `value` before it leaves the
                # browser, and AG-UI types `Context.value` as a string, so parse it.
                return json.loads(entry.value)
        return []


    async def run_agent(request: Request) -> Response:
        # `dispatch_request` parses the request internally, so build the adapter in
        # two steps instead: `run_input` is what carries the frontend's entries.
        # [!code highlight:4]
        adapter = await AGUIAdapter.from_request(request, agent=agent)
        deps = AppContextDeps(context=adapter.run_input.context)
        return adapter.streaming_response(adapter.run_stream(deps=deps))


    app = Starlette(routes=[Route("/", run_agent, methods=["POST"])])
    ```

    Two details are easy to miss:

    - **`value` is a string, not your object.** `useAgentContext` calls
      `JSON.stringify` on the value before the run leaves the browser, and
      AG-UI types `Context.value` as a string on both ends. So `json.loads` is
      required, and a shape check like `isinstance(entry.value, list)` can
      never pass.
    - **Use `from_request`, not `dispatch_request`.** The one-line
      `AGUIAdapter.dispatch_request(request, agent=agent)` parses the request
      for you, which leaves you no `run_input` to build `deps` from.

  </Step>
  <Step>
    ### Keep entries as data, not instructions

    Every entry is a claim your frontend made. It never establishes who is
    making the request. Deliver entries to the model as **data**, the way the
    tool above does. Do not build
    [`instructions`](https://pydantic.dev/docs/ai/agents/#instructions) out of
    them: instructions carry operator authority, so composing them from
    client-submitted text lets a prompt injection inherit that authority.

    Facts your *server* established (the authenticated user, the workspace,
    the tenant) are what belong in instructions.

  </Step>
</Steps>

Call `useAgentContext({ description, value })` once per value you want to send. Each call registers a context entry that is:

- Refreshed whenever `value` changes.
- Removed when the component unmounts.
- Sent to the agent with every run. The Built-in Agent adds each entry to the system prompt. Python LangGraph agents need `CopilotKitMiddleware` to add the entries, and ADK agents need an instruction provider. Microsoft Agent Framework, CrewAI Flows, and Pydantic AI agents drop the entries silently unless you wire them. The setup above shows the code for your framework.

```tsx title="src/ProfileScreen.tsx"
import { Text, View } from "react-native";
import { useAgentContext } from "@copilotkit/react-native/headless";

export function ProfileScreen({
  userName,
  timezone,
  recentActivity,
}: {
  userName: string;
  timezone: string;
  recentActivity: string[];
}) {
  useAgentContext({ // [!code highlight:4]
    description: "The signed-in user's name and timezone",
    value: { userName, timezone },
  });

  useAgentContext({
    description: "The last actions the user took in the app, newest first",
    value: recentActivity,
  });

  return (
    <View style={{ padding: 16 }}>
      <Text>Signed in as {userName}</Text>
    </View>
  );
}
```

The `description` matters. It's a short label the agent sees next to the value, so it knows what to do with it. Treat it like a parameter docstring.

Call `useAgentContext` in as many components as you like. The agent receives every entry that is registered at the time of the run.

<Callout type="warn" title="Context values arrive as JSON strings">
  The AG-UI protocol defines a context value as a string. Therefore
  `useAgentContext` calls `JSON.stringify` on any `value` that is not already a
  string, and your agent receives the JSON text instead of the object or the
  array.

  Parse the value before you read a field from it. Use `json.loads(item["value"])`
  in Python, or `JSON.parse(item.value)` in TypeScript. If you skip the parse
  step, an index such as `colleagues[0]` returns a single character, and a shape
  check such as `isinstance(value, list)` can never pass.

  Do not stringify the value again, because that produces double encoding. A
  `value` that is already a string is sent unchanged, so no parse step is needed
  for it.
</Callout>

## Wire it to your own state [#wire-it-to-your-own-state]

`useAgentContext` doesn't care where the value comes from: local state, a React context, Redux, a query cache, or your navigation state. The value must be JSON-serializable. Its serialized form is compared on each render, so a new object with the same contents does not register the entry again.

## Rendering data does not send it [#rendering-data-does-not-send-it]

A screen that renders a list has put the list in the view tree, not in the agent's context. Those are separate steps. An agent without the second step still answers: the text reads well, the values look plausible, and nothing errors.

Register the data with `useAgentContext`, and tell the agent in its instructions to refuse to answer about records that the context doesn't carry. Then check one answer against the records your app actually holds.

## Treat entries as untrusted input [#treat-entries-as-untrusted-input]

Every entry is a claim your app made, and a user can change it. It never proves who is making the request. Let entries inform the agent's answer, but take facts that grant access, such as the authenticated user, the workspace, or the tenant, from your server. If your agent builds its prompt from entries, keep them apart from your own instructions, so text in an entry can't override them.

## Try it [#try-it]

Ask the agent: "What is my name?" It answers with the value of `userName`. Change the name in your app and ask again: the answer changes.

For every option, see the [`useAgentContext` reference](/reference/react-native/hooks/useAgentContext).
