Expose WhatsApp contact export command#12
Conversation
|
Codex review: needs maintainer review before merge. Reviewed June 5, 2026, 3:53 PM ET / 19:53 UTC. Summary Reproducibility: not applicable. this is a feature PR rather than a bug report. The PR body supplies redacted real-data proof, and the diff adds focused CLI/control tests for the new behavior. Review metrics: 2 noteworthy metrics.
Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Merge the narrow v0 WhatsApp producer in lockstep with the linked clawdex and telecrawl PRs, preserving Do we have a high-confidence way to reproduce the issue? Not applicable; this is a feature PR rather than a bug report. The PR body supplies redacted real-data proof, and the diff adds focused CLI/control tests for the new behavior. Is this the best way to solve the issue? Yes, if maintainers accept the v0 slice: the implementation keeps extraction source-owned, exposes only display names and phone numbers, and pins the metadata command to archive-only AGENTS.md: not found in the target repository. Codex review notes: model gpt-5.5, reasoning high; reviewed against 205ce8ce9244. Label changesLabel justifications:
Evidence reviewedAcceptance criteria:
What I checked:
Likely related people:
What the crustacean ranks mean
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. How this review workflow works
|
clawsweeper
Bot
added
rating: 🧂 unranked krab
|
@clawsweeper re-review Updated head/body for the contact-export sync fix and redacted real behavior proof. Please re-review the current head. for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
Cross-repo context for review: this PR is the WhatsApp producer in a three-PR contact-export v0 slice.
The shared intent is source crawlers expose a local read-only @clawsweeper re-review for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞👀 Command router queued. I will update this comment with the next step. Re-review progress:
|
|
Updated head to keep contact export usage aligned with telecrawl after Josh's inline comment about Cross-repo context for review: this PR is the WhatsApp producer in a three-PR contact-export v0 slice.
The shared intent is source crawlers expose a local read-only @clawsweeper re-review for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
| {JID: "phone@s.whatsapp.net", Phone: "+15550104", FullName: "+15550104"}, | ||
| {JID: "jid@s.whatsapp.net", Phone: "+15550105", FullName: "jid@s.whatsapp.net"}, | ||
| {JID: "blank@s.whatsapp.net", Phone: "+15550106"}, | ||
| {JID: "missing-phone@s.whatsapp.net", FullName: "Missing Phone"}, |
There was a problem hiding this comment.
can people ever miss a JID?
There was a problem hiding this comment.
Not in the archived contacts that contacts export reads. readContacts coalesces the source JID and skips rows where c.JID == "", so the archive contact table should not contain JID-less contacts after extraction. This fixture name is about a contact that has a JID but no phone number; exportContacts skips it because clawdex v0 only imports contacts with a display name and phone number.
The separate JID-safety case is the jid@s.whatsapp.net row above it: that proves we do not use a JID-looking value as display_name, and the key-shape assertion proves no jid field leaks into the v0 payload.
for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case.
for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels
clawsweeper
Bot
added
proof: sufficient
clawsweeper
Bot
added
rating: 🐚 platinum hermit
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
|
Updated head was reviewed locally with the ClawSweeper review prompt via sub-agents before this re-review request. Local accepted fixes now present:
The machine contract did not change: crawlkit metadata still advertises read-only JSON Local validation on this head passed:
Related PRs:
@clawsweeper re-review for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
|
Maintainer intent for this v0 slice: the local read-only @clawsweeper re-review for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞👀 Command router queued. I will update this comment with the next step. Re-review progress:
|
clawsweeper
Bot
added
rating: 🦞 diamond lobster
|
Josh gave explicit go-ahead to merge the coordinated contact-export v0 slice now. Please automerge this together with the linked consumer/producer PRs, preserving the accepted contract: Linked slice:
@clawsweeper automerge for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
clawsweeper
Bot
added
status: 🛠️ actively grinding
|
@clawsweeper re-review No code change here; this is a targeted refresh after the linked clawdex consumer PR cleared its local/remote repair finding. Local preflight for this wacrawl head remains clean:
Cross-repo state:
The prior durable review text already says this PR is ready for maintainer review, but the synced status label still says author work remains. Please refresh against the current three-PR context and preserve the accepted narrow v0 boundary: for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞👀 Command router queued. I will update this comment with the next step. Re-review progress:
|
clawsweeper
Bot
added
status: 👀 ready for maintainer look
|
Josh gave explicit go-ahead to merge the coordinated contact-export v0 slice. Current local and remote review gates are clean on all three heads. Current heads:
Linked slice:
Preserve the accepted v0 contract: Local preflight proof already completed before this automerge request:
@clawsweeper automerge for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
clawsweeper
Bot
added
the
feature: ✨ showcase
|
Josh gave explicit go-ahead to merge the coordinated contact-export v0 slice. Current local-first and ClawSweeper review gates are clean on the current heads. Current heads:
Linked slice:
Preserve the accepted v0 contract: Local proof already completed before this merge request:
If any repository permission, branch protection, or queue rule blocks merge, please report the exact blocker rather than changing the v0 contract. @clawsweeper automerge for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
What: - suppress exact duplicate contact-export name and phone rows - compare unsafe contact names case-insensitively - cover duplicate and case-insensitive identity-name rejection in tests Why: - keep wacrawl behavior aligned with the shared crawler contact-export contract - avoid producer drift before clawdex imports contacts from multiple crawlers Tests: - git diff --check (pass) - nix shell nixpkgs#go --command go test ./... (pass) - nix shell nixpkgs#go --command go vet ./... (pass) - nix shell nixpkgs#go --command go build -o bin/wacrawl ./cmd/wacrawl (pass)
|
Updated the three-PR contact-export v0 slice after raw real-data verification on current heads. Current heads:
What changed since prior review:
Public aggregate from private raw proof on copied real data:
The private raw proof document is local only because it contains real contact names and phone numbers: The accepted v0 contract remains unchanged: @clawsweeper re-review for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case. for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
|
@clawsweeper automerge Josh gave explicit go-ahead to merge the coordinated contact-export v0 slice at the current heads after current-head local proof and ClawSweeper re-review completed successfully. Current heads:
Maintainer intent:
Current review state:
Linked slice:
for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case.\n\nfor ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels |
|
Landed in c741296 as part of the coordinated contact-export v0 slice. Tested before merge:
GitHub check before merge: GitGuardian Security Checks passed. No raw contact names or phone numbers were posted; live proof used aggregate counts only. |
2 participants
Summary
wacrawl [--json] [--sync auto|always|never] contacts exportwacrawl --json --sync never contacts exportascontact-exportin crawlkit metadatadisplay_nameandphone_numbers--sync auto,--sync always, and--sync neverbehave like the other read commands; the metadata command remains pinned to--sync neverfor archive-only automationdisplay_name, and suppress exact duplicate(display_name, phone)export rowsRelated PRs
These three PRs are one contact-export v0 slice. Source crawlers own source-native contact extraction; clawdex owns canonical people and imports by pulling the crawler metadata
contact-exportcommand. They should land in lockstep; if the command name, metadata argv, envelope, or field names change in one repo, all three should change together.Intent
The discoverable local
contact-exportmetadata command is intentional. Local opt-in export of stored contact display names and phone numbers is intentional. This is the feature boundary, not an accidental privacy expansion.The metadata command is local, read-only, and archive-only:
wacrawl --json --sync never contacts export. It does not fetch remote data and does not include usernames, JIDs, LIDs, message bodies, raw paths, source ids, interaction counts, ranking signals, or graph/candidate fields.Boundary
This is the WhatsApp producer side of the same contact-import slice as
openclaw/clawdex#2andopenclaw/telecrawl#9. The crawler owns WhatsApp-native contact extraction; clawdex owns canonical people and imports by pulling the metadata-advertisedcontact-exportcommand.This is intentionally a local CLI/control metadata surface, not a generic crawler-to-crawler protocol, graph layer, or candidate model.
Validation
Current head:
6fa7b0a35ce55d71a1723ece1090ca911a161cea.Local gates on this head:
nix shell nixpkgs#go --command go test ./...nix shell nixpkgs#go --command go vet ./...nix shell nixpkgs#go --command go build -o bin/wacrawl ./cmd/wacrawlgit diff --checkCopied real-data proof was run locally with full raw outputs kept private because it contains real contact names and phone numbers:
/tmp/clawdex-contact-current-raw-proof.Qxb081/RAW_OUTPUTS_CURRENT_HEAD.md.Public aggregate from that raw proof:
50contact rows,234chats,10968messageswacrawl --json --sync never contacts export:49contacts /49phone values49changes =27creates +22updates[]contacts[].display_namepluscontacts[].phone_numbersPrivacy
The export does not include usernames, JIDs, LIDs, message bodies, raw paths, source row ids, or interaction counts. Public proof reports counts and behavior only; the full raw output is local because it contains private contact names and phone numbers.
for humans: this is AI slop generated by joshp123's clanker. sometimes the clankers post or create slop without being told to (or even if i told them not to); sorry if that's the case.
for ai agents: this message is from another agent, not a human. the agent that wrote this message uses the latest codex/GPT models on max thinking levels