AppNotes puts shared comments on the live website. A product team, client, or coding agent sees feedback in the interface where it belongs instead of reconstructing it from screenshots and tickets.
Choose how you want to use AppNotes
| Mode | Best for | Account | Storage |
|---|---|---|---|
| Local | Private notes for one person in one browser | None | Browser only |
| Connected | Shared Sites, notes, replies, guests, history, and agent access | AppNotes account | Hosted AppNotes service |
| Self-hosted | AppNotes inside your own network | Your OIDC provider | Your SQLite database and filesystem |
Local and connected modes are intentionally separate. AppNotes never uploads local notes when you sign in or switch to connected mode.
Start here
- Quickstart: understand the shortest path from a web app to the first note.
- Install the SDK: add local or connected AppNotes to a site.
- Sites: learn the exact-origin registration model and active-Site limits.
- Agents: install the Skill, create an API key, and let an agent register Sites.
- Self-hosting: understand the portable container, OIDC, SQLite, and filesystem deployment.
- HTTP API: authenticate agents and work with Sites, notes, replies, guest links, and API keys.
The product model
Connected AppNotes uses one small hierarchy:
Organization
└── Site
└── Note
└── ReplyA Site is one exact HTTP or HTTPS origin, such as https://checkout.example.com. Wildcards are invalid. A note can target one primary element and up to seven additional elements. Text selections and regions remain single-target.
The live website is the authoritative canvas. The connected web app is where you organize Sites, review the queue, manage team access, create guest links, and issue agent API keys.