gmail-sync

/gmail-sync - Sync Application Status from Gmail

You are scanning the user's Gmail for status signals on tracked job applications (interview invites, assessment links, offers, rejections) and, once approved, writing the detected changes into job_search_tracker.csv and documents/applications/<company>_<role>/outcome.md - the same two places /outcome writes to, in the same schema.

Unlike /outcome (which asks the user what happened), /gmail-sync classifies real emails on its own - but it never writes on its own. Every classified change is presented as a batch before anything touches the tracker or outcome.md, and only proceeds once the user approves it (approving the whole batch at once is fine; writing first and flagging it after is not). Because a wrong write silently corrupts application history that /setup later calibrates from, every proposed change must cite its source email and every uncertain case must be surfaced instead of guessed. Never treat this command's job as "notice something in an inbox" - it is "propose a correct, sourced line for a permanent record, and write it only once the user says yes."

Follow these steps in order.

---

Step 0: Prerequisites

Confirm the Gmail MCP tools (mcp__claude_ai_Gmail__*) are available. If not, tell the user to connect the Gmail integration (claude.ai Settings → Connectors → Gmail) and stop - do not attempt this via Bash, IMAP, or any other channel.

---

Step 1: Parse Input

$ARGUMENTS may contain:

• Nothing → default lookback (see Step 3)
• A company name, e.g. /gmail-sync acme → scope the search to that one tracked application
• since <YYYY-MM-DD> → override the lookback start date for this run only (does not change the persisted state file)

---

Step 2: Load State

1. Read job_search_tracker.csv. If it does not exist, tell the user there is nothing to sync against yet (suggest /outcome or /apply first) and stop. Do not create it here - /gmail-sync never originates new applications, only updates existing ones.
2. Read gmail_sync/state.json (create if missing: {"last_sync": null, "processed_message_ids": []}).
3. Build the set of open applications: tracker rows whose status is not Final (per the Tracker status vocabulary in /outcome). For each, derive its archive folder documents/applications/<company>_<role>/ by the Subfolder naming rule in documents/README.md and check whether outcome.md exists there. Reuse this exact derived path for any write in Step 7a.