smartmemory-capture
Public
Watch
1
0
Fork
You've already forked smartmemory-capture
 0
mirror of https://github.com/smartmemory/smartmemory-capture.git synced 2026-10-20 14:31:33 +00:00
1 branch 0 tags
Find a file
Code
Clone this repository
Exact

README.md

SmartMemory Capture

Version: 1.3.0

Capture surfaces that send web and mobile content into SmartMemory. Capture is a thin ingestion surface — it extracts content well at the edge and posts it to SmartMemory's /memory/ingest. All processing (extraction, entities, embeddings, the knowledge graph) and storage happen in SmartMemory core. There is no separate database or pipeline in this repo; captures appear in SmartMemory recall, not a local clip list.

Components

Path What it is
extension/ Chrome/Edge/Brave MV3 browser extension (the primary surface)
mobile-android/ Android share-sheet app (Capacitor)

How it connects (CAP-CONN-1)

Both surfaces speak one REST contract — POST /memory/ingest — implemented by either target. The extension classifies the target by endpoint host and applies the matching rule:

Target Endpoint Auth
Local (lite) http://127.0.0.1:9014 — a SmartMemory daemon on this machine No token (loopback is OS-authenticated)
Cloud (service) https://api.smartmemory.ai (or self-hosted, HTTPS) API token + Workspace ID required (sent as X-Workspace-Id — the service scopes every capture to a workspace)
  • Detect local SmartMemory probes GET /health on the lite daemon and verifies it identifies as SmartMemory. If found and no endpoint is configured, it auto-targets the daemon. If not found, the UI guides you to start it (smartmemory server) or use Cloud.
  • The same backend can run on a SQLite (lite) or FalkorDB backend — transparent to capture.

"Lite" is the local SmartMemory distribution (the smartmemory package's daemon), not a separate clip store. The browser extension needs an HTTP endpoint, so a fully embedded install with no running daemon is reachable only via SmartMemory's CLI/MCP, not this extension.

Browser extension

Install (unpacked)

  1. Open chrome://extensions/, enable Developer mode
  2. Load unpacked → select the extension/ folder
  3. Open the extension's Settings:
    • Click Detect local SmartMemory to use a local daemon, or
    • Enter your Cloud API URL + API token

Branding (v1.3.0)

The extension is named SmartMemory Capture everywhere (toolbar title, popup, settings, library, notifications). Icons (16/32/48/128) are rendered from the shipped logo (extension/icons/logo.svg, a copy of smart-memory-web/public/logo.svg) by extension/generate_icons.py (needs rsvg-convert). Colors, type, radii and motion are copied from the design system token file into extension/brand.css (source: smart-memory-design-system/colors_and_type.css). Every color in brand.css, the page stylesheets and the in-page sheet is a token from that file (alpha on a token color is allowed). The token file has no light theme, so the light roles reuse its gray scale and blue-600, and where a token cannot carry text at 4.5:1 the control uses a different token pairing instead (for example danger buttons use dark text on the destructive token). python3 extension/scripts/check_contrast.py checks the WCAG ratio of every text and background state pair in dark and light and the token mapping. It exits 1 on any failure. Dark is the default theme and light follows the system setting. System fonts only, no remote assets. After updating, reload the unpacked extension at chrome://extensions.

Capture modes

  • Full Page — page text content
  • Article — main article via Readability (great for news/blogs)
  • Selection — selected text (right-click → "Capture selection to SmartMemory")
  • Screenshot — visible-area snapshot

Captures carry rich provenance into SmartMemory context/properties: origin=browser:save (search-visible user content), source_url, title, capture_mode, plus author / OG / video metadata where available. Re-capturing the same URL dedupes (CORE-INGEST-DEDUPE-1).

Settings

  • Storage Mode — Local First (cache locally, sync in background) or Server Primary (sync first)
  • Local SmartMemory — detect/auto-target the lite daemon
  • API URL / API Token — Cloud target (token required) or a local daemon URL
  • Default tags, Duplicate URL policy, Export/Import

Privacy

Captures go only to the SmartMemory endpoint you configure (your local daemon or your account). Nothing is sent to any third party. The API token is stored device-locally and is never synced to Google's cloud.

Documentation

Full SmartMemory documentation: https://docs.smartmemory.ai