@quanta-intellect/vessel-browser 0.1.53 → 0.1.56

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -100,6 +100,8 @@ Today, Vessel provides the browser shell, page visibility, and supervisory surfa
100
100
  - **Workflow Flow Tracking** — agents can declare a named multi-step workflow at runtime using `flow_start`; progress is tracked step-by-step with `flow_advance` and visible in the sidebar throughout execution
101
101
  - **Structured Page Visibility Context** — extraction can report in-viewport elements, obscured controls, active overlays, and dormant consent/modal UI
102
102
  - **Popup Recovery Tools** — agents can explicitly dismiss common popups, newsletter gates, and consent walls instead of brute-forcing generic clicks
103
+ - **Form Autofill Profiles** — save reusable personal or work profiles in Settings and fill common contact, address, and organization fields on the current page; Vessel matches fields using labels, names, placeholders, and autocomplete hints
104
+ - **Page Diff / "What Changed?"** — Vessel remembers the last snapshot of a page and surfaces a `Changed` badge in the address bar when the title, headings, or main content differ on a later visit; expand it to see a compact summary of what changed since the last snapshot
103
105
  - **Per-Tab Ad Blocking Controls** — tabs default to ad blocking on, but agents can selectively disable and re-enable blocking when a page misbehaves
104
106
  - **Domain Policy** — allowlist or blocklist domains globally in Settings; agents cannot navigate to blocked domains
105
107
  - **Agent Credential Vault** (Premium) — encrypted credential storage for agent-driven logins; credentials are filled directly into login forms via a "blind fill" pattern and are never sent to AI providers; user consent dialog before every use; TOTP 2FA support; domain-scoped access; append-only audit log
@@ -228,7 +230,7 @@ Vessel is designed to act as the browser runtime that your external agent harnes
228
230
 
229
231
  1. Launch Vessel
230
232
  2. Open Settings (`Ctrl+,`) to confirm MCP status, copy the endpoint, or change the MCP port
231
- 3. Optional: set an Obsidian vault path or session preferences
233
+ 3. Optional: set an Obsidian vault path, create autofill profiles, or adjust session preferences
232
234
  4. Start Hermes Agent or OpenClaw and point it at Vessel — the easiest way is `vessel-browser-mcp --stdio` as the MCP command (auth is resolved automatically), or connect directly to `http://127.0.0.1:<mcpPort>/mcp` with the bearer token from `~/.config/vessel/mcp-auth.json`
233
235
  5. Use the Supervisor panel in Vessel's sidebar to pause the agent, change approval mode, review pending approvals, checkpoint, or restore the browser session while the harness runs
234
236
  6. Use the Bookmarks panel to organize saved pages into folders and expose those bookmarks back to the agent over MCP
@@ -243,6 +245,8 @@ Notes:
243
245
  - For `llama-server`, use `--ctx-size 16384` minimum and `32768` recommended for reliable Vessel agent loops; lower values often fail once prompt, tool schema, and tool history accumulate
244
246
  - Approval policy is controlled live from the sidebar Supervisor panel rather than a separate global settings screen
245
247
  - Settings now show MCP runtime status, active endpoint, startup warnings, and allow changing the MCP port with an immediate server restart
248
+ - Settings also include reusable Form Autofill profiles for one-click filling of common contact and address forms on the active page
249
+ - The address bar can also show a `Changed` badge when Vessel detects that a previously visited page has meaningfully changed since the last saved snapshot
246
250
  - Agents can selectively disable ad blocking for a problematic tab, reload, retry the flow, and turn blocking back on later
247
251
  - Agents can persist authenticated state with named sessions, for example `github-logged-in`, and reload that state in later runs
248
252
  - The intended control plane is an external harness driving Vessel through MCP
@@ -488,8 +492,9 @@ src/
488
492
  │ ├── ai/ # Agent tools, query flow, and AI provider implementations
489
493
  │ ├── tabs/ # Tab + TabManager (WebContentsView)
490
494
  │ ├── agent/ # Agent runtime, checkpoints, supervision, flow tracking
491
- │ ├── content/ # Readability extraction, reader mode, screenshot
495
+ │ ├── content/ # Readability extraction, reader mode, screenshot, page snapshots/diff
492
496
  │ ├── config/ # Settings persistence
497
+ │ ├── autofill/ # Autofill profile persistence and form-field matching
493
498
  │ ├── ipc/ # IPC handler registry
494
499
  │ ├── vault/ # Agent Credential Vault (encrypted storage, consent, audit)
495
500
  │ ├── mcp/ # MCP server for external agent control