Claude Code qwen2.5-coder:14b agent bug
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the reported claude.md instructions and reproducing the prompt in the stated Codex CLI 2.1.96 setup with Ollama, qwen2.5-coder:14b, and Windows Terminal under WSL or PowerShell. Compare the expected Glob tool execution with the JSON being printed; done means the agent handles the request without exposing tool-call JSON.
Written by the indexing model from the issue text.
Description
What version of Codex CLI is running?
2.1.96 (Claude Code)
What subscription do you have?
none im Using Local Ai with Ollama
Which model were you using?
qwen2.5-coder:14b
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What terminal emulator and version are you using (if applicable)?
Windows Terminal (WSL / PowerShell)
Codex doctor report
What issue are you seeing?
at every prompt i use its saying
{
"name": "Glob",
"arguments": {
"pattern": "**/*.{java,kotlin}"
}
}
i asked chatgpt and its saying that it cant start agents or something
What steps can reproduce the bug?
i dont know this is my claude.md:
Claude Code Operating Rules
You are the primary developer for this repository.
You own the project until it builds successfully.
Never stop after:
- Analysis
- Planning
- Reading files
- Creating checklists
- Explaining changes
- Fixing only one file
Instead:
Read → Edit → Compile → Fix → Repeat
If compileJava fails:
- Read every compiler error.
- Fix every error.
- Compile again.
- Repeat until successful.
If build fails:
- Fix the cause.
- Build again.
If runServer fails:
- Read the stacktrace.
- Fix the cause.
- Start the server again.
Do not ask for confirmation between tasks.
Do not stop because one phase finished.
Immediately continue with the next phase.
Only stop when ALL are true:
- No Kotlin remains.
- Every file is valid Java 21.
- compileJava succeeds.
- build succeeds.
- runServer starts successfully.
- PLAN.md is fully completed.
Never output internal tool calls.
Never output JSON describing tools.
Use the available tools automatically.
Always modify the repository instead of describing modifications.
What is the expected behavior?
- Find every Java and Kotlin file:
Glob(pattern: "**/*.{java,kotlin}") - Inspect every source file to identify remaining Kotlin syntax:
● {
"name": "Glob",
"arguments": {
"pattern": "**/*.{java,kotlin}"
}
}
Additional information
No response
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·