Windows: SessionStart hook is not triggered after Codex completes compact

Open
#35,540 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

Reproduce the issue on Windows with a configured SessionStart hook, then trace the SessionStart dispatch around compact completion and inspect the hook logs. Confirm the fix by verifying that the hook runs after compaction as well as at initial session start, and add or run the relevant regression coverage if the existing test structure exposes this path.

Written by the indexing model from the issue text.

Description

bug CLI context hooks windows-os
What version of Codex CLI is running?

codex-cli 0.145.0

What subscription do you have?

no

Which model were you using?

No response

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What terminal emulator and version are you using (if applicable)?

No response

Codex doctor report

What issue are you seeing?

On Windows, Codex does not trigger the configured SessionStart hook after the compact operation completes.

This prevents initialization logic that depends on the hook from running again, such as refreshing environment variables, regenerating context files, or executing project setup scripts.

What steps can reproduce the bug?

Steps to Reproduce

  1. Configure a SessionStart hook on Windows.
  2. Start a Codex session.
  3. Confirm that the hook runs when the session initially starts.
  4. Run compact during the session.
  5. Wait for compaction to complete.
  6. Check the hook logs or output.
What is the expected behavior?

No response

Additional information

No response

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.