Skip to main content
GET
/
v1
/
projects
/
{projectId}
/
memory
/
conflicts
Memory conflicts
curl --request GET \
  --url https://api.example.com/v1/projects/{projectId}/memory/conflicts \
  --header 'Content-Type: application/json' \
  --data '
{
  "resolution": "<string>",
  "mergedContent": "<string>"
}
'
When a new memory contradicts an existing one, Kommit flags both as conflicting. Use these endpoints to list and resolve conflicts.

​
List conflicts

​
projectId
string
required
Project UUID.
curl https://api.getkommit.ai/v1/projects/a1b2c3d4-e5f6-7890-abcd-ef1234567890/memory/conflicts \
  -H "Authorization: Bearer km_your_api_key"

​
Resolve a conflict

POST /v1/projects/{projectId}/memory/conflicts/{conflictId}/resolve
​
conflictId
string
required
Conflict UUID.
​
resolution
string
required
One of:
  • keep_existing — keep the original memory, archive the new one
  • keep_new — keep the new memory, supersede the original
  • merge — combine both into a single memory (requires mergedContent)
  • archive_both — archive both and write a fresh memory separately
​
mergedContent
string
Required when resolution is merge. The combined memory content.
curl -X POST https://api.getkommit.ai/v1/projects/a1b2c3d4-e5f6-7890-abcd-ef1234567890/memory/conflicts/c1a2b3c4-d5e6-7890-abcd-ef1234567890/resolve \
  -H "Authorization: Bearer km_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "resolution": "merge",
    "mergedContent": "Use PostgreSQL with Drizzle ORM. Originally chose over Prisma for edge runtime support. Now also preferred for its SQL-like query builder API."
  }'