Common Workflows

Wato is organized around a few repeatable workflows: storing team memory, reviewing changes, controlling tool access, packaging agent context, publishing artifacts, inspecting activity, and keeping users in sync with your directory.

Manage team memory

Team memory is durable context that agents and humans can reuse across sessions. It is stored as Markdown pages inside team-scoped memory repositories.

Use this workflow to:

• Capture customer context, support learnings, product decisions, runbooks, and internal processes.
• Keep memory organized by team instead of putting everything in one shared workspace.
• Let agents retrieve useful context before future work.
• Update memory over time as the team learns.

In the UI, go to Teams → [Team] → Memory to browse the file tree, read pages, and make draft edits. Through MCP, agents can search, read, patch, or write memory files using mesh_search_memory, mesh_read_memory_file, mesh_patch_memory_file, and mesh_write_memory_file.

Review memory proposals

Memory changes are not trusted immediately. Wato keeps new or edited memory in a draft branch until it is submitted and approved.

Use this workflow to:

• Review what an agent or teammate wants to add.
• Compare proposed Markdown changes before they are merged.
• Prevent incorrect or low-quality notes from becoming trusted context.
• Keep a clear approval trail for important memory changes.

In the UI, go to Teams → [Team] → Memory → Review to see pending proposals, inspect diffs, check mergeability, and merge approved changes. Through MCP, agents can submit drafts with mesh_submit_memory_branch_for_review, list pending proposals with mesh_list_memory_proposals, and inspect a proposal with mesh_get_memory_proposal.

Final approval happens in the Wato review UI so a human reviewer can inspect the change before it becomes trusted memory.

Configure MCP access

Wato lets teams control which MCP connectors and tools agents can use. Access can be scoped by team, connector, and individual tool.

Use this workflow to:

• Approve connectors for specific teams.
• Allow useful tools while blocking risky or unnecessary ones.
• Give different teams different MCP access.
• Keep agent tool usage aligned with company policy.

In the UI, go to Admin → Connectors or Teams → [Team] → Connectors to approve connectors, configure accounts, sync tools, and manage access.

This matters because MCP tools can read data, write records, trigger actions, or access sensitive systems. Wato treats connector access as governed infrastructure instead of an all-or-nothing setup.

Package agent context

Wato can package team memory, rules, skills, plugins, and MCP setup information into portable agent context.

Use this workflow to:

• Give agents the right starting context.
• Avoid manually copying instructions into every AI client.
• Keep team rules and memory consistent across tools.
• Help different clients start from the same governed context.

In the UI, go to Teams → [Team] → Setup to manage the team's agent context package. A package can include:

• Team memory
• Team rules
• Published skills
• Plugin manifests
• MCP server information
• Setup instructions

Agents can use the package as their starting context, then call Wato MCP tools when they need deeper or fresher information.

Publish and manage artifacts

Artifacts are generated apps, files, previews, or other outputs that teams want to publish and share with controlled access.

Use this workflow to:

• Publish generated work as a versioned artifact.
• Share artifact URLs with the right audience.
• Control whether an artifact is public, organization-only, or restricted.
• Keep artifact access tied to Wato users, teams, groups, and policy.
• Let approved artifacts show live data from team-approved connectors without exposing connector credentials in the browser.

In the UI, go to Artifacts or Teams → [Team] → Artifacts to browse artifacts, publish versions, manage visibility, and review access settings. Artifacts can be served through Wato-controlled domains, with Wato enforcing access before private or restricted artifacts are opened.

Live artifacts

A live artifact is a hosted HTML artifact that can load fresh data through Wato at runtime. The artifact remains a normal web page, while Wato handles authentication, connector access, team policy, and traceability server-side.

Use live artifacts when you want dashboards, reports, or operational tools that refresh from approved systems instead of showing only static exported data.

Agents creating live artifacts should:

• Call wato_get_live_artifact_primitives before authoring the artifact.
• Use mesh_search_tools to confirm the exact connector tools available to the current team.
• Declare requested live calls in the HTML with data-wato-call and a stable data-wato-id.
• Use data-wato-defaults only for safe fixed defaults. Viewer-provided values should come from page controls such as forms, filters, or selected rows.
• Load the Wato dashboard SDK and initialize it with WatoDashboard.init().
• Call approved tools through the SDK instead of calling provider APIs or MCP endpoints directly from browser code.

When publishing a live artifact, choose the team whose approved connectors should power the live data. Wato uses that team's connector policy to create the live view. If the artifact requests a connector tool that is not available or needs extra review, Wato will not silently grant browser access.

For local development, bind the dashboard view before expecting live calls to work. Use wato_bind_dashboard_view with the generated HTML and the exact browser origins you plan to open, such as http://localhost:5173. Hosted artifacts do not need hardcoded organization or team values in the HTML; Wato resolves the live view from the artifact launch context.

Inspect traces

Wato records traces for MCP activity so teams can understand what agents did.

Use this workflow to answer questions like:

• Which MCP tool was called?
• Who called it?
• Which team context was used?
• What input was sent?
• Did the call succeed or fail?
• When did it happen?

In the UI, go to Traces or Teams → [Team] → Traces to inspect agent and MCP activity. Traces are useful for debugging, compliance, security review, usage monitoring, and understanding agent behavior.

Sync users and groups

Wato supports enterprise directory sync so users, groups, and team membership can stay aligned with your identity provider.

Use this workflow to:

• Import users from your company directory.
• Map directory groups to Wato teams.
• Keep team membership updated when people join, move, or leave.
• Reduce manual access management.

In the UI, go to Admin → Teams or the directory sync settings to map directory groups to Wato teams. Directory sync helps Wato reflect the company's source of truth for access, while still enforcing Wato-specific team membership, memory visibility, and MCP permissions.