Web clipper

The independently released AuroraDocs Web Clipper saves pages and selections from the browser into AuroraDocs.

What It Captures

The current clipper supports:

• Clip page: creates a Bookmark object, sends it to Inbox, and stores the source URL.
• Clip selection: creates a Page object with the selected content quoted in the body, sends it to Inbox, and stores the source URL.

Selection clipping preserves basic formatting such as bold text, links, and lists. Relative links are saved against the original page URL.

Where Clips Go

Clips land in Inbox so you can process them later:

• tag them
• move them into a space or folder
• convert a capture into a task when appropriate
• link them into existing notes

See Inbox & capture for the triage flow.

Setup

Download the current ZIP from the Web Clipper releases page, then follow the install and update instructions in the public README. The clipper owns its version and release cadence independently from AuroraDocs.

The popup asks for:

• AuroraCloud API URL
• workspace ID
• AuroraDocs sign-in

The clipper handles MFA prompts and keeps a refreshable local extension session instead of requiring you to paste a short-lived bearer token.

E2EE workspaces

E2EE capture is enabled from a trusted AuroraDocs browser session with Enable encrypted capture. AuroraDocs shows an eight-character approval code; the extension never asks for a recovery phrase and receives only a scoped clipper credential plus the workspace's public capture key. The broad sign-in session is removed from the extension after pairing.

Captures are sealed in the extension before upload. AuroraCloud stores only the opaque envelope and a bounded pending receipt, so the clipper works while every AuroraDocs page is closed and does not require the desktop app. The Inbox item appears after a trusted AuroraDocs client unlocks the workspace. Lost responses can be retried with the same capture ID; key rotation reseals from an AES-GCM-encrypted local retry source without persisting capture plaintext.

Revoke the browser from Workspace encryption settings. A revoked or expired scoped credential fails closed and the popup returns to pairing.

Operator rollout

The server-side feature is disabled by default. Enable it only after applying the clipper capture migrations and setting AURORA_E2EE_CLIPPER_CAPTURE_ENABLED=1. The limits are configurable through the corresponding AURORA_E2EE_CLIPPER_MAX_* and AURORA_E2EE_CLIPPER_RETENTION_DAYS settings; keep the envelope and pending-count limits bounded and monitor the pending capture/quarantine paths before widening them. Do not use an aur_mcp_... token in the clipper. Those service credentials are for non-interactive MCP clients; the clipper uses an interactive AuroraDocs session.

Scope

The clipper is for AuroraCloud workspaces. Browser-only and Local folders workspaces do not expose a server API that a browser extension can safely write to from outside the app.