What was the actual cause of the README.md failure?

The local command policy rejected all four commands the agent tried, including Get-Content -LiteralPath README.md -TotalCount 60, so the file body never reached the model.

Did the deepseek-v4.1-flash model connection work in this test?

Yes, the ds41-flash profile loaded and the model name was deepseek-v4.1-flash; the thread and turn started, but local command execution was blocked afterward.

What should be checked next after a command rejection?

The recommended next check is the sandbox, approval, and command policy settings, then rerun the same README.md task without changing the model, profile, or task at the same time.

Large Language ModelsAI Coding AssistantsZenn AI/ML16h agoNov 14, 2026, 04:00 JST

Codex CLI README.md failure traced to local command policy, not deepseek-v4.1-flash

Send on LINE

3 Key Points

What happened
In a November 13, 2026 test on Windows PowerShell, a Codex CLI 0.168.0 session loaded the ds41-flash profile for deepseek-v4.1-flash and started the thread, but all four local commands, including Get-Content -LiteralPath README.md -TotalCount 60 and cmd /c dir, were rejected by local command policy.
Why it matters
The failure sits after model connection, so changing the model name would not address it; the blocked commands meant the file content never reached the model.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Get these free every morning

Context & Analysis

The test record separates four layers: model list, API response, profile, and local commands. Before the README.md task, a minimal API request returned HTTP 200 with a visible OK for deepseek-v4.1-flash on both Responses and Chat Completions, and the model ID appeared in a 170-model catalog. The session also logged input 91,635 tokens and output 850 tokens, showing the profile and model were engaged. The failure occurred only at the local command stage, where command policy rejected each attempt. The author recommends isolating layers, starting with short API tests before profile trials, and rerunning the same task after fixing local policy rather than changing multiple variables at once.

FAQ

What was the actual cause of the README.md failure?: The local command policy rejected all four commands the agent tried, including Get-Content -LiteralPath README.md -TotalCount 60, so the file body never reached the model.
Did the deepseek-v4.1-flash model connection work in this test?: Yes, the ds41-flash profile loaded and the model name was deepseek-v4.1-flash; the thread and turn started, but local command execution was blocked afterward.
What should be checked next after a command rejection?: The recommended next check is the sandbox, approval, and command policy settings, then rerun the same README.md task without changing the model, profile, or task at the same time.

Zenn AI/MLRead Original Article

Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Get it free

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.