Web app and deep links
Use web links in results to open exact Dreamstate objects in the app.
The web app is where you inspect and work with the objects in a Dreamstate workspace. Use it to review Context, rows, drafts, messages, runs, and settings with the people who share the workspace. It is also the practical companion to Architect, because a state-bearing agent result can link back to the exact app object it created or read.
The app does not create a different data model from the CLI, MCP, or REST. Those doors use the same contract and workspace boundary. Start here when you want to see the output, then use What is Dreamstate when you want an agent or script to repeat an inspected workflow.
Find the screen that owns the work
The sidebar groups each object by the job it owns. Home is the workspace starting point. Inbox is for an existing conversation, while Sequences is for net-new outreach cadence and enrollment. Workbooks contain working row sets and their sourcing or enrichment work. Context contains the knowledge an agent should read before it writes, sources, or plans.
| Sidebar label | Path | Use it for |
|---|---|---|
| Home | /dashboard/workspace | Workspace home and starting point. |
| Inbox | /dashboard/unibox | All inboxes and My inbox views for existing conversations. |
| Tasks | /dashboard/tasks | Assigned work, queues, due dates, and completion. |
| Calendar | /dashboard/calendar | Social post scheduling and publishing work. |
| Workbooks | /dashboard/workbooks | Workbooks, worksheets, row sources, columns, and cells. |
| Context | /dashboard/context | Revisioned workspace knowledge documents. |
| Sequences | /dashboard/automations/sequences | Outreach sequences, steps, and enrollment state. |
| Workflows | /dashboard/automations/workflows | Automation graphs, triggers, and workflow runs. |
| Settings | /dashboard/settings | Integrations, mailboxes, members, roles, and workspace settings. |
Analytics has Outreach, Social, AI Visibility, and Credits views under the dashboard analytics route. Records use the records route family. Agency workspaces use /agency. The Architect surface opens in an in-app drawer rather than a separate sidebar destination.
Inspect saved state, not a copy
A state-bearing response can include web_url. That URL points to the exact object in the web app, such as a saved workbook, workflow, draft, or run. The JSON identifier remains the source of truth, but the URL provides a direct handoff from an agent conversation to the screen where a person can read the fields, result, and history.
Use that handoff after any meaningful change. For a workbook, inspect the worksheet's row source, columns, and score. For a workflow, inspect the graph and its run history. For an Inbox action, inspect the existing thread rather than treating outreach and a reply as interchangeable. For a social outcome, inspect the saved draft or calendar record before deciding whether a separate publish action is appropriate.
Open the saved worksheet from this result and summarize the row source, evidence column, score, and run state.A link is not evidence that the requested work succeeded. Read the status and output on the linked screen. If the row set is empty, the workflow failed, or the saved object is not the intended one, use the run record and error details to correct the input or configuration before moving to a live effect.
Use the app for shared review
Dreamstate keeps shared workspace work visible. Context documents are revisioned and attributed to the member and client that wrote them. Workbooks put a row source, columns, cell state, and score in one place. Tasks own assigned work, due dates, delegation, saved views, and closing completed assignments. These screens let a team see the durable result of an agent turn instead of relying on a transcript.
Use Settings for workspace-level administration, including members, roles, integrations, reports, mailboxes, do-not-contact rules, outreach settings, playbooks, and workspace settings. Reply playbooks live at /dashboard/settings/playbooks. A provider connection or mailbox can block a send or a provider-backed run, but it does not block drafting a sequence, building a workbook, or saving other work.
Treat these UI labels as the ownership map. A saved CRM record belongs in Records, while a working sourcing list belongs in Workbooks. A reply belongs in Inbox, while a cadence belongs in Sequences. Choosing the correct screen makes it easier to check the correct state and avoids applying a change to a nearby but different object.
Use Calendar for social scheduling, and use Analytics for the reports that describe outreach, social, AI visibility, or credits. These views expose the workspace result after the object has been created. They do not replace the object-specific screen when you need to inspect a row, a draft, a sender policy, or a run event.
When it goes wrong
If an agent cannot find a capability, have it search for the outcome and retrieve the returned contract. A run can fail with capability_not_fetched when the exact contract was not delivered in the current turn. It can fail with mode_required when a mutating request omits its mode. These are contract failures, not instructions to repeat a guessed request.
Use dry run when you need validation against the real workspace without business writes, provider spend, or outward action. A live paid call can return quote_required; inspect its estimate and rerun unchanged parameters with a max_credits ceiling. When a connected account is missing, save the build work, name the connection that is needed, and connect it before the affected step.
If a run has already started, inspect it through Runs before retrying. The run record, events, result state, and any receipt show what Dreamstate recorded. Do not assume that a cancellation removed an external effect. Check the saved object and returned state, then decide whether a corrective action is needed.
When a response includes a repair, follow the repair's stated next action. It can point to a missing schema, a legal field, an expected input shape, or a retry condition. That is more reliable than copying an earlier request into the app, because contracts and workspace state can differ between otherwise similar jobs.
Preserve the error code and trace information when you ask a teammate or Architect to diagnose the result.