Package wacli

[mavam]

Request

Please add openclaw/wacli as a package output, including aarch64-darwin support.

wacrawl covers read-only access to WhatsApp Desktop data, while wacli is the complementary linked-device client for live synchronization, search, and sending. Packaging both here would provide the complete WhatsApp toolchain without requiring Homebrew.

Packaging notes

• Upstream requires Go 1.27 or newer.
• Build with CGO enabled and the sqlite_fts5 tag so message search uses its FTS index.
• Build target: ./cmd/wacli.
• Upstream documents the required build flags in docs/install.md.
• macalinao/additional-nix-packages contains a small existing buildGoModule derivation that may be useful as prior art.
• Authentication and the WhatsApp store should remain mutable outside the Nix store.

I'm currently carrying a local derivation and would like to consolidate on this flake once wacli is available here.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 20, 2026, 3:46 AM ET / 07:46 UTC.

Summary
This remains a concrete, in-scope packaging request: current main has no wacli output, and no open implementation PR was found. The linked source derivation is useful prior art, but upstream release archives offer a path consistent with repository policy.

Reproducibility: not applicable. this requests a new package output, and source inspection confirms that output is absent; it does not report broken existing behavior.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
A focused packaging PR is suitable for manual promotion using the existing tool pattern; automatic bug-fix intake does not apply to this new capability.

Review details

Best possible solution:

Provide a release-backed wacli package with matching plugin metadata, update automation, and offline runtime checks, while retaining upstream user-owned authentication and database paths.

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

Not applicable: this requests a new package output, and source inspection confirms that output is absent; it does not report broken existing behavior.

Is this the best way to solve the issue?

Yes, adding the tool here follows the documented ownership boundary; prefer the published release archives over a source derivation unless platform checks establish that the archives are unsuitable.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Published archives still need Nix runtime and FTS5 validation on each exported platform; their availability alone does not prove compatibility.

Codex review notes: model internal, reasoning medium; reviewed against 55fca87692e9.

Label changes

Label changes:

• add P2: This is a concrete optional package addition with a clear downstream use case and limited scope.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:queueable-fix: Current issue advisory state selects this label.
• add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.

Label justifications:

• P2: This is a concrete optional package addition with a clear downstream use case and limited scope.

Evidence reviewed

Acceptance criteria:

• go test -race -count=1 ./cmd/update-tools ./cmd/sync-skills
• go vet ./...
• nix flake check --no-build --all-systems
• nix flake metadata --no-update-lock-file --no-write-lock-file ./tools/wacli
• nix build .#wacli --no-link --print-out-paths --print-build-logs

What I checked:

• Requested export is absent: The complete package support matrix includes wacrawl but not wacli; exports are generated exclusively from that matrix. README, package files, updater catalog, and plugin directories likewise contain no wacli implementation. GitHub main matches the inspected checkout. (flake.nix:13, 55fca87692e9)
• Repository ownership and packaging policy: The full root AGENTS.md was read. It assigns tool packaging here, prefers suitable upstream release assets, and requires package, plugin metadata, checks, and updater integration together for first-party batteries. No VISION.md or maturity scorecard was found. (AGENTS.md:9, 55fca87692e9)
• Suitable release candidates already exist: Repository identity was verified through GitHub. Release v0.18.2, published September 11, 2026, provides darwin_arm64, linux_amd64, and linux_arm64 archives. Its annotated tag resolves to the recorded commit. Archive availability supports release packaging but does not establish Nix runtime compatibility. (cd4370388f03)
• Authoritative build and state contract: The issue explicitly depends on wacli's installation contract. Release documentation requires Go 1.27 and CGO for source builds, identifies sqlite_fts5 as necessary for indexed search, and documents mutable user-owned stores. The Darwin release configuration enables CGO and sqlite_fts5. Authentication keys and databases belong outside the Nix store. (docs/install.md:8, cd4370388f03)
• Reporter supplied useful prior art: The linked derivation was inspected after verifying repository ownership. It packages wacli 0.18.1 with buildGo127Module, sqlite_fts5, cmd/wacli, and a version check. It is a useful source-build fallback, rather than proof that this target already exports wacli. (pkgs/by-name/wa/wacli/package.nix:9)
• Canonical and release checks: The REST listing returned all 33 repository items, with this issue the only open item and no wacli implementation PR. The supplied merged references concern package-export refactoring and maintenance-command cancellation, not adding wacli. The releases endpoint returned an empty array.

Likely related people:

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

How this review workflow works

• 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.