Extension System Test

 

Cursive System Test

This page checks the prerequisites for Cursive TypeID. Green checks mean ready to use.

Running checks 0 of 7 checks complete
  1. Chromium-based browser

    Detecting…

    How to fix

    Cursive requires a Chromium-based browser. Install one of:

    • Google Chrome (recommended) — google.com/chrome
    • Microsoft Edge, Brave, Arc, or Opera

    Firefox and Safari are not currently supported. Reopen this page in a Chromium browser after installing.

  2. Cursive TypeID extension installed

    Waiting for response…

    How to install or troubleshoot

    Install Cursive TypeID: Get it from the Chrome Web Store.

    1. Click Add to Chrome on the Web Store page.
    2. Approve the permissions prompt.
    3. Come back to this page and reload (Ctrl+Shift+R).

    Already installed? Open chrome://extensions and verify:

    • The extension is enabled (toggle on the bottom-right of its card).
    • There is no red Errors button — if so, click it and share the contents with support.
    • If you just updated, click the circular Reload icon on the extension card.
  3. Backend installed and active

    Probing 127.0.0.1…

    How to start the backend

    New here? See the full setup guide at cursivetechnology.com/about-extension — it covers downloading, installing, and verifying the Cursive backend.

    Already installed? Run through these checks:

    1. Look for the Cursive icon in your system tray (Windows, bottom-right) or menu bar (Mac, top-right). If it is missing, the backend is not running.
    2. If installed but not running, launch Cursive Backend from your Start menu / Applications folder.
    3. Confirm a firewall or antivirus is not blocking 127.0.0.1:5000 or 127.0.0.1:52845.

    Still failing? Run this 30-second test. Open http://127.0.0.1:5000/status in a new tab. You should see something like:

    {"enrolled": false, "model_loaded": true, "window_size": 50}

    If the page does NOT load (blank, refused, or "site can't be reached"): the backend is genuinely down. Restart it from your Start menu / Applications folder, then re-run this test.

    If you DO see the JSON above but this page still reports the backend as unreachable: the backend is fine, but the extension cannot talk to it. Try, in order:

    1. Open chrome://extensions, find Cursive TypeID, and click the circular Reload icon on its card.
    2. Re-run the checks on this page using the Re-run checks button below.
    3. If still failing, fully close and reopen Chrome (not just this tab — quit the browser).
    4. Check your antivirus or firewall for blocked outbound connections from Chrome to 127.0.0.1 — some security suites quarantine localhost traffic from browser extensions.
    5. As a last resort, remove and reinstall the extension from chrome://extensions.
  4. Extension can read data on all sites

    Checking permissions…

    How to grant site access
    1. Open chrome://extensions.
    2. Find Cursive TypeID and click Details.
    3. Scroll to Site access and choose On all sites.
    4. Reload this page.

    If set to On click or On specific sites, the extension will not capture on pages it has not been explicitly granted — Cursive will appear to work intermittently.

  5. Monitoring enabled in extension

    Reading toggle…

    How to enable monitoring
    1. Click the Cursive icon in your browser toolbar (top-right).
    2. If you do not see it, click the puzzle-piece icon and pin Cursive TypeID.
    3. Toggle Monitoring to On.

    Monitoring is off by default after a fresh install. Once enabled, the preference persists across sessions.

  6. Extension storage healthy

    Round-tripping a key…

    How to fix storage errors

    This usually means the browser ran out of storage quota for extensions, or the extension profile is corrupted.

    1. Free disk space (Chrome requires at least a few hundred MB available).
    2. If the problem persists, remove and reinstall the extension from chrome://extensions.

    If you also need to reset the backend itself, use its uninstaller; it will prompt you about keeping or deleting your signature data.

  7. System clock in sync

    Comparing client vs. server time…

    How to sync your clock

    Biometric timestamps assume the client and server agree on wall-clock time. Drift of more than a few seconds will degrade verification accuracy.

    • Windows: Settings → Time & language → Date & time → toggle Set time automatically on, then click Sync now.
    • macOS: System Settings → General → Date & Time → enable Set time and date automatically.
    • Linux: sudo timedatectl set-ntp true