Capture from other apps and services

Every captured item records how it arrived. The source badge helps you filter the queue, understand its provenance, and decide whether an automation should be allowed to act on it.

Available channels depend on your platform and enabled integrations.

Quick Capture

Use the Capture dialog for text, links, files, and voice memos. Open it inside Lar with mod + Shift + N, from the command palette, or with the desktop global shortcut mod + Shift + Space.

Quick Capture is a direct user gesture. It can either add to Captures or create a typed Object immediately.

See Capture something quickly for the complete workflow.

Clipboard

Use Paste to Captures or mod + Shift + V to read and save the current clipboard contents once.

Lar has no clipboard watcher and does not continuously inspect clipboard changes. Check the clipboard before invoking the command if it may contain a password, token, recovery phrase, or one-time code.

Drag and drop

Open Captures and drop one or more files anywhere on the page. Lar stores them through the attachment path and adds a file capture to the queue.

File bytes are treated as opaque input during capture. Opening, parsing, importing, extracting text, or sending a file elsewhere is a later action.

On iOS or Android, use the system Share action and choose Lar. The native share target accepts only the URL, title, text, and files that you explicitly selected.

If the workspace is locked or the main app is closed, the mobile target encrypts the pending envelope to this device and Lar processes it after the workspace opens. The share target does not unlock the database and does not fetch or unfurl shared URLs.

Share-sheet content is still untrusted evidence: a shared caption, filename, or URL can be misleading. Review it before enrichment or conversion.

Deep links

Desktop automation tools and OS shortcuts can create an item with a lar://capture link. A deep link may launch Lar, wait for the workspace to unlock, and then add the capture.

Deep links are create-only, size-limited, rate-limited, and restricted to safe fields and http/https URLs. They never fetch a submitted URL during ingestion.

Any local application—and in some situations a web page—can attempt to invoke a custom URL scheme. Deep-link captures are therefore marked Unverified.

Automatic workflows are demoted to suggestions for unverified channels unless the workflow trigger explicitly names that channel. Do not use deep links to pass secrets.

Integrations

Connected services can deliver content directly to Objects or into Captures, depending on the integration’s Deliver to setting.

Telegram can poll messages sent to your bot, including supported voice and photo attachments. It defaults to Captures.
Readwise can sync highlights. Bulk highlight sync commonly uses direct delivery, but you can choose the destination exposed by the integration.
Kindle imports a local My Clippings.txt file and does not require network access.
Web Extension can send selected browser content to Captures after you approve the connection.

Open Settings → Integrations, choose the service, review its destination, and use Sync now for a user-initiated fetch. Enable automatic sync only if you want Lar to contact that service in the background.

Integration credentials are sealed through the platform’s secure key storage. Each token-backed integration is restricted to its declared service host.

Hosted capture channels

A configured hosted server may advertise account-bound Email, Telegram, or WhatsApp capture. Availability and entitlement depend on that server; a channel shown as planned is not active until the server explicitly offers it and you connect it.

Hosted capture necessarily involves the configured gateway receiving the message before the device does. Review that server’s retention and privacy policy before connecting a channel containing sensitive material.

System and notification events

Reminders, workflow reports, sharing events, sync events, and update notices appear under the notification bell. They are not capture Objects and do not trigger Capture workflows.

This separation keeps status updates from being converted into notes or starting capture automations.