Expose safe project and thread ordering APIs for Codex Desktop
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
App / Codex Desktop
What feature would you like to see?
Codex Desktop supports drag-and-drop organization, but automating it through the UI is unsafe because dropping a thread onto a project changes its project membership instead of merely changing its visual order.
Please expose supported App Server APIs for:
- reading the persisted project and thread display order;
- assigning an explicit order or moving an item before/after another item;
- sorting projects and threads by recent activity;
- distinguishing reorder operations from moving a thread between projects;
- applying an atomic batch reorder;
- returning the resulting order for verification;
- preserving thread-to-project membership during reorder;
- restoring a previous order after failure.
Use case
Users with many long-running projects need external local organizers that can rank projects and threads by activity without editing internal files or using fragile mouse automation.
A supported ordering API would also make accessibility tooling and local workflow automation substantially safer. The key requirement is that a visual reorder must never be confused with changing a thread's project membership.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; begin by mapping the App Server endpoints and data structures for projects, threads, membership, and persisted display order. Review how current drag-and-drop behavior distinguishes reordering from project moves, then identify tests for atomic batches, returned order, membership preservation, and rollback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100