docs: add CodexBar for Windows

[hinneslung]

Hi, thanks for building CodexBar! I would like to request listing CodexBar for Windows alongside Win-CodexBar.

It's a native Windows tray app that uses the unchanged CodexBar CLI through WSL2, with x64 and ARM64 installers. I maintain the Windows code and handle support in the fork.

This adds one README link, following the Linux integration listings in #991 and #2734. No application code changes.

Checks: git diff --check passed; confirmed the repository and published downloads are available. make test could not run because make is not installed on this Windows machine. A native Windows debug build stopped in unchanged upstream CQuickJS code (clock_gettime / CLOCK_MONOTONIC unavailable).

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs real behavior proof before merge. Reviewed September 9, 2026, 7:30 AM ET / 11:30 UTC.

ClawSweeper review

What this changes

Adds a README link to an independently maintained Windows tray app, describing its WSL2 requirement and x64 and ARM64 installers.

Merge readiness

⛔ Blocked before merge - 2 items remain

This is a useful, narrowly scoped listing consistent with previously merged companion-project links. It is absent from current main and the latest release, and the repository profile does not permit automatic closure.

Priority: P3
Reviewed head: cc09cf66411c634c386897c6801a080c251f4afd

Review scores

Measure	Result	What it means
Overall readiness	🦪 silver shellfish (2/6)	The patch is focused and source-correct, while the strict external-PR proof requirement remains unmet for the root README change.
Proof confidence	🦪 silver shellfish (2/6)	Needs stronger real behavior proof before merge: The changed surface is the README’s Windows listing; the contributor reports a working destination and published downloads, but supplies no after-change rendered-link demonstration. A redacted screenshot or short recording of the rendered entry opening the intended repository would cover this narrow change; Windows provider execution is unnecessary. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Needs proof	Needs stronger real behavior proof before merge: The changed surface is the README’s Windows listing; the contributor reports a working destination and published downloads, but supplies no after-change rendered-link demonstration. A redacted screenshot or short recording of the rendered entry opening the intended repository would cover this narrow change; Windows provider execution is unnecessary. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed	7 items	Reviewed policy and exact introduced change: Read the full root AGENTS.md and README. The pinned base-to-head diff adds exactly one Markdown link; no application, dependency, workflow, or settings files change. No .agents/maintainer-notes directory exists. The read-only review did not run builds or artifact-producing tests. Current main still lacks the listing: The Windows section on pinned main lists only Win-CodexBar; the proposed companion link is distinct. Latest release comparison: The v0.57.0 README also lacks this Windows companion listing.
Findings	None	None.
Security	None	None.

How this fits together

CodexBar’s README directs users to platform-specific companion projects. The new Windows entry leads readers to a separate repository that distributes and supports its own app.

flowchart LR
  A[Windows user] --> B[CodexBar README]
  B --> C[Windows companion listing]
  C --> D[External project repository]
  D --> E[Installers and setup guide]
  D --> F[External support tracker]

Loading

Before merge

• Add real behavior proof - Needs stronger real behavior proof before merge: The changed surface is the README’s Windows listing; the contributor reports a working destination and published downloads, but supplies no after-change rendered-link demonstration. A redacted screenshot or short recording of the rendered entry opening the intended repository would cover this narrow change; Windows provider execution is unnecessary. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
• Complete next step (P2) - Add redacted evidence of the rendered README entry opening the intended project. Updating the PR body should trigger a fresh review; if it does not, ask a maintainer to comment @clawsweeper re-review.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep the concise companion listing with its explicit WSL2 prerequisite and separate project support boundary.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR adds a documentation link rather than repairing reported runtime behavior.

Is this the best way to solve the issue?

Yes: a single entry in the existing Windows section follows merged companion-listing precedent and avoids importing platform-specific code.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 928166f89947.

Labels

Label changes:

• add P3: This is a one-line documentation discoverability improvement with no runtime changes.
• add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🐚 platinum hermit.
• add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs stronger real behavior proof before merge: The changed surface is the README’s Windows listing; the contributor reports a working destination and published downloads, but supplies no after-change rendered-link demonstration. A redacted screenshot or short recording of the rendered entry opening the intended repository would cover this narrow change; Windows provider execution is unnecessary. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Label justifications:

• P3: This is a one-line documentation discoverability improvement with no runtime changes.
• rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs stronger real behavior proof before merge: The changed surface is the README’s Windows listing; the contributor reports a working destination and published downloads, but supplies no after-change rendered-link demonstration. A redacted screenshot or short recording of the rendered entry opening the intended repository would cover this narrow change; Windows provider execution is unnecessary. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

What I checked:

• Reviewed policy and exact introduced change: Read the full root AGENTS.md and README. The pinned base-to-head diff adds exactly one Markdown link; no application, dependency, workflow, or settings files change. No .agents/maintainer-notes directory exists. The read-only review did not run builds or artifact-producing tests. (README.md:238, cc09cf66411c)
• Current main still lacks the listing: The Windows section on pinned main lists only Win-CodexBar; the proposed companion link is distinct. (README.md:236, 928166f89947)
• Latest release comparison: The v0.57.0 README also lacks this Windows companion listing. (README.md:236, 45cda6084d64)
• Merged listing precedent: docs: point Linux users at codexbar-waybar companion repo #991 and Add codexbar-cosmic-applet to Linux desktop integrations #2734 merged comparable companion links. GitHub’s commit response verifies Marouan-chak as the author of the former README addition. Local deeper history and blame encountered unavailable objects, so no source-line introduction attribution is claimed. (README.md, 150c5abf16b6)
• Destination ownership and description: GitHub identifies the linked repository as hinneslung/CodexBar-for-Windows. Its README describes a native Swift Windows app using the upstream CLI through WSL2 and directs support to its own tracker. This supports the listing’s description without making that external implementation part of this patch. (README.md)
• Advertised downloads exist: Release v0.56.8-windows.1, published September 8, includes both windows-x86_64-setup.exe and windows-arm64-setup.exe assets. Release notes explicitly identify the independent fork and disclose unsigned downloads.

Likely related people:

• Marouan-chak: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Add a screenshot or short recording showing the rendered README entry opening the intended repository, with private information redacted.

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.