Context-Aware
Web Toolbox

See it, log it

Auto-run "Save as movie / book / game (SiYuan)" on Douban book / movie / game pages — browse and it's in your library, with no clicks at all; turn on "ask before running" if you'd rather confirm before writing.

Expand, then clip

One action chains "Click 'Expand full text' → Wait for the element → Copy page clip"; works for collapsed comments and lazily loaded long articles.

Select and search

Pick the site's search box and have Fill input use the selection — select a phrase and click once to fill it in (React-controlled search boxes work too).

Polish while you type

Put the caret in any site's input box, press Cmd/Ctrl+Shift+K (same key in the userscript; the right-click menu is extension-only), and act on the text you just wrote — Polish into Chinese / translate into Chinese / translate into English ship out of the box. The result replaces the text in that very box, caret parked at the end, and a bad pass is undone with Cmd/Ctrl+Z; while the model works, the palette leaves a "Running…" line in place.

Archive element screenshots

Open a report / dashboard page and capture a chosen area as PNG; you can also pick several blocks at once to export them one by one, or stitch them vertically into one long image. Pick the selector right on the page.

Then do: action chains

An action can carry a series of follow-up steps: after the main step succeeds they run in order. Example: save an Orca Note bookmark, then write a row to a SiYuan database (one click, both libraries populated); after saving, copy "《Title》 Link" to the clipboard. A step can also be set to "wait for my confirmation" — it doesn't run automatically, but waits for your click on the result surface (say, read the AI translation first, then decide whether to save it to notes).

Steps are a list: the first row is the main step, and the whole chain can be moved up and down (including swapping the main step further back — {{step.*}} cross-references inside the chain are rewritten to follow).

The built-in "Translate" ships with two such next steps: share card (original + translation) and post to X (translation + link).

Automation: click buttons / fill inputs

Actions can be set to "auto-run when the matching page opens" (unless the site is set to "Quiet" or "Off"), and chains can click buttons, fill inputs, and wait for elements; pick the selector right on the page. You can also capture any element as an image, and stitch several into one long image. Off by default, enabled per action.

Per-site control

Don't want a dashboard, bank, or intranet page touched? Click "This site" at the top of the orb panel to turn it off right there, or press and hold to pick a tier: Dock only / Selection only / Quiet (no auto-run, no suggestions) / Off (no UI mounted, and not counted in your browsing footprint). Scope can be "this site incl. subdomains / this page only"; resume from the extension icon (userscript: the script-manager menu), and manage the list under Studio "Preferences → Where it shows up".

AI extraction (optional)

Connect your own OpenAI-compatible model (DeepSeek / OpenRouter / SiliconFlow / local Ollama all work). The prompt is the config: hand {{content}} to the model and it produces summaries / copy / keywords, used in any action just like ordinary variables. Nothing depends on AI unless you turn it on — and translation still works, because it runs on the browser's built-in on-device translation.

AI config assistant

Not sure which action to set up? Describe what you want in one sentence (e.g. "clip this kind of page's article ad-free" or "build an Orca Note mode with bookmark, excerpt and task actions") and let AI draft a config — a single action, a batch of actions (with follow-up steps), or a whole mode, with shipped recipes as the parameter baseline. Nothing changes until you confirm; landing and auto-run are confirmed in the preview (auto-run is off by default and states its consequence when ticked); preview it, then click "Apply" (one-step undo). It reuses the model connection you configured. You can also flip it around — click "See what you can do on this page" and AI suggests several candidate actions for this kind of page.

Into your own notes

Orca Note (MCP) and SiYuan (kernel API): three targets — database / document & daily note / document database — with missing columns created automatically, duplicate checks before saving, and images localized into the notes asset library. You fill in the connection; it talks straight to your service.

Save to local files

Clips, share cards, and articles can all be saved as local files (Markdown / text / images). Paths support variables and subfolders — e.g. Shunshou/{{date:YYYY-MM-DD}}/{{title}}.md, ready to drop into your Obsidian / SiYuan vault; names are auto-numbered on collision, and you can choose to overwrite. Files are only written to your own Downloads folder — your existing download history is never read or listed.

One-click save into Obsidian

With Obsidian installed, write a page clip straight into your vault — via an obsidian:// deep link handed to Obsidian, with no server in between; the path inside the vault supports subfolders (e.g. Shunshou/{{date:YYYY-MM-DD}}/{{title}}), collisions can append or overwrite, and by default the note doesn't pop open.

Action Market

Subscribe to the official catalog and install action packs others have made by tag or search; dependencies and conflicts are reported, and packs can be checked for updates or uninstalled. Action packs are pure data (actions / extraction rules / prompts) with no code or secrets.

Command palette: use a sentence directly

Press Ctrl/⌘ + Shift + K to open the command palette — type a few letters to filter actions, then Enter to run; what you type can also be used directly: the palette's "Use this text…" section lists actions that reference {{input}}, and a shipped "Save a note" action stores one sentence straight into Orca Note / SiYuan.

Config is data

Modes / scenes / actions / variable groups are all visual config: undo a wrong change with ⌘Z, import, export, and share. A field source can be a selector / "label:value" / meta / JSON-LD / URL regex / selection / template / try in order, and you can add transform chains; one field can read differently per site, and "Try" tells you which source is in play. Built-in variables include full-page text / clip / table / clipboard / run-time pick. Templates can also chain transforms on variables: {{title|trim|slice(0,20)}} (trim, then cut to 20 characters).

Data page: backup and share

Import / export / backup in one place: export a scene as an action pack to share with friends, export your whole config as a backup or to move machines, and restore from a backup (secrets live in separate storage and are not included). Article rules can be exported as their own rule pack. A single action can be shared on its own too ("Share…" on node / group rows), and your own GitHub Gist can serve as cross-device config sync — secrets and per-device settings such as the orb position stay put.

Local scripts (advanced)

If you write JS, you can write a short extraction script for a site, with { url, title, selection, document } as input. Stored only on your machine, not in the config and not included in export / sharing; off by default — turn on "Allow User Scripts" on the extension's details page.