Skip to content

ghost_commit tool creates large session that kills codex #7395

@devtonic0

Description

@devtonic0

What version of Codex is running?

0.61.1-alpha.1

What subscription do you have?

Business

Which model were you using?

Gpt-5.1-Codex

What platform is your computer?

No response

What issue are you seeing?

As seen in multiple issues, many users are having issues with indefinite reconnecting that never ends on both cli and vs code extension.

After many tests, and attempted fixes i have found that this issue in my case was due to an abnormally large jsonl session file. Which wasnt just 100% larger, or 200%, but a whopping 33,000% larger than the 2nd largest file. (3.9gb in size) now after inspecting this file i of course saw its all single line, and had to format it with jq to read it. And the issue was immediately obvious. This file contained every node module path, every pip path, and the path of every single file inside every node module and python package in this workspace. Not once, or twice, but several times.

Why is this? "Ghost_commit", 2476 snapshots listing every single untracked file in the repo.

These snapshots should exclude build files, .venv, dist, node modules, and several others. They should adhere to git ignore, and if there isnt one there is no reason they shouldnt be automatically ignoring these directories.

What steps can reproduce the bug?

Use codex on a large repository, with node_modules, venv, dist, or build. View jsonl file for that session.

What is the expected behavior?

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtool-callsIssues related to tool calling

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions