Issue trackers and Pathmode overlap more than they did a year ago, and it is worth naming the overlap before the difference.
The trackers draft now, not just track. Linear's project composer develops an idea with its agent before the project goes live, pulling context from the workspace and connected tools to sharpen the brief and build a plan, and Linear's Loops edit that plan as scope and dates move. Jira's Rovo drafts from workspace context. Asana's AI assistants summarize and propose work. So "the tracker has no upstream" is no longer true, and a reader who has used one of these composers will notice if a comparison says otherwise.
Pathmode is the product judgment layer around the tracker. Its primitive is the evidence-anchored IntentSpec: a structured artifact whose parts each point at the signal that justified them. Its agent drafts as well. The difference is where the decision lives, and what that makes possible. The repository gets the decision. Pathmode keeps the evidence and the authorization behind it.
Residence. Pathmode's intent is a file in the repository the coding agent builds from, versioned with the code and readable by any agent, as a file or over MCP. The tracker's brief lives in the tracker. Linear's Loops can now keep it in step with the project, but every trigger is activity in the tracker and none of them reads the code, which is why the brief and the codebase drift apart over the quarter after the issue closes.
Authorization of the exact revision. Because the intent is a file, a decision can be bound to one version of it. A person reviews the proposal from a link, without opening the repository, and sends corrections back to the agent that wrote it. When the result is right, they authorize that exact revision, and an agent working through Pathmode checks the authorization covers the current file before it builds. If the file changes afterwards, the earlier authorization no longer covers it, and Pathmode flags the revision as undecided.
Verification. When a pull request opens, Pathmode grades the diff against the intent and cites the code it relied on, flagging a dropped outcome or an unenforced constraint. Native code review reviews the code, and code intelligence explains the code. Neither measures the code against the brief that asked for it.
Anchoring, underneath all three. Every requirement in an IntentSpec is anchored to a quote, a metric, or an observation. Pulling context in to sharpen a brief informs the prose and then stops being addressable, so the reason cannot be interrogated later.
Open suggestions, a narrow point about the hosted editor. Linear shipped text attribution in July 2026: author indicators distinguish a colleague from the Agent from a Loop, agent edits highlight for review, and it persists through version history. Who typed a line is answerable there. In Pathmode's hosted editor, an agent-added claim arrives unresolved and stays that way until a person keeps it, edits it, or removes it. A label can be read or ignored. A state has to be cleared. Intents that live in the repository are revised through reviewed changes instead.
A quarter later. Code intelligence can tell you what the code does. The questions that come up after a project closes are different. Which version of the decision was authorized, and by whom? What evidence stands behind this requirement? Does the code that shipped still honor it? The brief holds the conclusion. It does not hold what stood behind each requirement, or whether the shipped code still honors it.
This shape holds across the category, with different amounts of drafting bolted on. Linear is the most aggressive about extending into AI-era execution, from the project composer through coding sessions to native diffs. Jira owns enterprise distribution and is adding Rovo across it. Asana sits in cross-functional work management. In all three the unit of work is a document that lives in the tracker, its requirements are not anchored to evidence, and nothing after the merge checks the code against what was decided.
They compose. Pathmode produces the intent and holds the result to it. The tracker schedules the work, runs the agents, and ships it. Pathmode's MCP server is a grounding source those agents can read from, so the drafting surface your team already likes works against an artifact that remembers.