Restart app-server per workspace without full app restart (for account switching)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- tauri, typescript
Research direction
Trace how each workspace starts and owns its persistent codex app-server process, then inspect the workspace sidebar actions for an appropriate entry point. The implementation should provide a per-workspace reconnect or restart action that uses the current ~/.codex account without restarting the whole app; verify that subsequent requests use the refreshed process.
Written by the indexing model from the issue text.
Description
Problem
When using multiple Codex accounts via a tool like Codex Switcher, switching accounts updates ~/.codex but does not affect already-running workspace sessions in CodexMonitor. Each workspace has a persistent codex app-server process started at launch with the original account. After switching accounts externally, all requests continue to use the old session and fail with usageLimitExceeded.
The only workaround currently is a full app restart (Cmd+Q and reopen).
Expected Behavior
A way to restart the app-server for a specific workspace from within CodexMonitor — either via:
- A right-click context menu on the workspace
- A button in workspace settings
- Automatic detection of account changes in
~/.codex
Debug Log Evidence
Both workspaces return the same rate limit error after account switch:
"codexErrorInfo": "usageLimitExceeded"
"willRetry": false
Even after switching accounts externally, new turn/start requests go to the same exhausted session.
Suggested Fix
Add a Reconnect or Restart app-server option per workspace in the sidebar context menu. This would kill the current app-server process and spawn a fresh one, picking up whatever account is active in ~/.codex at that moment.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 416
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from Dimillian/CodexMonitor
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Dimillian/CodexMonitor#590 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 63/100
Dimillian/CodexMonitor#615 ·
-
Codex Monitor does not surface MCP browser tool approval prompts, making browser tools appear hung Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Dimillian/CodexMonitor#612 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Dimillian/CodexMonitor#599 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Dimillian/CodexMonitor#598 ·
All issues in Dimillian/CodexMonitor
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100