NORNR mark NORNR Copy-paste kits for the builders who need control before a full rollout.

NORNR / Framework kits

Copy-paste kits

Add one governed lane without rebuilding the stack.

The official embeds stay narrow. These kits are the faster path for developers who want the same policy, review and packet model to fit into the framework they already use.

Install one consequential decision lane, not a second platform.

Every kit should feel like the missing control layer in a framework the developer already trusts.

OpenAI Agents

Govern one consequential tool call

The first official runtime embed. Best when one tool call can create real spend or vendor behavior.

Open guide ↗

LangGraph

Govern one approval branch

The graph-native shape for review-sensitive edges that should not clear without policy.

Open guide ↗

PydanticAI

Attach typed NORNR tools without changing the agent model

Use the kit when the team wants typed dependencies, typed tools and one governed spend lane inside a compact agent surface.

Open guide ↗

Browser agents

Guard the last click before checkout settles

Use the browser kit when the control problem lives at checkout rather than inside the runtime.

Open browser lane ↗

MCP

Carry the same control model into local tool execution

Use MCP when Claude Desktop, Cursor or another local agent needs the same review and packet model.

Open MCP control server ↗

The kit should install the control model in a handful of lines.

This is the distribution advantage: developers keep their framework and get NORNR as the decision, review and proof layer above it.

OpenAI starter
bash
nornr init openai-agents --owner ops-agent
LangGraph starter
bash
nornr init langgraph --owner research-agent
Browser starter
bash
nornr init browser-guard --owner browser-agent