Files
codex/codex-rs/app-server-protocol/schema/json/v2/ThreadAttachmentOwnerListResponse.json
T
joeytrasatti-openai 2635431edb Add attachment owner lookup to the app-server (#50094)
## Why

`thread/attachment/list` lists attachments for a known thread. Clients also need to find the threads associated with a given attachment identity.

## What changed

Add `thread/attachmentOwner/list` to return owning thread IDs and archive status for an exact `attachmentType` and `identityKey`. Support cursor pagination and an optional `archived` filter, including both archived and non-archived threads by default.

Wire the request through the thread store and update documentation, protocol schemas, and generated TypeScript and Python types. The lookup is limited to the configured thread store and reports current membership, not an atomic resource-cleanup check.

## Testing

Extend app-server integration tests to cover exact type-and-key matching, multiple owners, archive filtering, and invalid cursor rejection.

GitOrigin-RevId: 30f4a20e00243d0023246d465a9b95213b3adeb6
2026-10-01 20:47:05 +00:00

42 lines
999 B
JSON
Generated

{
"$schema": "http://json-schema.org/draft-07/schema#",
"definitions": {
"ThreadAttachmentOwner": {
"description": "A thread that currently owns an attachment with the requested identity.",
"properties": {
"archived": {
"description": "Whether the owning thread is archived, not whether it is currently executing a turn.",
"type": "boolean"
},
"threadId": {
"type": "string"
}
},
"required": [
"archived",
"threadId"
],
"type": "object"
}
},
"description": "One page of matching owners, including threads without their own user messages.",
"properties": {
"data": {
"items": {
"$ref": "#/definitions/ThreadAttachmentOwner"
},
"type": "array"
},
"nextCursor": {
"type": [
"string",
"null"
]
}
},
"required": [
"data"
],
"title": "ThreadAttachmentOwnerListResponse",
"type": "object"
}