Overview
contox_update_context modifies an existing context. You can update the name, description, content, or any combination of these fields. Only the fields you provide will be changed.
Important: When updating content, the new content completely replaces the existing content. It is not appended. If you want to add to existing content, first read the current content with contox_get_context, then provide the combined content.
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
id | string | Yes | — | The context ID to update |
name | string | No | — | New name for the context |
description | string | No | — | New description |
content | string | No | — | New content (replaces existing content entirely) |
Return value
Returns a confirmation message with the updated context's name and ID:
Context updated: My Context (ctx_abc123)
Usage examples
Updating content
Claude calls: contox_update_context({
id: "ctx_abc123",
content: "## Architecture\n\nNext.js 14 with App Router and TypeScript strict mode.\n\n## Database\n\nPostgreSQL with Drizzle ORM."
})
Renaming a context
Claude calls: contox_update_context({
id: "ctx_abc123",
name: "Architecture & Infrastructure",
description: "Tech stack, infrastructure, and deployment setup"
})
Notes
- At least one optional field (name, description, or content) should be provided. Calling with only
idhas no effect. - Content replacement is atomic — there is no partial update of content.
- If the context ID does not exist, the tool returns an error.