Windows app: persist workspace layout and restore last open thread/window

Open
#37,429 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop, operating-systems

Research direction

No files or tests are named in the issue. Start by locating the Windows app startup/shutdown path and existing settings or state persistence entry points, then trace how the active thread and pane layout are represented. Done means normal restarts restore the prior context and layout, with the requested login and minimized-to-tray options addressed or clearly scoped.

Written by the indexing model from the issue text.

Description

app enhancement session windows-os
Environment
  • Codex Windows app (Microsoft Store)
  • Package: OpenAI.Codex
  • Version: 26.803.5235.0
Problem

On every restart, the desktop app does not reliably restore the last open thread/window or the user-adjusted pane/column widths and positions. There is also no visible option to launch at sign-in minimized to the background/tray.

Steps to reproduce
  1. Open Codex on Windows.
  2. Resize/rearrange the sidebar and workspace columns; open a working thread.
  3. Close and relaunch the application.
Actual behavior

The app starts without restoring the prior working context and layout; panel widths/positions need to be set again.

Expected behavior

Persist the last active thread/window plus sidebar and panel layout across normal restarts. Ideally provide optional "Launch at login" and "Start minimized to tray" settings.

Impact

This makes daily, short iterative work significantly slower because the work context and UI layout must be rebuilt repeatedly.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.