---
title: "Set Chat Mind Context Disabled"
method: POST
path: "/api/chats/{chat_id}/mind-context"
tags: ["chats"]
---

# Set Chat Mind Context Disabled

`POST /api/chats/{chat_id}/mind-context`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/chats/{chat_id}/mind-context`
- Auth: none declared

Suppress (or re-admit) Mind-derived context from this chat's prompts.

TOS-1988 Phase 1: the with-vs-without-Mind benchmark's arm-B switch, and
the write-path sibling of ``POST /{chat_id}/extraction`` above. Unlike
that endpoint, this is read-side only - it never orphans or re-admits any
durable Mind projection, so there is no reconciliation worker to fire on a
real transition.

## Path parameters

- `chat_id` string, uuid, required

## Headers

- `x-impersonate-identity-id` string, nullable

## Request body

- MindContextDisabledRequest
  - `disabled` boolean, required

## Response `200`

Successful Response

- OkResponse
  - `ok` boolean

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/thinqos/apis/thinqos-api.md) · [All operations](https://skmtc.dev/thinqos/apis/thinqos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/thinqos/apis/thinqos-api/revisions/ce2c2ce318b1?raw)