Tutorials

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 choose BYOK or Local / Ollama 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, refresh the profile, and save a snapshot.
  3. Use automatic sync after the first save works.

Hosted BYOK

  1. Choose Bring your own model key in Setup.
  2. Use OpenRouter or OpenAI and paste the key into local settings.
  3. Run a small enrichment and keep the key local.

Local / Ollama

  1. 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

    Use Redo when pricing or context is weak. Add feedback so the stronger pass knows what to fix.

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 suffix are correct and that the provided URL is preserved.
  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 controls the table columns, output rules, research depth, and document categorization.

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.

Connected path: Google export

  1. Connect Google only when you want direct export.
  2. Choose an existing Sheet, create a new Sheet, or create a new Google Doc.
  3. Confirm selected rows, headers, and the active prompt columns before sending.

Integration path: JSON or NDJSON

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

Sync an account across surfaces

Snapshots contain sanitized settings, prompts, workspace rows, usage, logs, copy/export state, and provider-key status. Raw provider keys and sessions stay local.

  1. Save a snapshot manually after your first successful enrichment.
  2. On another surface, sign in and load the snapshot.
  3. Choose Merge account history to preserve local rows, Replace local history to use the account snapshot, 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 Settings > Integrations. Every push target is opt-in and off until you arm it.

Push to API

  1. Open Settings > 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; the versioned integration_export_v1 envelope is POSTed with a deterministic idempotency key.

ApplicationAgent adapter

  1. Enable the ApplicationAgent adapter in Settings > 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 fires once to whichever of Push to API, managed webhooks, or ApplicationAgent are armed.
  3. All auto-push switches default off until you enable them.
Keys stay sealed: endpoint credentials are excluded from account snapshots and travel only inside the encrypted secrets bundle.

Run local / Ollama on Windows

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 GitHub Release into an unpacked extension. YourStasis reads its public release manifest only when you click Check for update in Settings > Version & upgrade.

  1. Download the versioned zip from the validated GitHub Release link.
  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.