Non-dangerous actions trigger the safety check.

Open
#33,983 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go, rust
Domain
security, testing

Research direction

Start by reproducing the behavior while using ton-blockchain/ton and xssnick/tonutils-go for emulation, transaction building, and consistency checks, including negative scenarios. Capture the exact operation that triggers Codex's safety check, since the report currently has no specific reproduction steps. Done means the identified non-dangerous test scenario no longer triggers the check unexpectedly.

Written by the indexing model from the issue text.

Description

app bug safety-check windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

26.715.31251

What subscription do you have?

20x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When using https://github.com/ton-blockchain/ton and https://github.com/xssnick/tonutils-go for emulation, transaction building, and verifying consistency between different virtual machine implementations, the safety check is often triggered.

This may be related to the fact that testing requires covering negative scenarios as well, such as cases where the balance becomes unexpectedly low or similar situations.

What steps can reproduce the bug?

I can’t provide a specific example because Codex doesn’t show what exactly triggers the safety check. It may work normally for hours, but sometimes it simply refuses to work every five minutes.

What is the expected behavior?

I expect the safety check not to be triggered by tests or local reproductions of different execution scenarios, including negative test cases.

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.