Skip to content →

Desktop ships a chat agent with MCP and builtin tools. Web has agent definitions and a workflows surface. Cloud jobs can run on Temporal when you pick the API target. The assistant is useful because it can see the vault, the browser, and the ledger — and because a background job can keep watching after you close the lid.

Oppulence / Agents and workflows

A copilot with tools, and jobs that run when you are not looking.

Chat without tools is a drafting window.

The assistant is useful because it can see the vault, the browser, and the ledger — and because a background job can keep watching after you close the lid.

Interactive on the desktop. Scheduled on either side.

Copilot chat is the default desktop agent. Pre-built meeting-prep and email-draft agents are opt-in. Background tasks declare an execution target: desktop or api. The API path uses Temporal.

MCP, not a private plugin format

Servers are configured in ~/.rowboat/config/mcp.json. The same protocol the rest of the toolchain already uses.

In-app browser

Desktop can read a page and match skills to a URL. That is a local capability, not a hosted crawler.

Questions

No. The self-hosted visual agent-builder in the legacy rowboat app is a different codebase. This page describes the desktop copilot, MCP, and the web agents/workflows surfaces.