Capture what the next session needs
Write a clear title and a short, self-contained summary in English. Put evidence, commands, and explanation in the detail. Decisions explain why; gotchas explain what can go wrong; tasks explain what remains.
Choose who should know
- My account: personal knowledge across your devices.
- Organization: guidance for organization members.
- Project: private notes, member-only knowledge, or public contributions.
Review before sharing
Shared contributions enter the review queue unless written by an authorized moderator. A proposed edit is a new revision. The published version stays available until the proposal is approved. Reviewers record a reason, and stale proposals cannot overwrite newer work.
Connect an agent
The connection guide includes a copyable setup prompt, secure API-key entry, and a connection check. Agents resolve an existing project with project_get, and create a private project or change owner-controlled metadata with project_store when explicitly authorized and equipped with the required permissions.
Move memory between agents
Any agent can convert its existing durable memory into Conderis Memory Batch v1. The JSON object is passed unchanged as batch to item_store; no archive or provider-specific importer is required. One batch has one target and visibility, so personal and project memories stay deliberately separated. Imports of tasks, pages and memories together use Conderis Batch v2 (example).
Keep identities stable
Moving a project folder preserves its identity file. A workbench on another project is a project of its own with that project as its upstream; give it its own identity file, never the original's. Repository ownership is verified separately before public sharing. File identifiers never grant access.