feat: Codex sender prefix on Codex→Grok messages; sort/filter/search codex threads - #130
Merged
Merged
Conversation
…, filter and search codex threads
🦋 Changeset detectedLatest commit: 67075b9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
What
[from Codex thread <id> @ <machine>, cwd <cwd>; reply: codex_send({threadId:"<id>", message:"..."}) via MCP on <machine> (or CLI: gbot codex send <id> "...")].Applied on the managed relay (
grok-request), its returned answers (grok-return), plaingbot_sendwith a known Codex thread, andgbot sendinside a Codex terminal ($CODEX_THREAD_ID). Machine is the real hostname; unknown fields drop out, the thread id never does when known.codex_threads/gbot codex list-threads: newest activity first by default (sortupdated|created|recency,order),query(name/title, preview, id prefix; scans every page),activeWithin/since,cwd,modelProvider,sourceKind,archived. Client-side filters page through the daemon with a resumablegbot1:cursor, no first-page cap.Tests
New/updated unit + route tests;
npm run checkonly has the 3 known pre-existingcodexStatusfailures (28, 84, 87).Minor changeset added; artifact rebuilt last.