Versions

For agents and people who connect agents to Conderis. The server now offers eight tools instead of 27, and the tool list costs about 6,500 characters of context instead of about 19,000 (#309, #317). The old tool names no longer exist; an agent that calls one receives an unknown-tool error.

What to do

• Reload the MCP connection in every client, so the client fetches the new tool list.
• Replace old tool names in your own instructions (for example a global CLAUDE.md or AGENTS.md): memory_recall becomes recall, and memory_store becomes item_store with kind: "memory". The table below lists the rest.
• Read the system guide once with recall and guide=true. Version 31 was the first for v2; the current one is named at the top of every recall.

The eight tools

Tool	Purpose
recall	Session start: instructions, active tasks, pages and memories within a budget; guide=true returns the system guide.
project_get	Your projects, or one project with your permissions, assignable people and agents, and counts.
project_store	Create or change a project.
item_get	One task, memory, page, proposal or the instructions; history=true, version, offset/take.
item_list	Short entries of one kind, with query, filter, sort and cursor paging.
item_store	Create or change items, or store a batch.
item_action	Claim, complete, block and unblock tasks; archive and restore; relate; approve, reject and withdraw proposals.
item_delete	Request permanent deletion of private data posted by mistake.

Old tool, new call

Before	Now
system_memory	recall with guide=true
memory_recall	recall
project_list	project_get without projectId
project_create, project_update	project_store
task_assignee_list	project_get with projectId (assignees)
memory_get, item_get, proposal_get	item_get (a proposal with ref: "proposal:<id>")
task_list, item_search, proposal queue	item_list with kind, optionally query
item_history	item_get with history=true
memory_store, page_store, task_create, task_patch	item_store with kind and fields
task_claim, task_complete	item_action with claim or complete
item_archive	item_action with archive or restore
relation_create, relation_remove	item_action with relate or unrelate
relation_list	item_get (direct relations are part of the item)
proposal_review, proposal_withdraw	item_action with approve, reject or withdraw
item_delete	item_delete (a single version with version)
privacy_deletion_queue, privacy_deletion_review	Web app only: Moderation

Rules that changed

• One patch rule for every kind: an omitted field is kept, null clears it.
• Every item has one version. Changing content needs the version from item_get; a stale version is refused and names the current one. Moves (parent, position) need no version. Revision ids are no longer part of the contract.
• A task's text is content (formerly description), and its parent is parent (formerly parentTaskNumber).
• Lists return short entries and page with limit, cursor, total, hasMore and nextCursor. Tasks are the active ones unless includeClosed is set.
• Recall and lists name a memory as #N in the project being read, read with item_get(projectId, number: N), and as memory:<id> without a project, read with item_get(ref: "memory:<id>") (formerly project:<guid>#N and user:memory:<id>).
• propose=true asks for review (formerly review: "require"), and reason is shown to the reviewer (formerly explanation).
• A missing write permission is the outcome denied, not an error.
• Responses name people by their display name and never contain email addresses.

Batches

• Conderis Batch v2 imports tasks, pages and memories together: up to 100 items, each kind stored atomically on its own, and an item's parent may be the key of an earlier item of the same kind. Sending the same batch again stores nothing twice. Schema: https://conderis.com/schemas/conderis-batch-v2.schema.json, example: https://conderis.com/examples/conderis-batch-v2.json.
• A Conderis Memory Batch v1 file is still accepted unchanged, as batch of item_store with kind: "memory".

For agents and people who connect agents to Conderis. The server now offers eight tools instead of 27, and the tool list costs about 6,500 characters of context instead of about 19,000 (#309, #317). The old tool names no longer exist; an agent that calls one receives an unknown-tool error.

What to do

• Reload the MCP connection in every client, so the client fetches the new tool list.
• Replace old tool names in your own instructions (for example a global CLAUDE.md or AGENTS.md): memory_recall becomes recall, and memory_store becomes item_store with kind: "memory". The table below lists the rest.
• Read the system guide once with recall and guide=true. Version 31 was the first for v2; the current one is named at the top of every recall.

The eight tools

Tool	Purpose
recall	Session start: instructions, active tasks, pages and memories within a budget; guide=true returns the system guide.
project_get	Your projects, or one project with your permissions, assignable people and agents, and counts.
project_store	Create or change a project.
item_get	One task, memory, page, proposal or the instructions; history=true, version, offset/take.
item_list	Short entries of one kind, with query, filter, sort and cursor paging.
item_store	Create or change items, or store a batch.
item_action	Claim, complete, block and unblock tasks; archive and restore; relate; approve, reject and withdraw proposals.
item_delete	Request permanent deletion of private data posted by mistake.

Old tool, new call

Before	Now
system_memory	recall with guide=true
memory_recall	recall
project_list	project_get without projectId
project_create, project_update	project_store
task_assignee_list	project_get with projectId (assignees)
memory_get, item_get, proposal_get	item_get (a proposal with ref: "proposal:<id>")
task_list, item_search, proposal queue	item_list with kind, optionally query
item_history	item_get with history=true
memory_store, page_store, task_create, task_patch	item_store with kind and fields
task_claim, task_complete	item_action with claim or complete
item_archive	item_action with archive or restore
relation_create, relation_remove	item_action with relate or unrelate
relation_list	item_get (direct relations are part of the item)
proposal_review, proposal_withdraw	item_action with approve, reject or withdraw
item_delete	item_delete (a single version with version)
privacy_deletion_queue, privacy_deletion_review	Web app only: Moderation

Rules that changed

• One patch rule for every kind: an omitted field is kept, null clears it.
• Every item has one version. Changing content needs the version from item_get; a stale version is refused and names the current one. Moves (parent, position) need no version. Revision ids are no longer part of the contract.
• A task's text is content (formerly description), and its parent is parent (formerly parentTaskNumber).
• Lists return short entries and page with limit, cursor, total, hasMore and nextCursor. Tasks are the active ones unless includeClosed is set.
• Recall and lists name a memory as #N in the project being read, read with item_get(projectId, number: N), and as memory:<id> without a project, read with item_get(ref: "memory:<id>") (formerly project:<guid>#N and user:memory:<id>).
• propose=true asks for review (formerly review: "require"), and reason is shown to the reviewer (formerly explanation).
• A missing write permission is the outcome denied, not an error.
• Responses name people by their display name and never contain email addresses.
• A Conderis Memory Batch v1 file is still accepted unchanged, now as batch of item_store with kind: "memory". In a v2 batch an item's parent may be the key of an earlier item of the same kind.

For agents and people who connect agents to Conderis. The server now offers eight tools instead of 27, and the tool list costs about 6,500 characters of context instead of about 19,000 (#309, #317). The old tool names no longer exist; an agent that calls one receives an unknown-tool error.

What to do

• Reload the MCP connection in every client, so the client fetches the new tool list.
• Replace old tool names in your own instructions (for example a global CLAUDE.md or AGENTS.md): memory_recall becomes recall, and memory_store becomes item_store with kind: "memory". The table below lists the rest.
• Read the system guide once with recall and guide=true. Version 31 was the first for v2; the current one is named at the top of every recall.

The eight tools

Tool	Purpose
recall	Session start: instructions, active tasks, pages and memories within a budget; guide=true returns the system guide.
project_get	Your projects, or one project with your permissions, assignable people and agents, and counts.
project_store	Create or change a project.
item_get	One task, memory, page, proposal or the instructions; history=true, version, offset/take.
item_list	Short entries of one kind, with query, filter, sort and cursor paging.
item_store	Create or change items, or store a batch.
item_action	Claim, complete, block and unblock tasks; archive and restore; relate; approve, reject and withdraw proposals.
item_delete	Request permanent deletion of private data posted by mistake.

Old tool, new call

Before	Now
system_memory	recall with guide=true
memory_recall	recall
project_list	project_get without projectId
project_create, project_update	project_store
task_assignee_list	project_get with projectId (assignees)
memory_get, item_get, proposal_get	item_get (a proposal with ref: "proposal:<id>")
task_list, item_search, proposal queue	item_list with kind, optionally query
item_history	item_get with history=true
memory_store, page_store, task_create, task_patch	item_store with kind and fields
task_claim, task_complete	item_action with claim or complete
item_archive	item_action with archive or restore
relation_create, relation_remove	item_action with relate or unrelate
relation_list	item_get (direct relations are part of the item)
proposal_review, proposal_withdraw	item_action with approve, reject or withdraw
item_delete	item_delete (a single version with version)
privacy_deletion_queue, privacy_deletion_review	Web app only: Moderation

Rules that changed

• One patch rule for every kind: an omitted field is kept, null clears it.
• Every item has one version. Changing content needs the version from item_get; a stale version is refused and names the current one. Moves (parent, position) need no version. Revision ids are no longer part of the contract.
• A task's text is content (formerly description), and its parent is parent (formerly parentTaskNumber).
• Lists return short entries and page with limit, cursor, total, hasMore and nextCursor. Tasks are the active ones unless includeClosed is set.
• Recall and lists name a memory as #N in the project being read and as memory:<id> without a project; both work with item_get as they are (formerly project:<guid>#N and user:memory:<id>).
• propose=true asks for review (formerly review: "require"), and reason is shown to the reviewer (formerly explanation).
• A missing write permission is the outcome denied, not an error.
• Responses name people by their display name and never contain email addresses.
• A Conderis Memory Batch v1 file is still accepted unchanged, now as batch of item_store with kind: "memory". In a v2 batch an item's parent may be the key of an earlier item of the same kind.

For agents and people who connect agents to Conderis. The server now offers eight tools instead of 27, and the tool list costs about 6,500 characters of context instead of about 19,000 (#309, #317). The old tool names no longer exist; an agent that calls one receives an unknown-tool error.

What to do

• Reload the MCP connection in every client, so the client fetches the new tool list.
• Replace old tool names in your own instructions (for example a global CLAUDE.md or AGENTS.md): memory_recall becomes recall, and memory_store becomes item_store with kind: "memory". The table below lists the rest.
• Read the system guide once with recall and guide=true. It is version 31.

The eight tools

Tool	Purpose
recall	Session start: instructions, active tasks, pages and memories within a budget; guide=true returns the system guide.
project_get	Your projects, or one project with your permissions, assignable people and agents, and counts.
project_store	Create or change a project.
item_get	One task, memory, page, proposal or the instructions; history=true, version, offset/take.
item_list	Short entries of one kind, with query, filter, sort and cursor paging.
item_store	Create or change items, or store a batch.
item_action	Claim, complete, block and unblock tasks; archive and restore; relate; approve, reject and withdraw proposals.
item_delete	Request permanent deletion of private data posted by mistake.

Old tool, new call

Before	Now
system_memory	recall with guide=true
memory_recall	recall
project_list	project_get without projectId
project_create, project_update	project_store
task_assignee_list	project_get with projectId (assignees)
memory_get, item_get, proposal_get	item_get (a proposal with ref: "proposal:<id>")
task_list, item_search, proposal queue	item_list with kind, optionally query
item_history	item_get with history=true
memory_store, page_store, task_create, task_patch	item_store with kind and fields
task_claim, task_complete	item_action with claim or complete
item_archive	item_action with archive or restore
relation_create, relation_remove	item_action with relate or unrelate
relation_list	item_get (direct relations are part of the item)
proposal_review, proposal_withdraw	item_action with approve, reject or withdraw
item_delete	item_delete (a single version with version)
privacy_deletion_queue, privacy_deletion_review	Web app only: Moderation

Rules that changed

• One patch rule for every kind: an omitted field is kept, null clears it.
• Every item has one version. Changing content needs the version from item_get; a stale version is refused and names the current one. Moves (parent, position) need no version. Revision ids are no longer part of the contract.
• A task's text is content (formerly description), and its parent is parent (formerly parentTaskNumber).
• Lists return short entries and page with limit, cursor, total, hasMore and nextCursor. Tasks are the active ones unless includeClosed is set.
• propose=true asks for review (formerly review: "require"), and reason is shown to the reviewer (formerly explanation).
• A missing write permission is the outcome denied, not an error.
• Responses name people by their display name and never contain email addresses.
• A Conderis Memory Batch v1 file is still accepted unchanged, now as batch of item_store with kind: "memory".