Overview

contox_list_contexts returns a list of all contexts in the current project. Each context includes its metadata but not its full content — use contox_get_context to retrieve the content of a specific context.

This is useful for understanding the project's memory structure, finding context IDs for other operations, and checking the state and tier of individual contexts.

Parameters

This tool takes no parameters.

Return value

Returns a JSON array of context objects, each containing:

Field	Type	Description
`id`	string	Unique context ID
`name`	string	Display name
`description`	string	Brief description
`parentContextId`	string or null	Parent context ID for hierarchy
`schemaKey`	string or null	Brain schema key (e.g., `root/architecture`)
`tier`	number or null	Tier level: 1 (always loaded), 2 (on-demand), 3 (archive)
`state`	string or null	State: `draft`, `approved`, or `deprecated`
`tokens`	number or null	Approximate token count
`updatedAt`	string	ISO timestamp of last update

Usage examples

Listing all project contexts

User: Show me all my memory contexts

Claude calls: contox_list_contexts()

Response:
[
  {
    "id": "ctx_abc123",
    "name": "Project Memory",
    "description": "Root context for AI project memory",
    "parentContextId": null,
    "schemaKey": "root",
    "tier": 1,
    "state": "approved",
    "tokens": 450,
    "updatedAt": "2025-04-15T10:30:00Z"
  },
  {
    "id": "ctx_def456",
    "name": "[Memory] Architecture",
    "description": "Tech stack and architecture decisions",
    "parentContextId": "ctx_abc123",
    "schemaKey": "root/architecture",
    "tier": 1,
    "state": "approved",
    "tokens": 1200,
    "updatedAt": "2025-04-15T10:30:00Z"
  }
]

Finding a context ID to update

User: Update my architecture context with the new database schema

Claude calls: contox_list_contexts()
// Finds the architecture context ID from the response
Claude calls: contox_update_context({ id: "ctx_def456", content: "..." })

Notes

The response includes all contexts regardless of state (draft, approved, deprecated).
Sub-contexts are identified by having a non-null parentContextId.
Memory sub-contexts created by contox_save_session are prefixed with [Memory] in their name.
Scan sub-contexts created by contox_scan are prefixed with [Scan] in their name.

contox_save_session

contox_get_context