Views in your coding tool
Coding tools that support the MCP Apps extension can show some WeHarness results as small views inside the conversation, instead of text only. Tools that do not support it get exactly the same results as text and structured data.
WeHarness has not yet checked the views in each coding tool. Whether your tool shows them depends on the tool and its version.
Which tools have a view
Section titled “Which tools have a view”| Tool | View |
|---|---|
plan_get (with plan_id) |
A plan: options with their checks, scope, budget, and Open in WeHarness to approve |
task_get |
A task: state, writer, steps and reproduced reports |
session_pr_get (and the pr prompt) |
A pull request: state, branches, checks, changes since the push, and Open in WeHarness to approve the push |
trace_get |
A trace: the steps as a waterfall, the failing step, where in the code it ran |
traces_search |
Recent traces, or failing calls by tool and error |
monitoring_get |
Monitoring: key numbers, a small chart, the busiest tools, the alerts |
eval_run_get (with compare_with) |
An evaluation run: regressed, fixed and unchanged cases |
application_get |
An application: traces, ingest, alerts, test sets, lessons |
catalog_get |
A catalog entry with its status label |
online_evaluators_get |
Online evaluators: today’s counts and the newest scores |
automations_get |
Automations: the rules, their state and the review list |
plan_validate |
A plan check: problems and each option’s eligibility |
context_search |
Code search: results citing path, lines and commit |
What every view does and does not do
Section titled “What every view does and does not do”- It never approves anything. A plan’s or a pull request’s view opens the WeHarness web app in your browser, where you approve.
- It shows the result it came with, and nothing else. It makes no network request of its own and holds no token or secret.
- Your application’s text stays text. Names, messages and code from your application or repository are shown as plain text, never as HTML, and length-limited. Right-to-left text is shown in its own direction, and hidden direction-override characters are removed.
- Links go to the web app only. A view opens links through your coding tool, and only to the WeHarness web app.
- It follows your tool’s look. It takes your tool’s light or dark theme and fits a narrow panel (320 to 480 pixels). Every control can be reached with the keyboard.
For tool builders
Section titled “For tool builders”The views are served as ui://weharness/<view>.html resources with the MIME type text/html;profile=mcp-app, and named in each tool’s _meta.ui.resourceUri. A client sees _meta.ui and the ui:// resources only when it says during initialization that it supports the extension (io.modelcontextprotocol/ui) with that MIME type. The page is self-contained: its scripts and styles are inline and pinned by hash in its own content security policy, which allows no outside connection. See the resources in the Tools and prompts reference.