Repository navigation
feat(lastcode): add Codex thread inspection - #54
Merged
lastobelus merged 12 commits intoAug 22, 2026
Merged
Conversation
Owner
Author
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3436cc036
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
lastobelus
force-pushed
the
lastcode/codex-thread-read
branch
from
August 22, 2026 04:12
b3436cc to
3e4612f
Compare
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3e4612fc1c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 901b0783c2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6732d11255
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b9a533b76c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a0e46ed769
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d9bd9d0d33
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 457cfcaa66
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 86e501b743
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6648627a8d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
lastobelus
added a commit
that referenced
this pull request
Aug 29, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Aug 29, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Aug 29, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Aug 30, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Aug 31, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 1, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 2, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 2, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 2, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 2, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 2, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 2, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 3, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 3, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 3, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 3, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 3, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 5, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 5, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 5, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 5, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 5, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
lastobelus
added a commit
that referenced
this pull request
Sep 5, 2026
Codex can already discover and inspect LastCode/T3 Code sessions by probing environment variables and SQLite, but that path is unofficial, inconsistent, and awkward across hosts. A single user running a handful of concurrent threads needs a small supported command surface for identifying, listing, reading, messaging, and waiting on those threads. This umbrella contains all three reviewed slices: 1. [#54](#54) adds Codex-only `current`, `list`, and `read` commands plus the generated `lastcode-thread` launcher. Reads prefer the authenticated live server and use a bounded, read-only SQLite fallback. 2. [#59](#59) adds live-only, fire-and-forget `send`. 3. [#61](#61) adds exact `send --wait` correlation and standalone `wait`, with bounded answers and recovery handles. Codex receives authoritative LastCode and provider thread identity. Cross-host use deliberately composes the same command over SSH. Durable usage documentation is in `docs/user/codex-thread-tools.md`. This remains a personal, low-concurrency tool. It does not add an MCP server, broker, host registry, UI, generic retry framework, or general-purpose orchestrator. If the provider accepts a turn but the process dies, correlation finalization fails, the assistant-finalization marker cannot be persisted before the durable link is recorded, or a checkpoint revert removes the tracked turn, that wait handle can time out; automatic retry and reconciliation are intentionally deferred. - Each slice passed focused tests, package typechecks, lint, formatting, bounded Luna-high review rounds, and exact-head Codex review before being merged into this umbrella. - The rebased patch is identical across all 16 feature commits and contains only 42 thread-tools files. - The exact current head `6c618fa9d` passed 224 focused tests and the guarded quick local CI gate on base `0b0bca08e`, including all workspace tests and typechecks and 2,749 passing server tests. - Exact-head Codex review reported no major issues, and every review thread is resolved. **Do not merge this umbrella PR into `lastcode/main` until the user explicitly rubberstamps it.** Implemented by GPT-5.6 Sol, reviewed with GPT-5.6 Luna, in the T3 Code Codex harness.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Codex can infer LastCode session identity by probing environment variables and SQLite, but there is no supported, bounded way to identify, list, or inspect threads—especially when composing the same operation over SSH.
Solution
t3 thread current|list|readwith stable, bounded JSON output;lastcode-threadwrapper and expose it only to Codex processes on supported POSIX hosts;This PR is slice 1 of umbrella PR #52. It intentionally contains no thread messaging or waiting behavior.
Validation
Implemented with GPT-5.6 Sol and reviewed with GPT-5.6 Luna in the Codex harness.