macos - история диалога не подтягивается

[grabius]

у меня макос

---

Детали разъезжаются (справа криво отображаются)

Сам диалог не грузится - 2 минуты ждал, висит без ответа "Loading messages...". Ожидал что можно будет читнуть диалог - не дает.

Лог:

  codedash — Claude & Codex Sessions Dashboard
  http://localhost:3847
  Press Ctrl+C to stop

  19:38:55 [API] GET /api/sessions
  19:40:01 [DATA] loaded 464 sessions {"codex":464}
  19:40:03 [ACTIVE] pid=88894 codex/active cpu=1.5% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=90438 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=90435 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=90200 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=90199 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=88893 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=87437 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=87436 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:40:03 [ACTIVE] pid=69099 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  19:41:21 [API] GET /api/terminals

---

При запуске все еще пусто, хотя предыдущее исью закрыли (где должно было отображать типа "в процессе"

---

[vakovalskii]

Thanks for the detailed report and logs! I see several issues:

1. Slow loading (66 seconds for 464 sessions)
Your /api/sessions took from 19:38:55 to 19:40:01 — that's because each Codex session file is read from disk to count messages. We have a 10s cache, but the first load with 464 sessions is heavy. We'll optimize this.

2. "Loading messages..." hangs
This is likely a large session file. Could you share:

• How large is the session file? Run: ls -lh ~/.codex/sessions/*/*/* | sort -k5 -h | tail -5
• Does codedash show any error in the server log when you click that session?

3. Active sessions all show source=fallback-latest
The ! character in your path (/Users/kyxa/!data/...) may be causing issues with shell escaping. We'll check this.

4. UI layout issues (details panel)
We just widened the panel to 840px in v6.8.2 — please run codedash update && codedash restart and check if it's better.

Quick fix to try now:

npm i -g codedash-app@latest && codedash restart

Also: could you run this and paste the output?

ls ~/.codex/sessions/ | head -5
ls -lh ~/.codex/sessions/*/*/* | sort -k5 -h | tail -5
wc -l ~/.codex/history.jsonl

[grabius]

(base) kyxa@kyxamac ~ % ls -lh ~/.codex/sessions/*/*/* | sort -k5 -h | tail -5
-rw-r--r--@ 1 kyxa  staff   365M Mar 16 19:33 rollout-2026-03-16T19-31-21-019cf7ea-bb42-7843-83f9-da7846a91e25.jsonl
-rw-r--r--@ 1 kyxa  staff   365M Mar 16 19:33 rollout-2026-03-16T19-31-27-019cf7ea-d2aa-74f1-8134-d0be73369783.jsonl
-rw-r--r--@ 1 kyxa  staff   397M Mar 17 10:24 rollout-2026-03-17T10-21-59-019cfb1a-1f68-7a82-bb6f-11ac25c26e75.jsonl
-rw-r--r--@ 1 kyxa  staff   398M Mar 17 10:46 rollout-2026-03-15T02-09-34-019cef0a-9547-71f0-bea4-5b3ef0e1d80b.jsonl
-rw-r--r--@ 1 kyxa  staff   413M Apr  1 19:55 rollout-2026-03-30T17-36-56-019d3f64-1335-77a3-94b2-9d8e802c1785.jsonl
(base) kyxa@kyxamac ~ %

(base) kyxa@kyxamac !auto_scripts % ls ~/.codex/sessions/ | head -5
ls -lh ~/.codex/sessions/*/*/* | sort -k5 -h | tail -5
wc -l ~/.codex/history.jsonl
2025
2026
-rw-r--r--@ 1 kyxa  staff   365M Mar 16 19:33 rollout-2026-03-16T19-31-21-019cf7ea-bb42-7843-83f9-da7846a91e25.jsonl
-rw-r--r--@ 1 kyxa  staff   365M Mar 16 19:33 rollout-2026-03-16T19-31-27-019cf7ea-d2aa-74f1-8134-d0be73369783.jsonl
-rw-r--r--@ 1 kyxa  staff   397M Mar 17 10:24 rollout-2026-03-17T10-21-59-019cfb1a-1f68-7a82-bb6f-11ac25c26e75.jsonl
-rw-r--r--@ 1 kyxa  staff   398M Mar 17 10:46 rollout-2026-03-15T02-09-34-019cef0a-9547-71f0-bea4-5b3ef0e1d80b.jsonl
-rw-r--r--@ 1 kyxa  staff   413M Apr  1 19:55 rollout-2026-03-30T17-36-56-019d3f64-1335-77a3-94b2-9d8e802c1785.jsonl
    3189 /Users/kyxa/.codex/history.jsonl
(base) kyxa@kyxamac !auto_scripts %

• Does codedash show any error in the server log when you click that session?
  No errors, nothing - I've shown you the full log during the first 2-3 minutes of codedash's work in the previous message.

And after the update, no info about "loading sessions" - for about one minute (I see in the console that they are loading, but nothing in UI)

And still no changes after the click on the session

After about 1 minute I see "Failed to load messages." but nothing in the console

(base) kyxa@kyxamac ~ % npm i -g codedash-app@latest && codedash restart

changed 1 package in 351ms

  Stopping codedash on port 3847...
  Stopped.
  Starting...


  codedash — Claude & Codex Sessions Dashboard
  http://localhost:3847
  Press Ctrl+C to stop

  22:51:22 [API] GET /api/sessions
  22:52:26 [DATA] loaded 466 sessions {"codex":466}
  22:52:28 [ACTIVE] pid=88894 codex/active cpu=0.5% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=90438 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=90435 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=90200 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=90199 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=88893 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=87437 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=87436 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:52:28 [ACTIVE] pid=69099 codex/waiting cpu=0% cwd=/Users/kyxa/!data/!agents_temp_data/browser_review/zones_controls_ghost session=019d6789... source=fallback-latest
  22:53:34 [API] GET /api/terminals

[vakovalskii]

Thanks for the file sizes! The problem is clear:

Your top session files are 365-413 MB each. When codedash tries to load session detail, it reads the entire file into memory with readFileSync() — that's 400MB into a Node.js string, which causes the hang.

For now, a workaround: codedash won't crash, but loading a 400MB session will be very slow. We need to implement streaming reads for large files — tracking this.

The 64-second initial load is because we count messages in each Codex session file. With 466 files and some being 400MB+, this is expected. We'll optimize to use file size as a fast estimate instead of counting lines.

Update to latest version (codedash update) — the Windows CMD fix (#64) is also included now.

[grabius]

• The 64-second initial load is because we count messages in each Codex session file
  Just write "Counting messages..." on start, and that will be enough - at least the person will understand that this is not the case when the program just does not work, it is in progress.

[vakovalskii]

Thanks for the detailed logs! A few things I can see:

1. Dialog not loading ("Loading messages...")
Can you share which session ID you're trying to open? From the log I see only Codex sessions (464). The session detail might be hanging on a very large JSONL file.

Quick debug: run this in terminal and share the output:

codedash show <session-id-you-clicked>

Or if you remember the first few chars of the session ID from the card, try:

ls -lh ~/.codex/sessions/ | head -20

This will show if any session files are abnormally large.

2. False positive active sessions (9 codex processes)
Fixed in v6.15.14 — MCP servers and child processes are now filtered. Please update:

npm i -g codedash-app@latest

3. Layout issues (details panel)
Also likely fixed in recent versions. Please update and let me know if it persists.

What version are you on? (codedash version)