Rozenite for Agents

    Rozenite for Agents is the agent-facing way to interact with React Native DevTools and Rozenite plugins. It gives coding agents a reliable interface for inspecting a running React Native app through Rozenite, including logs, network activity, React profiling data, and plugin-specific tooling.

    You can access this workflow through the rozenite agent CLI or, if you need direct programmatic access, through @rozenite/agent-sdk. For most users, the CLI is still the recommended starting point.

    Experimental

    This functionality is experimental and may not work in all cases. If you run into a bug, please open an issue.

    What coding agents use it for

    • Read app logs while debugging a failure
    • Capture and inspect network requests during a user flow
    • Run React profiling when investigating slow renders
    • Use tools exposed by installed Rozenite plugins
    • Use app-defined custom tools registered directly by the running app
    • Work against the connected app target without inventing custom instrumentation

    Before you start

    Make sure:

    • Rozenite is installed and configured for the app
    • your app is running in development mode
    • Metro is running
    • at least one React Native target is connected

    If you have more than one simulator, emulator, or device connected, you will need to choose which one to inspect.

    Rozenite for Agents requires a project with Rozenite already installed and configured. The agent skills teach your coding agent how to use that setup effectively.

    Rozenite for Agents is designed for AI and coding agents first. The underlying CLI can be called directly with npx rozenite, but the intended use is for an agent to drive it while debugging or implementing changes in a React Native app.

    React Native DevTools will disconnect

    Rozenite for Agents acts as a debugger connection to the running app. Because of a current React Native limitation, starting an agent session will disconnect React Native DevTools if it is already attached.

    This is a platform limitation rather than a Rozenite-specific design choice. Support for multiple simultaneous debugger connections is being worked on, and once React Native allows that, Rozenite for Agents will be able to coexist with React Native DevTools.

    How agents usually work with it

    The typical flow is:

    1. Connect to a running app target by creating or reusing a session.
    2. Discover which Rozenite domains are available for that target.
    3. Use the relevant domain to inspect the app state or collect debugging data.

    Built-in domains include console, network, react, performance, and memory.

    Runtime domains can also come from installed Rozenite plugins. At the moment, the documented agent-capable plugin domains include:

    • @rozenite/controls-plugin
    • @rozenite/file-system-plugin
    • @rozenite/react-navigation-plugin
    • @rozenite/mmkv-plugin
    • @rozenite/network-activity-plugin
    • @rozenite/redux-devtools-plugin
    • @rozenite/storage-plugin
    • @rozenite/tanstack-query-plugin

    Prefer the built-in network domain first when it is available. @rozenite/network-activity-plugin is the documented fallback plugin domain for apps where the built-in network domain is unavailable.

    Apps can also expose in-app custom tools. These are runtime tools registered directly by the app instead of by a separate Rozenite plugin package.

    If you want to give a coding agent this workflow directly, install the rozenite-agent skill for CLI workflows or rozenite-agent-sdk for SDK-driven scripts and automations.

    Next steps

    • Install the Agent Skills (rozenite-agent for CLI workflows, rozenite-agent-sdk for code-first SDK workflows) if you want Codex or another coding agent to use Rozenite effectively.
    • Adding tools to your application – expose custom tools from your app for agents to call.
    • Making your plugin agent-enabled – expose tools from your Rozenite plugin to agents.
    • Agent SDK – build custom tooling or automation on top of the agent workflow.

    Need React or React Native expertise you can count on?

    Let's talk