Harnesses

Cursor

Adapter ID

cursor

Vendor

Anysphere

Docs

cursor.com

Scope

Project

Native

5 of 10

Emulated

1 of 10

Planned

4 of 10

Round-trip

Digest-verified

Cursor's agent (editor + CLI). The richest instructions mapping — all four activation modes are native rules.

Pack & unpack

# capture an existing Cursor project as a bundle
uap pack --from cursor

# install a bundle into a Cursor project
uap unpack --to cursor

# convert from Cursor to any other harness
uap convert --from cursor --to <harness>

Where components land

Paths are project-scope, relative to the directory you pack/unpack. Every location below is where Cursor actually reads the component — verified against the official docs.

Component	Location	Support
Instructions	`.cursor/rules/<name>.mdc` always / auto+paths / auto / manual map 1:1 to the four Cursor rule types.	Native
Commands	`.cursor/commands/<name>.md`	Native
Subagents	`.cursor/agents/<name>.md`	Native
Skills	`.cursor/skills/<name>/`	Native
MCP servers	`.cursor/mcp.json` No SSE/HTTP discriminator — SSE reads back as HTTP (reported emulated).	Native
Hooks	`.cursor/hooks.json`	Planned
Permissions	`.cursor/cli.json`	Planned
Setup	`hook`	Planned
Env	`—`	Planned
Files	`project root`	Emulated

Fidelity notes

Components marked Native round-trip losslessly — pack(unpack(D)) ≡ D, digest-verified by the conformance suite.
Components marked Emulated install a faithful approximation and are flagged in the fidelity report so nothing is silently lost.
Components marked Planned are reported as skipped today; the target location shown is where the adapter will install them.