E2E coverage for agent CLIs on native Windows

Open
#48 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@zpzjzj is already working on this.

Since Jul 2, 2026.

Assessment

This issue has not been assessed yet.

Description

Context (PR #33 self-review follow-up): the agent CLI path (Claude Code / Codex / Qoder) is launched via a bash-based Node/nvm bootstrap, so `internal/agent` on native Windows currently has zero e2e coverage. The Windows e2e job (`E2E (none runtime, Windows)`) only exercises mock-engine + script-judge.

Proposal:

  • Either: rework the Node/nvm bootstrap to run under PowerShell, then enable the existing e2e suite on Windows.
  • Or: add a Windows-WSL job that boots WSL, installs the agent CLIs, and runs the existing full e2e — covers the recommended workflow.
  • Or (interim): add a Windows-host job that requires Git Bash pre-installed and runs full e2e through bash — covers the documented limitation path.

Currently the recommended workflow ("use WSL2") has no CI verification.

Dominant language
Go
Stars
1.5k
Forks
134
Avg merge
1d 22h
Merged PRs (30d)
61

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 alibaba/skill-up

All issues in alibaba/skill-up

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.