Chrome extension · local Sheets review

Clearer data.
You stay in control.

Review the Google Sheets you choose, understand each finding, and create checked correction copies. Your original workbooks stay intact.

Set up the companionRead the privacy policy

A local companion is required. You need the source repository, Node 24.19.0, npm 12.0.2 and an open terminal on your computer. Installing the extension alone does not start the companion.

A Chrome Web Store draft exists, but the extension is not yet approved or publicly installable. No public install link is claimed here. The publisher configures Google authorization for the store package; store users do not need to create their own OAuth client. Real Google access remains limited to eligible test accounts while public Google verification is pending.

A review you can follow

01 · CHOOSE

Select the scope

Discover accessible spreadsheets, then select the workbooks to scan. Multiple workbooks require a separate opt-in. Nothing is selected automatically.

02 · REVIEW

See the exact findings

Check column mappings, donor and gift identifiers, dates, amounts and currencies. Inspect source-cell references and every proposed before-and-after value.

03 · APPROVE

Create correction copies

Approve a specific plan before new workbooks are created. Tidepath reads copies back and records their status. Original workbooks are never edited.

Set up the companion on your computer

The companion is available as source, without a bundled installer or automatic startup. This 0.1.x release has been live-tested on Windows x64 only. Complete companion installation and extension operation on other platforms have not been verified.

  1. Install the pinned runtime. Use Node 24.19.0 and npm 12.0.2. Follow the development setup for prerequisites.
  2. Get the source and dependencies.
    git clone --branch codex/tidepath-mvp https://github.com/jemsbhai/buildbettercode4miami.git tidepath-companion
cd tidepath-companion
npm ci

For a configured store test package

If you already have authorized access to the publisher-configured store test package, open Tidepath and confirm that its displayed extension ID is bdojcligphldnmdchmlhgibhlldgflcd. Do not rebuild or edit the installed package's manifest. The publisher supplies its Google OAuth configuration; you do not create a client yourself.

Start the companion with this store ID and a separate journal:

npm run sheets:local -- --extension-id bdojcligphldnmdchmlhgibhlldgflcd --data-file .data/local-sheets/store-google-journal.json

Keep the terminal open, paste its generated token into Local connection token, and choose Connect local companion. Then choose Connect Google account with an eligible test account. Public Google access is pending verification; a configured package does not by itself grant every account authorization. Store approval and a public install link are also pending.

For a credential-free rehearsal with that installed package, stop the companion cleanly and use a separate fictional journal:

npm run sheets:local -- --extension-id bdojcligphldnmdchmlhgibhlldgflcd --demo --data-file .data/local-sheets/store-demo-journal.json

Pair the new token, find the fictional spreadsheets and choose your scope. Scan, confirm mappings, review proposed changes and approve fictional copies. Do not connect Google in fictional mode. Fictional mode makes no Google or AI requests and creates no Google files.

For a local installation from source

You can build an unpacked extension before a public store release. Run npm run extension:package, open chrome://extensions, enable Developer mode and choose Load unpacked. Select out/tidepath-extension, keep that folder in place and copy its actual extension ID. An unpacked ID can differ from the store ID above.

npm run sheets:local -- --extension-id YOUR_UNPACKED_EXTENSION_ID --demo

The default source package has no Google OAuth client. Fictional rehearsal works immediately after pairing. Only this local source-install path requires you to supply your own matching Chrome-extension OAuth client to use real Google data. Follow the local Google authorization and packaging guide, then stop fictional mode, start without --demo, pair the new token and connect an eligible Google account.

The companion listens only on 127.0.0.1:4318. Use a different journal for fictional mode and Google mode. A stopped companion cannot scan. Deterministic review needs no AI account or key.

Do not repackage an already configured local installation without its OAuth client option: default packaging replaces that configuration. The separate sheets:bridge command belongs to the older Google Workspace integration; use sheets:local for this extension.

Your data, explained

Google provides the selected spreadsheet data and stores correction copies that you approve. Checks run in the companion on your computer, which keeps a local journal of selected eligible snapshots, findings and operation history.

The extension requests Google authorization, session storage and access to its loopback companion. It does not monitor other websites, inject page scripts, track browsing history, or run advertising or analytics. The publisher does not automatically receive your spreadsheet data or keys.

Local pairing uses HTTP on your own device; Google and optional AI API requests use HTTPS. Journals are not encrypted by Tidepath. Protect your device and delete unneeded local records.

Read the complete data, retention and deletion policy.

Optional advice, off by default

Deterministic review needs no model key. Optional AI advice requires your own OpenAI key entered in the hidden terminal prompt, then approval of one exact outgoing request.

That request contains scan issue counts and standard table/field categories, not raw cells, contact values, workbook names or IDs. OpenAI receives the approved request directly. Advice cannot approve or apply corrections.

OpenAI API use is billed to your account. Limits do not guarantee an exact bill; failed requests may incur charges. Keep AI off if you only want deterministic review.

Know what a correction copy includes

Supported rules and limits · Companion operation and recovery

Support and recovery

The companion is not responding

Keep its terminal open, confirm port 4318 is available and use the exact installed extension ID. After restarting the companion, pair with its newly generated token. Reloading the extension or restarting Chrome clears its session pairing.

Google authorization or account history is unavailable

Verify that the package has an OAuth client configured for its extension ID and that your account is eligible. Reconnect after expired authorization. A different Google account needs a separate --data-file; do not overwrite another account's journal.

A correction request was interrupted

Check History and recovery before retrying. Preserve the original request identity. If creation may have succeeded without a response, inspect the recorded filename in Google Drive instead of submitting a new plan repeatedly.

Stop or uninstall

Disconnect Google, forget the connection, then press Ctrl+C in the companion terminal and wait for Stopped cleanly. After stopping, remove local journals, backups and downloads you no longer need. Uninstalling the extension does not delete those files or Google correction workbooks. Revoke the Google grant and remove unwanted copies separately in your Google account.

Contact jemsbhai@gmail.com or report an issue. Include a fictional reproduction or redacted error description. Never send API keys, tokens, private journals or confidential spreadsheet data.