clone/codex
1
0
Fork 0
mirror of https://github.com/openai/codex.git synced 2026-05-01 01:47:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Restack context fragment standardization

Browse Source 
Reapply the standardized model-visible context fragment work on top of the latest origin/main as a clean squashed restack.

Co-authored-by: Codex <noreply@openai.com>
This commit is contained in:
Charles Cunningham
2026-03-12 10:52:17 -07:00
parent 9f2da5a9ce
commit 3954e00f53
56 changed files with 6123 additions and 1483 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
codex-rs/app-server-protocol/schema/json/ClientRequest.json
View File

@@ -2370,6 +2370,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"
@@ -2618,7 +2619,7 @@
"type": "object"
},
"ThreadResumeParams": {
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.",
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.\n\nWhen resuming a thread that is already loaded/running, override fields are ignored and reported as mismatch warnings rather than being reapplied mid-session.",
"properties": {
"approvalPolicy": {
"anyOf": [
@@ -2650,6 +2651,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"
@@ -2801,6 +2803,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"

5
codex-rs/app-server-protocol/schema/json/codex_app_server_protocol.schemas.json
View File

@@ -11211,6 +11211,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"
@@ -12297,7 +12298,7 @@
},
"ThreadResumeParams": {
"$schema": "http://json-schema.org/draft-07/schema#",
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.",
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.\n\nWhen resuming a thread that is already loaded/running, override fields are ignored and reported as mismatch warnings rather than being reapplied mid-session.",
"properties": {
"approvalPolicy": {
"anyOf": [
@@ -12329,6 +12330,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"
@@ -12562,6 +12564,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"

5
codex-rs/app-server-protocol/schema/json/codex_app_server_protocol.v2.schemas.json
View File

@@ -8938,6 +8938,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"
@@ -10024,7 +10025,7 @@
},
"ThreadResumeParams": {
"$schema": "http://json-schema.org/draft-07/schema#",
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.",
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.\n\nWhen resuming a thread that is already loaded/running, override fields are ignored and reported as mismatch warnings rather than being reapplied mid-session.",
"properties": {
"approvalPolicy": {
"anyOf": [
@@ -10056,6 +10057,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"
@@ -10289,6 +10291,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"

1
codex-rs/app-server-protocol/schema/json/v2/ThreadForkParams.json
View File

@@ -99,6 +99,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"

3
codex-rs/app-server-protocol/schema/json/v2/ThreadResumeParams.json
View File

@@ -990,7 +990,7 @@
"type": "string"
}
},
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.",
"description": "There are three ways to resume a thread: 1. By thread_id: load the thread from disk by thread_id and resume it. 2. By history: instantiate the thread from memory and resume it. 3. By path: load the thread from disk by path and resume it.\n\nThe precedence is: history > path > thread_id. If using history or path, the thread_id param will be ignored.\n\nPrefer using thread_id whenever possible.\n\nWhen resuming a thread that is already loaded/running, override fields are ignored and reported as mismatch warnings rather than being reapplied mid-session.",
"properties": {
"approvalPolicy": {
"anyOf": [
@@ -1022,6 +1022,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"

1
codex-rs/app-server-protocol/schema/json/v2/ThreadStartParams.json
View File

@@ -123,6 +123,7 @@
]
},
"developerInstructions": {
"description": "Custom developer override for this thread session. Takes precedence over `~/.codex/config.toml` `developer_instructions`.",
"type": [
"string",
"null"