Portable, with boundaries

Choose an export—or teach a workflow—by what you need to reuse.

A readable conversation, a diagnostic trace, a Settings backup, and a reusable workflow are different artifacts. The safest choice is the narrowest one that fits your goal; when you already know the steps, Teacher mode can learn them from one manual demonstration.

Which export or workflow path should I use?

GoalCommandResult
Save the visible conversation/exportA readable Markdown transcript.
Debug a recorded agent run/export --tracesMarkdown with model responses, tool calls, arguments, and results.
Back up or move Settings/export --configA webbrain-config/1 JSON snapshot.
Learn a workflow by doing it once/teach --start <name>A value-free saved workflow compiled from your manual demonstration.
Move one reusable automation/workflow --export <id>A sanitized webbrain-workflow/1 JSON definition.
Configuration exports contain plaintext secrets

A Settings snapshot can include provider API keys, profile data, user memory, custom skills, and permission choices. Store it like a password backup; do not attach it to a public issue.

Conversation and trace Markdown

/export captures the messages currently shown in the side panel and records the exporting WebBrain version. It is designed for reading, not for importing back into WebBrain.

/export --traces uses locally recorded traces for the current conversation. It can include prompts, model output, URLs, tool arguments, and tool results. Screenshots are omitted from this Markdown file. If tracing was off when a turn ran, that turn cannot be reconstructed later.

Sharing a bug report?

Start with the conversation export. Use the trace export only when tool-level detail is needed, and review either file for personal data first.

Back up Settings

  1. Enter /export --config.
  2. Store the downloaded webbrain-config-….json securely.
  3. Restore it with /import --file, or paste its JSON after /import.

The snapshot includes portable Settings values. It does not include conversations, traces, schedules, usage counters, accumulated spend, or device-bound Cloud Sync sessions and device IDs.

The schema value identifies compatibility. WebBrain currently exports and accepts webbrain-config/1.

Learn by demonstration

Teach WebBrain a workflow by doing it once

Use Teacher mode when you know the browser steps and want to save them without first asking the agent to complete a traced run. The demonstration is tab-scoped and compiles into the same guarded webbrain-workflow/1 format as /workflow --save.

  1. Open the starting page. Use a regular http(s) page and stop any agent run that currently owns the tab.
  2. Start teaching. Enter /teach --start <name>. A purple WebBrain Teach indicator appears on the page.
  3. Perform the workflow manually. In that tab, make the trusted clicks, complete fields, change checkboxes or radio buttons, submit with Enter, and navigate exactly as the reusable flow should.
  4. Check progress when useful. Enter /teach to see the active workflow name and captured action count.
  5. Compile and save. Enter /teach --end. Then open /workflow to run, rename, export, or delete the learned workflow.
Typed values are never learned

The page capture code records a field’s semantic identity, not its contents. Each completed field becomes a runtime parameter, and WebBrain asks for the current value locally whenever the saved workflow runs.

Capture boundaries

  • Only trusted actions in the top-level page are captured; actions performed by WebBrain itself are excluded.
  • The session follows navigation in the same tab and records at most 100 normalized actions.
  • Teacher mode and automated agent runs cannot own the same tab at the same time. Finish with /teach --end before starting an agent task.
  • Unsupported or unsafe targets are skipped. The save result reports warnings and replay still requires an unambiguous semantic match.
  • /teach --end closes the temporary teaching session even when compilation cannot produce a workflow, so correct the page or demonstration and start again.

Create from a trace, then move a saved workflow

Teacher mode is the manual-demonstration path. If the agent already completed the task successfully with tracing enabled, save that execution instead:

  1. Enable tracing and complete the task successfully.
  2. Save it with /workflow --save <name>.
  3. Run /workflow to find its ID.
  4. Download it with /workflow --export <id>.
  5. On another WebBrain installation, use /workflow --import --file.

A portable workflow is not the original trace or teaching session. WebBrain removes old element references, CSS selectors, click coordinates, URL query strings and fragments, and typed field values. Typed values become prompts that are collected locally each time the workflow runs.

The file keeps semantic target descriptions and origin/path scopes so WebBrain can find the current element and fail closed when a match is ambiguous. Normal Act permissions, submission confirmation, and result verification still apply.

Import creates a copy

WebBrain assigns a fresh local ID and timestamps instead of overwriting an existing workflow. Portable workflow files are limited to 1 MiB.

Review before sharing

FileMinimum review
Conversation MarkdownMessages and system notices.
Trace Markdown or Trace-page JSONPrompts, URLs, arguments, results, and any embedded screenshots.
Settings JSONDo not share unless you have intentionally removed every secret and private value.
Workflow JSONName, source metadata, site origins/path families, target labels, and step intent.

For the complete field-level formats and compatibility rules, see the technical format reference.