Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

agmsgd (v1.6.0, Windows): daemon enable records npm's extensionless codex shim, so every Codex seat stays windows_codex_executable_unresolved

Open Beginner friendly
#1,760 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, javascript, node.js
Domain
cli, devtools

Research direction

Start in scripts/daemon.sh around L492 in _resolve_codex, and scripts/daemon/channels/windows-codex-queue.mjs L11 resolveWindowsCodexExe. On Windows, make the recorded path resolve to codex.exe or the npm vendor exe, mirroring the gate's lookup. Done when agmsg daemon enable records a native codex.exe and daemon offer codex seats become addressable without the workaround.

Written by the indexing model from the issue text.

Description

Summary

On Windows with npm-installed Codex, every Codex seat stays blocked / windows_codex_executable_unresolved. Meanwhile daemon offer codex says it is available.

Details

  • agmsg daemon enable records npm's extensionless shim (.../AppData/Roaming/npm/codex) as meta.codex_path. The cause is that _resolve_codex (scripts/daemon.sh, around L492) takes the first <PATH dir>/codex.
  • The Windows queue gate, resolveWindowsCodexExe (scripts/daemon/channels/windows-codex-queue.mjs, L11), accepts an absolute path only when its basename is codex.exe.
    • It does the npm vendor-exe lookup only for the bare name codex.
    • So the recorded path is never accepted.
  • Git Bash's .exe lookup also makes [ -f <dir>/codex ] true for a lone codex.exe. That path is still recorded as codex.

Proposal

On Windows, resolve the recorded path the way resolveWindowsCodexExe resolves the bare name: first <dir>\codex.exe, then npm's @openai/codex-win32-<arch> vendor exe.

Alternatively, let the gate apply that lookup to an absolute codex shim as well.

Workaround

AGMSG_REAL_CODEX=<native codex.exe> agmsg daemon enable records the native exe. The seat became addressable on the next check, with no restart.

Environment

  • agmsg v1.6.0 (install.sh), agmsgd enabled with agmsg daemon enable
  • Windows 11 Pro 26200, non-admin user, Git for Windows bash 5.2.37 (MSYS)
  • Node 24.11.1, Codex CLI 0.164.0 (npm global), Claude Code 2.1.310
Dominant language
Shell
Stars
1.5k
Forks
156
Avg merge
19h 36m
Merged PRs (30d)
213

Getting set up

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 fujibee/agmsg

All issues in fujibee/agmsg

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.