Repository navigation
MCP servers on Codex threads can't tell which T3 thread called them #37770
boldaxolotl
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
An MCP server can't tell which T3 thread called it when the thread runs on Codex.
On Claude threads,
T3CODE_THREAD_IDis in the agent process environment, so MCP servers inherit it and can read the thread's title witht3 thread show <id> --json. On Codex threads, eachtools/callcarries only Codex's own thread id in_meta(threadId). #28604 gave CodexT3CODE_THREAD_IDthroughshell_environment_policy, which reaches shell commands but not MCP servers. The only Codex-to-T3 mapping is T3 Code's internal SQLite state.Proposal
Either:
t3-codeserver.t3 thread show --provider-thread <codex-thread-id> --json.Why
A tool's web dashboard labels each job with the title of the T3 thread that started it. Codex jobs show up unlabeled.
Related: #32870 (document
T3CODE_THREAD_IDas stable), #37501 (provider session id int3 thread show --json/t3 thread list --json, which would allow a lookup by listing).All reactions