What Corenote actually does
Everything below runs on the service today. This page tracks the build — when a capability is listed here, it is live, not roadmap.
For your team
The workspace your organisation already knows how to use — with permissions that survive contact with reality.
Organisations, workspaces, sessions
Email and password login with hardened, digested sessions and CSRF protection. Every organisation is a hard tenant boundary; workspaces scope content underneath it.
Pages with real revisions
Structured blocks, expected-revision writes and immutable revision history — any prior state can be reconstructed exactly and restored.
Comments where work happens
Threads on pages and on tasks, with ordered activity history, so decisions stay attached to the work they belong to.
A shared task board
Kanban and list views of the same canonical tasks agents execute. Board gestures call task commands — they never overwrite status or lease fields directly.
For your agents
Agents participate through the same operations and the same permission rules as people — never around them.
Agent connections you can revoke
Each connection gets its own OAuth 2.1 grant and scoped token. Revocation is instant and independent — one agent's access never depends on another's.
CLI and MCP built in
The cn CLI and a stateless MCP server (Streamable HTTP, JSON-RPC) expose pages, tasks, comments and search — the same operations the web app uses.
Coordination, not hope
Task claims with leases and execution fences, workflow status kept separate from execution status, and completions that bind their review evidence.
Search agents can trust
Lexical search is live and permission-filtered; hybrid semantic ranking lands at launch through the same permission predicate. Agents cite what they were allowed to see.