MCP Path

Claim-Conflict

Claim-Conflict is a public reference for tabs, active targets, and claim state. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.

Catalog path

Reference page for a documented MCP capability path.

Type: MCP path
Family: Tab Management & Claims
Effect: changes state
Status: Reference
Path: 2.8

Purpose

What this entry explains

What it does

This reference explains Claim-Conflict for tabs, active targets, and claim state. It is kept as a named reference so agents can cite the flow without inventing a tool name.

Use when

Use this entry when an agent needs to carry out the bounded step "Claim-Conflict" for tabs, active targets, and claim state.
Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
Use it before chaining follow-up tools so the next step is based on current evidence.

Reference Use

How agents should cite and apply this area

Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.

Signal, gate, behavior, boundary

Claim-Conflict describes a behavior for tabs, active targets, and claim state. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.

When agents cite it

An agent cites this path when it needs Claim-Conflict as context for a decision, block, target check, or follow-up tool choice.

Why no callable name

The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.

Signals and rule

Relevant response signals: claimHint. Safety axes: Browser state. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.

Family example

A task touches data, identity, or permissions in tabs, active targets, and claim state that may be used only with clear purpose.

The agent starts with nova.tab_new, reads the current response or reference, and only then chooses the concrete next tool.

nova.tab_new nova.tab_claim nova.set_active_tab

Sensitive values stay in current scope; they are not guessed, logged, or copied into other contexts.

Contract

Inputs and important response fields

This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.

Inputs

No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.

Response field	Explanation
`claimHint`	Response field named by the catalog source. Treat it as current evidence for the next decision.

Safety

Boundary before execution

Effect

Can change browser, page, or workflow state. The target and expected result must be clear before execution.

Agent rule

Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.

Human control

For humans, this entry names the browser or workflow state in tabs, active targets, and claim state that may change, so the action can be reviewed before and after execution.

Safety Axes

How this path can affect work

Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.

Browser state browser_state_change

Changes tab, navigation, focus, claim, scroll position, window state, or browser environment.

Confirm the target context visibly before execution and verify that the expected browser state was reached afterwards.