Original post by the person on Bluesky · Source language: English
An unresolved report that the AI stops even with detailed instructions
Nick Tune posted that he instructed Codex down to the line of code and asked it to continue, yet it stops at every response. The original post we checked this time does not describe any result after improvement.
- Who:
- Nick Tune, implementing with Codex
- Scope:
- One post by Nick Tune. Cause and workaround unconfirmed
- Source published:
- 2026-09-10
- Period observed:
- Time of experience not stated / social post September 10, 2026
- Editorial check:
- 2026-10-23
Only the source ID is saved in this browser. Nothing syncs across devices.
What was confirmed
- The person reports it stops at every response even after instructing down to the line of code.
- The original post describes no remedy or post-improvement result.
Who, and in what situation
An experience of giving the AI detailed implementation instructions and asking it to keep working.
What they needed
Getting the intended work done without the developer having to intervene at every response.
What they tried
This is a record of trying detailed instructions and a request to continue. The original post checked this time alone does not show an effective workaround.
What this source lets you read
A post that shows only what is troubling and from which the course of resolution cannot be followed is still worth leaving as unconfirmed.
What to check next
Which conditions would you change to keep going while preserving the checks you need?
Limits of this source
- A short single post; version, settings, prompt, logs and frequency of reproduction are unknown.
- The exact time the experience happened is not stated.
- That the original post has no solution does not mean no solution exists in the world.
Read the primary source
Links use the original title or a HAKOMIRO source description. Japanese originals retain their published wording.
Post reporting that Codex stops after each response (opens in new tab) ↗
Nick Tune/Bluesky /
We checked the public HTML body and post time. There is no material verifying cause or resolution.