Documentation

Get OpcClaw into your daily export motion—fast.

Getting started

OpcClaw Dashboard is the AI operating workbench for export teams: find buyers, follow up, catch timing signals, and keep outcomes inside a Project—not a generic chatbot, and not an agent marketplace.

Open Dashboard from the website

Use Get started or Log in. Signed-out users land on the login page (work email); signed-in users go straight to the home workspace. Google sign-in is coming soon; password reset is available.

Create your first project

After sign-in, use the project switcher to create a Project. A project maps to a product line, market, or outbound goal. Customers, signals, tasks, and files belong to the project—not to disposable chat threads.

Pick a real first path

① New task or an Agents scene card and describe the goal in natural language; ② open Prospecting / Outreach and start from your ICP; ③ later use Radar for “worth acting now” timing.

Workbench

Dashboard is a dense operating shell: brand, project switcher, primary nav, task list, and account area on the left; the main pane follows the nav. Collapse the sidebar when you need focus.

Chats and tasks are how work moves; prospects, touches, and market signals are what should persist. Clearing a chat must not wipe the project.

Suggested loop: define ICP → discover → qualify into Prospects → batch Touches → track delivery/opens/replies → let signals re-rank priority. Crawler ops consoles are not part of the customer workbench.

New task

Start an execution unit and describe the outcome in plain language.

Agents

Scene starters and session hub for concrete operating jobs.

Prospecting

Find accounts, run research, and enrich against your ICP.

Outreach

Manage the prospect list and follow-up progress (delivered / opened / replied).

Radar

Work actionable market signals—timing, not a second CRM shell.

Plugins & automations

Extend capabilities and run recurring operating jobs.

Agents

The Agents page is a task and scene entry: describe the goal in natural language (competitor analysis, follow-up, store ops), and the system runs capabilities inside a session. You finish outcomes—you do not pick internal agent roles.

Scene cards are starter entry points (procurement expert, international-station assistant, Vibe Selling, Shopify ops, coding assistant, and more). Clicks usually open a Project plus a drafted chat—not a marketplace install flow.

Tied to prospecting

Confirm goals and judgment rules in Prospecting, then start mining; or describe the ICP in empty-state natural language.

Tied to signals

New tasks can surface actionable hints from active Market Signals in the project—you see business copy, not internal taxonomy.

Marketing vs product

Homepage capability cards are narrative; real steps follow the sidebar and Project → task / Radar.

Market signals

Build a company list (Prospects) in a project, watch public changes, and turn evidence into actionable Market Signals. You process them in Radar by strength and timing. The product deliberately avoids unattributed blast send.

In the domain model, a Market Event is what happened and where; a Market Signal is what it means for this company and whether to act now. The sidebar product name is Radar (timing).

In the workbench

Open Radar for still-actionable signals; inspect summary, evidence, and prospect linkage. Outreach paths include email, LinkedIn, phone, WhatsApp, and more—usually drafts or ledger confirms, with human review before marking contacted.

When outreach is blocked

If the signal is not linked to a Prospect—or the subject is a competitor/non-customer—link/create a Prospect or convert first.

Two entrances

Prospecting / Outreach own the list and follow-up; Radar owns timing. They share one signal truth. Public collection runs in the platform backend—you do not configure crawler ops in Dashboard.

FAQ

Common questions from export teams getting started. If anything conflicts with live UI, trust Dashboard behavior.

How is the website different from the product? expand_more

Website is marketing and acquisition. Sign-in, projects, customers, and signals live on Dashboard.

Why create a Project first? expand_more

Customers, signals, tasks, and files belong to a Project—the long-lived operating context, not a temporary chat folder.

If I delete a chat, do I lose customer data? expand_more

No. Chat is interaction. Prospects, touches, and signals persist on the project.

Why can’t I auto-blast after a signal? expand_more

Human review by design: list → detail → choose a path → draft/confirm ledger—no unattributed sequences.

Are Radar and Market Signal the same? expand_more

The domain term is Market Signal; the sidebar product name is Radar (timing). Ops-wide intel consoles are not the customer Dashboard.

Prospecting vs Outreach? expand_more

Prospecting finds and enriches; Outreach runs list lifecycle and follow-up; Radar focuses on “act now” signals.

How do I sign in or reset password? expand_more

Dashboard supports work-email sign-in; Google is coming soon; forgot-password and reset flows are available. Website Login links out to Dashboard.