Cursor

Pathmode

Review what Cursor proposes.
Authorize what it builds.

Cursor drafts the feature from your request and repository. The product manager compares the proposal with the original request in Pathmode, corrects its interpretation, and authorizes the revision to implement.

Create your account

.cursorrules

# Project Context (auto-generated by Pathmode)

## Current Intent: Redesign Account Settings

Objective: Users can update preferences without drop-off

Outcomes: 3 testable conditions

Constraints: 3 non-negotiable rules

Evidence: 5 items from user research

## Constitution Rules

- All database access via server actions only

- Input validation with Zod on every API boundary

Connected team workflow · illustrative example

Review what the agent understood.

The request asks for a Cancel plan button. The proposal ends access immediately. The product manager settles the access timing before authorizing the build.

1. The agent proposes
Give Cursor the original ticket or brief. Ask it to draft the repository intent with assumptions labeled and attach the original request to the connected proposal.
2. The product manager corrects
Compare the request with “What the agent understood.” Record the decision to keep access active through the period the customer already paid for. Choosing a recommendation prepares a correction; it does not authorize implementation.
3. The revision returns for review
The repository agent applies the correction or reports why it cannot. The product manager inspects the applied change and the rest of the proposal, then authorizes that revision when it is right.
4. The engineer verifies the result
Cursor implements from the authorized intent.md and runs the applicable checks. Test cancellation with time left in the paid period and at period close; bring new limitations or contradictory findings back for review.

Connect the repository through repository setup, or invite the teammate who runs the coding agent. Local tools remain usable without an account; shared corrections and signed-in authorization require a connected workspace.

Follow the complete proposal review →

Context isn't judgment

Cursor can reason about the request and ask clarifying questions. Pathmode gives the product manager a shared review of the proposed behavior and a record of the revision they authorize.

Questions for your current workflow

?Where does the reviewer find the original request?
?Can the product manager inspect the proposed behaviors?
?How does a correction reach the repository agent?
?Which revision has permission to be implemented?
?How is the result checked against the agreement?

Cursor + Pathmode

Original request attached to the proposal
Behaviors available for inspection and correction
Corrections sent back to the repository agent
Signed-in authorization of the proposal revision
Implementation checks and findings tied to the intent

Two ways Pathmode powers Cursor

Use connected MCP tools for proposal review and corrections. Static exports remain useful snapshots of the agreed context; they do not carry live review state.

MCP Server

Repository intent and connected review state

Cursor's agent mode calls Pathmode tools directly. It reads your active intent, checks dependencies, and gets structured execution prompts — all in real time.

33 MCP tools for full context access
Dependency graph analysis built in
Agent stamps the intent on the PR; the merge grades the diff and marks it shipped
Applicable constitution rules included in agent context

.cursorrules Export

Static context, zero config

Generate a .cursorrules file from your workspace. Includes your strategy, constitution rules, and active intent — no MCP setup required.

One-click export from Pathmode workspace
Includes strategy, constraints, and active intent
Works in every Cursor mode
Commit to repo so the whole team gets context

Cursor names the intent on the pull request

The MCP tools teach the agent to name the intent on the branch or in the PR body, so the merge can grade the real diff and flip it to shipped. Any one of these references is enough:

pathmode:<uuid>intent/<uuid>Resolves PAT-<uuid>Closes PAT-<uuid>Fixes PAT-<uuid>

See the full story

.cursorrules that write themselves

Stop hand-maintaining rules files. Pathmode generates them from your workspace strategy, constitution rules, and active intent — with real user evidence baked in. Prefer Cursor's newer AGENTS.md format? The MCP server exports that too.

Intent-aware context

Your agent knows the objective, outcomes, constraints, and edge cases — not just the code.

Constitution rules included

Architectural constraints like "server actions only" or "Zod validation on every boundary" are baked into the rules file.

Evidence-backed decisions

The agent sees the friction reports, user quotes, and metrics that justify the work.

Always current

Re-export when the agreed intent changes. With MCP, ask the agent to read the current intent and review state before continuing.

Example auto-generated .cursorrules

markdown•.cursorrules

# Project Context (auto-generated by Pathmode)

## Workspace Strategy
Vision: Become the default way product teams communicate intent to AI agents.
Non-negotiables: Every feature must trace to user evidence. No spec ships without outcomes.

## Active Constitution Rules
- All database access via server actions only — no direct client queries
- Input validation with Zod on every API boundary
- Row-level security (RLS) enforced on all tables

## Current Intent: Redesign Account Settings
Objective: Users can update preferences without drop-off
Outcomes:
  - Settings save confirmation visible within 500ms
  - Password change completes in under 3 clicks
  - Drop-off rate on settings page below 30%
Constraints:
  - Must work on iOS Safari 15+
  - No full-page reloads on save
Evidence: 5 items — 3 friction reports, 1 user quote, 1 drop-off metric

33 tools. Full context.

Cursor's agent mode connects via Model Context Protocol. 10 tools work keyless on the intent.md in your repository; the rest read and write your Pathmode workspace.

Read

get_current_intent
Active intent with full spec
get_intent
Single intent by ID
list_intents
All intents, filter by status
search_intents
Keyword search across specs
query_evidence
Search evidence by type, severity, text

Write

create_intent
Create a new intent spec
update_intent
Update spec content
create_evidence
Log new evidence items
link_evidence
Link evidence to intents
log_implementation_note
Record technical decisions
record_implementation_finding
Write back what the build contradicted

Analyze

analyze_intent_graph
Critical path, bottlenecks, cycles
get_intent_relations
Dependency graph for one intent
get_workspace
Vision, principles, non-negotiables
get_constitution
Mandatory constraint rules
get_agent_prompt
Structured execution prompt

Act

verify_implementation
AI-grade work against the spec
update_intent_status
Mark verified; PR merges mark shipped
export_context
CLAUDE.md, .cursorrules, intent.md
intent_save
Save spec to intent.md (no API key)
intent_export
Export as agent config (no API key)
sync_context
Round-trip context into CLAUDE.md

What Cursor sees when it calls get_current_intent

json•intent response

{
  "objective": "Redesign account settings so users can update preferences without drop-off",
  "problemSeverity": "critical",
  "outcomes": [
    "Settings save confirmation visible within 500ms",
    "Password change completes in under 3 clicks",
    "Drop-off rate on settings page below 30%"
  ],
  "constraints": [
    "Must work on iOS Safari 15+",
    "No full-page reloads on save",
    "Respect existing RBAC permissions"
  ],
  "edgeCases": [
    { "scenario": "User loses connection mid-save", "expectedBehavior": "Draft persisted locally, retry on reconnect" },
    { "scenario": "Concurrent edits from two sessions", "expectedBehavior": "Last-write-wins with conflict toast" }
  ],
  "evidence": "5 items — 3 friction reports, 1 user quote, 1 drop-off metric"
}

Setup in under 2 minutes

Start without an account. Preflight runs on the intent.md in your repository, and nothing leaves your machine. Connect a workspace when a product manager should review what Cursor proposes.

Add Pathmode to Cursor

Paste this into ~/.cursor/mcp.json. No API key.

json•~/.cursor/mcp.json

{
  "mcpServers": {
    "pathmode": {
      "command": "npx",
      "args": ["-y", "@pathmode/mcp-server"]
    }
  }
}

Run preflight before it builds

Ask Cursor to check the repository's intent.md. check_intent_readiness grades six gates with no model call and names each blocker to fix.

Connect a workspace for review

With a key from Settings → API Keys, run npx @pathmode/mcp-server@latest setup pm_live_... and Cursor reads the proposal, open corrections, and authorization before implementing.

Also on the Cursor Directory with one-click install · Add --local to the args to stay keyless on a machine that already has a key.

Stop guessing what to build.
Review the proposal. Then build.

Give the product manager a review of what Cursor proposes to build.

Create your account

No credit card required · Free for solo builders

Review what Cursor proposes.
Authorize what it builds.

.cursorrules

# Project Context (auto-generated by Pathmode)

## Current Intent: Redesign Account Settings

Objective: Users can update preferences without drop-off

Outcomes: 3 testable conditions

Constraints: 3 non-negotiable rules

Evidence: 5 items from user research

## Constitution Rules

- All database access via server actions only

- Input validation with Zod on every API boundary

Review what the agent understood.

The request asks for a Cancel plan button. The proposal ends access immediately. The product manager settles the access timing before authorizing the build.

1. The agent proposes

Give Cursor the original ticket or brief. Ask it to draft the repository intent with assumptions labeled and attach the original request to the connected proposal.

2. The product manager corrects

Compare the request with “What the agent understood.” Record the decision to keep access active through the period the customer already paid for. Choosing a recommendation prepares a correction; it does not authorize implementation.

3. The revision returns for review

The repository agent applies the correction or reports why it cannot. The product manager inspects the applied change and the rest of the proposal, then authorizes that revision when it is right.

4. The engineer verifies the result

Cursor implements from the authorized intent.md and runs the applicable checks. Test cancellation with time left in the paid period and at period close; bring new limitations or contradictory findings back for review.

Follow the complete proposal review →

.cursorrules that write themselves

Intent-aware context

Your agent knows the objective, outcomes, constraints, and edge cases — not just the code.

Constitution rules included

Architectural constraints like "server actions only" or "Zod validation on every boundary" are baked into the rules file.

Evidence-backed decisions

The agent sees the friction reports, user quotes, and metrics that justify the work.

Always current

Re-export when the agreed intent changes. With MCP, ask the agent to read the current intent and review state before continuing.

# Project Context (auto-generated by Pathmode) ## Workspace Strategy Vision: Become the default way product teams communicate intent to AI agents. Non-negotiables: Every feature must trace to user evidence. No spec ships without outcomes. ## Active Constitution Rules - All database access via server actions only — no direct client queries - Input validation with Zod on every API boundary - Row-level security (RLS) enforced on all tables ## Current Intent: Redesign Account Settings Objective: Users can update preferences without drop-off Outcomes: - Settings save confirmation visible within 500ms - Password change completes in under 3 clicks - Drop-off rate on settings page below 30% Constraints: - Must work on iOS Safari 15+ - No full-page reloads on save Evidence: 5 items — 3 friction reports, 1 user quote, 1 drop-off metric

{ "objective": "Redesign account settings so users can update preferences without drop-off", "problemSeverity": "critical", "outcomes": [ "Settings save confirmation visible within 500ms", "Password change completes in under 3 clicks", "Drop-off rate on settings page below 30%" ], "constraints": [ "Must work on iOS Safari 15+", "No full-page reloads on save", "Respect existing RBAC permissions" ], "edgeCases": [ { "scenario": "User loses connection mid-save", "expectedBehavior": "Draft persisted locally, retry on reconnect" }, { "scenario": "Concurrent edits from two sessions", "expectedBehavior": "Last-write-wins with conflict toast" } ], "evidence": "5 items — 3 friction reports, 1 user quote, 1 drop-off metric" }

Review what Cursor proposes. Authorize what it builds.

Review what the agent understood.

1. The agent proposes

2. The product manager corrects

3. The revision returns for review

4. The engineer verifies the result

Context isn't judgment

Questions for your current workflow

Cursor + Pathmode

Two ways Pathmode powers Cursor

MCP Server

.cursorrules Export

Cursor names the intent on the pull request

.cursorrules that write themselves

Intent-aware context

Constitution rules included

Evidence-backed decisions

Always current

33 tools. Full context.

Read

Write

Analyze

Act

Setup in under 2 minutes

Add Pathmode to Cursor

Run preflight before it builds

Connect a workspace for review

Stop guessing what to build. Review the proposal. Then build.

Review what Cursor proposes. Authorize what it builds.

Review what the agent understood.

1. The agent proposes

2. The product manager corrects

3. The revision returns for review

4. The engineer verifies the result

Context isn't judgment

Questions for your current workflow

Cursor + Pathmode

Two ways Pathmode powers Cursor

MCP Server

.cursorrules Export

Cursor names the intent on the pull request

.cursorrules that write themselves

Intent-aware context

Constitution rules included

Evidence-backed decisions

Always current

33 tools. Full context.

Read

Write

Analyze

Act

Setup in under 2 minutes

Add Pathmode to Cursor

Run preflight before it builds

Connect a workspace for review

Stop guessing what to build. Review the proposal. Then build.

Review what Cursor proposes.
Authorize what it builds.

Stop guessing what to build.
Review the proposal. Then build.

Review what Cursor proposes.
Authorize what it builds.

Stop guessing what to build.
Review the proposal. Then build.