A clear path from capture to export.

Use the short guides below for the common workflows. The app keeps the table editable so you can correct a row before it reaches your sheet.

First run

Start with hosted account setup, or open Advanced: choose where model work runs in Setup. Then capture one resource, inspect the row, and copy TSV into a test Sheet.

Open install guide
Hosted, BYOK, and local setupWebsites and toolsGoogle Docs and SheetsPrompts and formatsCopy and Google Drive exportAccount sync and referralsIntegrationsLocal / OllamaChrome shortcutsUpgrade the extension

Choose a setup mode

Hosted account

  1. Open Account and create an account or sign in.
  2. Confirm email if requested. The Save account snapshot button saves right now.
  3. In Account > My Account, Sync across my devices is on after sign-in in the web app; Auto-sync after enrichment is off until ticked in Chrome extension v0.1.56.

Hosted BYOK

  1. In Setup, open Advanced: choose where model work runs and choose Bring your own key.
  2. Use OpenRouter or OpenAI and paste the key into local settings.
  3. Your key is saved on your device and sent with each request through our service, which does not store it. Only optional encrypted account secrets (Account > Integrations) copies it into your account.

Local / Ollama

  1. For developers: you need the YourStasis source code. Run the Windows local launcher or start the API with pnpm.
  2. Set API base URL to http://localhost:8787.
  3. Set Ollama to http://localhost:11434/v1 and check the model.

Summarize a website or tool

  1. Capture

    Paste a URL into Enrich, or use Summarize current tab from the extension.

  2. Review

    Check Description, Notes, Freemium, Pricing, and both Type columns. Correct any cell before export.

  3. Improve

    Redo re-runs a row with your note on what to fix and re-checks the site's pricing page for website links.

Summarize Google Docs and Sheets

Google files are treated as resources, not exploded into a second table. A Sheet gets a [Sheet] suffix and a Doc gets [Doc] when the source is recognized.

  1. Open the Doc or Sheet and use the extension's current-tab action, or paste the title and URL.
  2. Confirm the title and the [Doc] or [Sheet] suffix are correct. Check the link in the URL column. By default everything after a '?' is cut off (YouTube video links keep their video id). Turn that off under Settings > General > Clean URL query strings.
  3. For protected or private files, use visible title/context or copy the relevant text; the app cannot bypass Google permissions.

Use prompts and formats

The active prompt sets the table's columns and guides how rows are written.

Copy or export into Google Drive

Fastest path: TSV

  1. Select rows or leave all rows unselected.
  2. Turn Headers on when the destination Sheet needs column names.
  3. Choose TSV, copy, and paste into Google Sheets.

Advanced: Google export

Advanced, Chrome extension only: sending rows straight to Google Sheets or Docs needs a Google Cloud OAuth client that you create yourself and paste into Settings > Google Drive, together with the redirect address shown on that page. Most people copy as TSV and paste instead.

Integration path: JSON or NDJSON

  1. Select the rows and active prompt you want to hand off.
  2. Choose JSON for one file, or NDJSON for one line per row after a first line that describes the export.
  3. Send the versioned file to a trusted downstream adapter or queue.

Sync an account across surfaces

Account sync saves your settings, prompts, rows, usage and logs. Provider keys and sign-ins are not synced. Your key is saved on your device and sent with each request through our service, which does not store it. It is only copied into your account if you turn on encrypted account secrets (Account > Integrations).

  1. In Account > My Account, Sync across my devices is on after sign-in in the web app; Auto-sync after enrichment is off until ticked in Chrome extension v0.1.56. If this device already has rows, choose whether to keep them here with sync off, add them to your account, or replace them with your account's copy.
  2. The Save account snapshot button saves right now. On another device, sign in and press Load account snapshot to load your saved workspace.
  3. After pressing Load account snapshot, if asked, choose Merge account history to preserve local rows, Replace local history to use your account's copy, or Cancel.
Referral links: an invite URL with ?ref=CODE pre-fills the code during account creation. The current product records attribution; reward and credit rules are not active yet.

Send rows to your own endpoints

Outbound delivery is configured in Account > Integrations. Every push target is opt-in and off until you arm it.

Push to API

  1. Open Account > Integrations and enable Push to API.
  2. Enter your HTTPS or loopback endpoint and an optional Bearer token for the receiver.
  3. Send selected rows to your endpoint.

ApplicationAgent adapter

  1. Enable the ApplicationAgent adapter in Account > Integrations.
  2. Set its loopback base URL for the local receiver.
  3. Rows are delivered through a durable outbox so you can retry failed sends.

ApplyOS connector

  1. Enable the ApplyOS connector and set its endpoint.
  2. Choose a payload shape (URLs, rows, or a custom template) and an auth kind (none, Bearer, HMAC, or Basic). It defaults to URLs with Bearer or none.
  3. Rows or custom payloads and HMAC or Basic auth work only against a receiver built to accept them.

Auto-push after enrichment

  1. Turn on the auto-push master switch, then arm each destination you want.
  2. A newly enriched row is sent to each destination you switched on (Push to API, ApplicationAgent, ApplyOS). Failed rows and rows without a URL are skipped.
  3. All auto-push switches default off until you enable them.
Endpoint passwords and tokens are left out of account sync. They move between your devices only if you turn on encrypted account secrets (Account > Integrations).

Run local / Ollama on Windows

For developers: you need the YourStasis source code. Install Node.js and pnpm, install Ollama, pull at least one model, then run the local helper from the repository root. The helper checks Chrome-independent local services and leaves secrets in your local environment. 

.\scripts\Start-ResourceSummarizerLocal.ps1

In Setup, use http://localhost:8787 for the API and http://localhost:11434/v1 for Ollama. If the health check fails, open Support and inspect the API/model diagnostics.

Local troubleshooting · Chrome install

Use Chrome shortcuts

The managed command is the reliable path. A page-level Ctrl+Alt+Z shortcut depends on whether the current site allows the extension to see the key event.

  1. Open chrome://extensions/shortcuts.
  2. Assign or verify the YourStasis current-tab command.
  3. If it does not fire on Docs, Sheets, or another protected page, use the pinned icon or context menu.

Upgrade an unpacked Chrome extension

Chrome's Update button does not download a new release into an unpacked extension. YourStasis reads its public release manifest only when you click Check for update in Settings > Advanced > Version & upgrade.

  1. Download the current zip from the install page.
  2. Extract it over the same stable extension folder you already loaded in Chrome.
  3. Open chrome://extensions and click Reload on YourStasis.
  4. Open Settings and confirm the displayed version changed and your local settings remain.
Keep the same install identity: replacing files in the same unpacked folder and reloading normally preserves extension storage. Loading a separate copy can create another extension identity with a different local workspace.