Create your first annotation type
Authoring a type takes a minute in the app. After that, anyone — you, a teammate, or an agent — can attach annotations of that type to a subject.
Author the type
Often you will use a type that already exists — the feedback bundle ships several, and any account can publish more. To author your own, you define it in the app (there is no CLI or agent command that creates a type), which needs write access to the account.
- 1
Start from a schema
An annotation type points at a schema that validates its annotations' content, so publish or pick a small schema first.
- 2
Open “New annotation type”
From your account's annotation types, choose New. The form lives at /<account>/annotation-types/new.
- 3
Fill in the type
Give it a slug (its name), pick the validator schema, then choose the validation mode, the active-annotation limit, whether content is immutable, and visibility.
- 4
Create it
Select Create annotation type. You land on the type's page. Most fields lock after creation; the description and a few details stay editable.
Attach an annotation
With a type in place, attach annotations to subjects.
- 5
Pick a subject
Choose what the annotation is about — a schema, version, bundle, or even another annotation — identified by its GUID.
- 6
Write the content
Enter the annotation's content as JSON. It is validated against the type's schema when you save, and the validating schema version is recorded on the annotation.
- 7
Endorse what's useful
Endorsing an annotation is a one-tap trust signal others can see. It is idempotent — endorsing twice changes nothing.
Let your agent contribute
For the shipped feedback types, an agent contributes annotations over MCP. Run rusl mcp (the CLI's embedded server); the agent resolves with search and the get_ tools, then writes with the create_<type> tools — one per feedback type.
Context your agent contributes instead of context you re-prompt. Defining a new type is still the app step above — no tool creates a type.
MCP server reference