Verification trail
#1
✅ Verified
content/docs/administration/concepts/agent-accounts.md:78
- [Pulumi Agent Skills](/docs/ai/concepts/agent-skills/)
framing: Link text "Pulumi Agent Skills" matches the target page's h1/title_tag "Pulumi Agent Skills".; evidence: The internal link target exists at content/docs/ai/concepts/agent-skills.md, with h1 "Pulumi Agent Skills", so the link text matches the page title.; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match — Link text "Pulumi Agent Skills" matches the target page's h1/title_tag "Pulumi Agent Skills".
pass1 · url · high confidence
#2
✅ Verified
content/docs/administration/concepts/agent-accounts.md:79
- [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/)
evidence: The link target is there: content/docs/ai/guides/set-up-mcp-server.md exists and renders at /docs/ai/guides/set-up-mcp-server/, with h1 "Pulumi Model Context Protocol server". That matches the anchor text "Pulumi MCP server".; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match
pass1 · url · high confidence
#3
✅ Verified
content/docs/administration/concepts/billing-managers.md:61
A billing manager has the ability to access and update billing information, and to view organization metrics, such as resource count and member count (but…
framing: This is a URL claim. The path resolves to an existing page whose subject matches the anchor text. The billing-manager permission is backed only by this…; evidence: The link target exists at content/docs/ai/concepts/neo/usage-limits.md, and the page covers what the link text says: "Members with the **Admin** or **Billing Manager** role can view and change Neo usage limits" and "A Neo usage limit…; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
framing: exact-match — This is a URL claim. The path resolves to an existing page whose subject matches the anchor text. The billing-manager permission is backed only by this same-site docs page, not by product source.
pass1 · url · high confidence
#4
✅ Verified
content/docs/administration/get-started/choose-edition.md:80
Both billing options include detailed usage insights through the Billing & usage page in your organization settings. Track IaC resources, deployment minutes…
evidence: The link target exists at content/docs/ai/concepts/neo/usage-limits.md and covers the linked topic: "A Neo usage limit caps what your organization spends on Neo in a monthly billing period." The page also confirms the limits are set…; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
framing: exact-match
pass1 · url · high confidence
#5
✅ Verified
content/docs/administration/self-hosting/components/api.md:252
| `AGENTS_BYOK` | Pulumi Neo requests to a [custom model provider](/docs/ai/concepts/neo/model-providers/). |
framing: Only the internal link was checked. The AGENTS_BYOK value itself was not checked against product source.; evidence: The link target exists as content/docs/ai/concepts/neo/model-providers.md, titled "Bring your own model provider". It says: "With bring your own key (BYOK), Pulumi Neo uses your organization's existing model provider account for…; source: repo:content/docs/ai/concepts/neo/model-providers.md
source: repo:content/docs/ai/concepts/neo/model-providers.md
framing: exact-match — Only the internal link was checked. The AGENTS_BYOK value itself was not checked against product source.
pass1 · url · high confidence
#6
✅ Verified
content/docs/ai/_index.md:3
The page links to /docs/ai/concepts/cli-for-agents/, /docs/iac/cli/direct-resource-operations/, /docs/ai/concepts/agent-skills/…
evidence: All six link targets exist in the repo: content/docs/ai/concepts/cli-for-agents.md ("title: CLI for agents"), content/docs/iac/cli/direct-resource-operations/_index.md, content/docs/ai/concepts/agent-skills.md…; source: repo:content/docs/ai/concepts/cli-for-agents.md; repo:content/docs/iac/cli/direct-resource-operations/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md; repo:content/what-is/mcp-for-infrastructure-as-code.md; repo:content/docs/administration/concepts/agent-accounts.md
source: repo:content/docs/ai/concepts/cli-for-agents.md; repo:content/docs/iac/cli/direct-resource-operations/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md; repo:content/what-is/mcp-for-infrastructure-as-code.md; repo:content/docs/administration/concepts/agent-accounts.md
framing: exact-match
pass1 · url · high confidence
#7
✅ Verified
content/docs/ai/_index.md:3
Neo is suited to long-running, governed infrastructure tasks, while a coding agent is suited to interactive development; the two can be used together.
framing: The page describes coding agents handing long-running work off to Neo and continuing their own work, and Neo's guardrails and approvals. The claim restates…; evidence: The cited Neo concept page says "Claude Code, Codex, Cursor, and other agents can hand long-running infrastructure work to Neo through the Pulumi MCP server or the Neo handoff skill, then keep working while Neo runs." It also says Neo…; source: repo:content/docs/ai/concepts/neo/_index.md L19-22, L77-80; intuition: This is product positioning, and the only support is another Pulumi docs page; no product source confirms it.
source: repo:content/docs/ai/concepts/neo/_index.md L19-22, L77-80
framing: entailed-narrower — The page describes coding agents handing long-running work off to Neo and continuing their own work, and Neo's guardrails and approvals. The claim restates this as a split: Neo for long-running, governed tasks and the coding agent for…
pass1 · url · medium confidence
#8
✅ Verified
content/docs/ai/_index.md:19
A page exists at /docs/ai/get-started/ for getting started with Infrastructure AI.
evidence: content/docs/ai/get-started/_index.md exists and renders at /docs/ai/get-started/ with "title_tag: Get started with Infrastructure AI".; source: repo:content/docs/ai/get-started/_index.md
source: repo:content/docs/ai/get-started/_index.md
framing: exact-match
pass1 · url · high confidence
#9
✅ Verified
content/docs/ai/_index.md:25
The Pulumi CLI provides a `pulumi do` command that performs one-shot resource operations (direct resource operations).
framing: The link target is /docs/iac/cli/direct-resource-operations/, which exists as content/docs/iac/cli/direct-resource-operations/_index.md.; evidence: The pulumi/pulumi source defines `NewDoCmd` in pkg/cmd/pulumi/do/do.go, and pkg/cmd/pulumi/pulumi.go registers it as a CLI command. Its subcommands handle resource create/upsert, read, and function calls. The docs reference page…; source: gh search code --repo pulumi/pulumi newDoCmd → pulumi/pulumi:pkg/cmd/pulumi/do/do.go, pkg/cmd/pulumi/pulumi.go
source: gh search code --repo pulumi/pulumi newDoCmd → pulumi/pulumi:pkg/cmd/pulumi/do/do.go, pkg/cmd/pulumi/pulumi.go
framing: The link target is /docs/iac/cli/direct-resource-operations/, which exists as content/docs/iac/cli/direct-resource-operations/_index.md.
pass1 · api-surface · high confidence
#12
✅ Verified
content/docs/ai/_index.md:34
link: /docs/ai/get-started/
evidence: The target page is at content/docs/ai/get-started/_index.md, which has the title "Get started" and h1 "Get started with Infrastructure AI", so /docs/ai/get-started/ resolves.; source: repo:content/docs/ai/get-started/_index.md
source: repo:content/docs/ai/get-started/_index.md
pass1 · url · high confidence
#13
✅ Verified
content/docs/ai/_index.md:35
Users can connect the coding agent they already use to Pulumi, or enable Pulumi Neo for their organization and run their first task, per the Get started…
framing: The card text matches what the Get started page actually covers, so this is a navigation-consistency claim. I checked it against the target page, not against…; evidence: The claim restates a navigation card on the page, and the linked Get started page has both paths: "## Use your own agent" (Agent Skills, MCP server, CLI) and "## Use Pulumi Neo" with the link "[Get started with Pulumi…; source: repo:content/docs/ai/get-started/_index.md
source: repo:content/docs/ai/get-started/_index.md
framing: exact-match — The card text matches what the Get started page actually covers, so this is a navigation-consistency claim. I checked it against the target page, not against the product itself.
pass1 · feature · medium confidence
#14
✅ Verified
content/docs/ai/_index.md:37
The Concepts section explains how Agent Skills and the agent-friendly Pulumi CLI work, and how Neo handles tasks, permissions, pull requests, and…
evidence: content/docs/ai/concepts/_index.md exists, so /docs/ai/concepts/ resolves. It lists "Agent Skills", "CLI for agents", and Neo pages for "Tasks", "Permissions model", "Pull requests", and "Automations".; source: repo:content/docs/ai/concepts/_index.md
source: repo:content/docs/ai/concepts/_index.md
framing: exact-match
pass1 · url · high confidence
#15
✅ Verified
content/docs/ai/_index.md:42
link: /docs/ai/concepts/neo/
evidence: The internal link works. The page content/docs/ai/concepts/neo/_index.md exists in the repo with "title: Pulumi Neo" and sits in the AI concepts menu (parent: ai-concepts), so /docs/ai/concepts/neo/ resolves.; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
pass1 · url · high confidence
#16
✅ Verified
content/docs/ai/_index.md:43
Pulumi Neo investigates live infrastructure, reviews and proposes changes to IaC code, and takes on recurring maintenance.
framing: Card summary paraphrases the 'What Neo does' list on the Neo concept page.; evidence: The Neo concept page backs each part of the summary. It says Neo "reads your organization's live state in Pulumi Cloud" and answers questions by searching that state, "Proposes changes to your code" through pull requests, "Reviews your…; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: Card summary paraphrases the 'What Neo does' list on the Neo concept page.
pass1 · feature · medium confidence
#17
✅ Verified
content/docs/ai/_index.md:45
The Guides section contains step-by-step tasks such as connecting Claude Code, Cursor, and other agents to the Pulumi MCP server; link /docs/ai/guides/ must…
evidence: content/docs/ai/guides/_index.md exists (title "Guides"). It lists "[Set up the MCP server](/docs/ai/guides/set-up-mcp-server/): Connect Claude Code, Cursor, Windsurf, and other agents to Pulumi Cloud and the Pulumi Registry."; source: repo:content/docs/ai/guides/_index.md
source: repo:content/docs/ai/guides/_index.md
framing: exact-match
pass1 · url · high confidence
#18
✅ Verified
content/docs/ai/_index.md:49
An Integrations section exists at /docs/ai/integrations/ describing how to connect Neo to external MCP servers, cloud CLIs, and Slack.
framing: The page also covers GitHub. The claim leaves that out, but what it does say is still accurate.; evidence: content/docs/ai/integrations/_index.md exists (title "Integrations") and links to external-mcp-servers, cli-integrations ("calling out to cloud-provider CLIs"), and Slack: "Neo integrations connect the agent to MCP context sources, cloud…; source: repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/_index.md
framing: entailed-narrower — The page also covers GitHub. The claim leaves that out, but what it does say is still accurate.
pass1 · url · high confidence
#19
✅ Verified
content/docs/ai/_index.md:53
The Reference section documents the tools and prompts the Pulumi MCP server exposes, and the `pulumi neo` CLI command; link /docs/ai/reference/ must exist.
evidence: The page content/docs/ai/reference/_index.md exists. Its contents match the claim: "[MCP server tools](/docs/ai/reference/mcp-server-tools/): The tools and prompts the Pulumi MCP server exposes to your agent." and "[`pulumi neo` CLI…; source: repo:content/docs/ai/reference/_index.md; repo:content/docs/iac/cli/commands/pulumi_neo.md
source: repo:content/docs/ai/reference/_index.md; repo:content/docs/iac/cli/commands/pulumi_neo.md
framing: exact-match
pass1 · api-surface · high confidence
#20
✅ Verified
content/docs/ai/concepts/_index.md:14
The Get started page exists at /docs/ai/get-started/ and provides an end-to-end introduction to AI agents with Pulumi.
framing: The link target exists and is a starting-point page for AI agents with Pulumi. Calling it "end to end" is light editorial wording, and the page's…; evidence: content/docs/ai/get-started/_index.md exists, with title "Get started" and h1 "Get started with Infrastructure AI". Its meta_desc says: "Start using AI agents with Pulumi, either by connecting the coding agent you already use or by…; source: repo:content/docs/ai/get-started/_index.md
source: repo:content/docs/ai/get-started/_index.md
framing: exact-match — The link target exists and is a starting-point page for AI agents with Pulumi. Calling it "end to end" is light editorial wording, and the page's step-by-step paths reasonably support it.
pass1 · url · high confidence
#21
✅ Verified
content/docs/ai/concepts/_index.md:18
The Agent Skills concept page exists at /docs/ai/concepts/agent-skills/; Agent Skills are packaged Pulumi workflows that teach coding agents how to work with…
framing: The page calls them "knowledge packages that teach AI coding assistants domain-specific Pulumi workflows". The claim calls them "packaged Pulumi workflows…; evidence: content/docs/ai/concepts/agent-skills.md exists and is in the ai-concepts menu, so it publishes at /docs/ai/concepts/agent-skills/. It says: "Pulumi Agent Skills are knowledge packages that teach AI coding assistants domain-specific…; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match — The page calls them "knowledge packages that teach AI coding assistants domain-specific Pulumi workflows". The claim calls them "packaged Pulumi workflows that teach coding agents". The wording differs but the meaning is the same.
pass1 · url · high confidence
#22
✅ Verified
content/docs/ai/concepts/_index.md:23
The Pulumi Neo concept page exists at /docs/ai/concepts/neo/; Neo has user-configurable autonomy levels and can be used on multiple surfaces.
framing: The link target exists, and its content matches both summary points: configurable autonomy and several places to use Neo.; evidence: The target page exists at content/docs/ai/concepts/neo/_index.md, so /docs/ai/concepts/neo/ resolves. It says "Neo is one agent reachable from several places" and lists the console, CLI, editor, Slack, PRs and MCP. Under "How much…; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match — The link target exists, and its content matches both summary points: configurable autonomy and several places to use Neo.
pass1 · url · high confidence
#23
✅ Verified
content/docs/ai/concepts/_index.md:24
A task is the unit of work in Pulumi Neo, and Neo includes a Plan Mode, task modes, and approvals.
framing: The link description matches what the target page says: tasks are the unit of work, and the page covers Plan Mode, task modes and approvals. I checked this…; evidence: The linked page says "Tasks are Neo's primary unit of work." It also has sections titled "## Plan Mode", "## Task modes" (Review, Balanced, Auto) and "## Approvals and previews", which matches how the link is described.; source: repo:content/docs/ai/concepts/neo/tasks.md
source: repo:content/docs/ai/concepts/neo/tasks.md
framing: exact-match — The link description matches what the target page says: tasks are the unit of work, and the page covers Plan Mode, task modes and approvals. I checked this against the linked docs page only, not against product source.
pass1 · url · medium confidence
#25
✅ Verified
content/docs/ai/concepts/_index.md:25
Pulumi Neo acts as a different identity on each surface, and permission modes and approval modes constrain what Neo can do.
framing: Small wording gap: the page says "which identity it acts as on each surface," while the link text says "a different identity on each surface." On every…; evidence: The linked page exists and covers the described topics. Its meta_desc reads: "What Pulumi Neo can do, which identity it acts as on each surface, how permission and approval modes constrain it, and how to scope its access." It also has an…; source: repo:content/docs/ai/concepts/neo/permissions.md; intuition: "Acts as a different identity on each surface" could suggest Neo has separate identities of its own. The page says…
source: repo:content/docs/ai/concepts/neo/permissions.md
framing: exact-match — Small wording gap: the page says "which identity it acts as on each surface," while the link text says "a different identity on each surface." On every surface the page lists, Neo runs as a Pulumi user (the signed-in user, the user…
pass1 · url · high confidence
#26
✅ Verified
content/docs/ai/concepts/_index.md:27
Pulumi Neo supports interactive sessions in the terminal (Neo in the CLI) using the user's local project and credentials.
framing: The linked page describes an interactive terminal session that uses the local project and credentials, which is what the claim says.; evidence: The auto-generated CLI reference says: "Filesystem and shell tool calls from the agent run on this machine, in the working directory you select... If no prompt is provided, the TUI starts and waits for your first message." The linked…; source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from pulumi/pulumi); repo:content/docs/ai/concepts/neo/neo-in-the-cli.md
source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from pulumi/pulumi); repo:content/docs/ai/concepts/neo/neo-in-the-cli.md
framing: exact-match — The linked page describes an interactive terminal session that uses the local project and credentials, which is what the claim says.
pass1 · url · high confidence
#27
✅ Verified
content/docs/ai/concepts/_index.md:28
Pulumi Neo is available inside Zed, JetBrains IDEs, VS Code, and Cursor through the Agent Client Protocol.
framing: The linked page's meta_desc says the same thing as the claim. Product source confirms the generic ACP command. Editor support is protocol-level: Zed and…; evidence: The pulumi/pulumi changelog 3.254.0 says: "Add `pulumi neo acp` to run Neo as an Agent Client Protocol agent over stdio for ACP-capable editors". The linked page says "Use Pulumi Neo directly inside Zed, JetBrains IDEs, VS Code, and…; source: gh search code --owner pulumi "neo acp" (pulumi/pulumi:changelog/3.254.0.md, pkg/cmd/pulumi/neo/acp_adapter.go); repo:content/docs/ai/concepts/neo/neo-in-your-editor.md; intuition: The command is hidden (`newNeoACPCmd is the hidden pulumi neo acp subcommand`), so it may not show up in CLI…
source: gh search code --owner pulumi "neo acp" (pulumi/pulumi:changelog/3.254.0.md, pkg/cmd/pulumi/neo/acp_adapter.go); repo:content/docs/ai/concepts/neo/neo-in-your-editor.md
framing: exact-match — The linked page's meta_desc says the same thing as the claim. Product source confirms the generic ACP command. Editor support is protocol-level: Zed and JetBrains support ACP natively, while VS Code and Cursor use an extension.
pass1 · url · high confidence
#28
✅ Verified
content/docs/ai/concepts/_index.md:32
Pulumi Neo supports organization-wide custom instructions and per-repository `AGENTS.md` instructions.
framing: I didn't fetch the hinted page (/docs/ai/concepts/neo/instructions/). The Neo Settings page states the same two layers, org-wide Custom Instructions and…; evidence: (escalated from pass1) The Neo Settings docs say "Custom Instructions set organization-wide defaults that apply to every task" and that "Repository instructions (AGENTS.md) add project-specific conventions when Neo enters a repository".…; source: https://www.pulumi.com/docs/ai/neo/settings/ ; https://www.pulumi.com/blog/pulumi-neo-now-supports-agentsmd/
source: https://www.pulumi.com/docs/ai/neo/settings/ ; https://www.pulumi.com/blog/pulumi-neo-now-supports-agentsmd/
framing: exact-match — I didn't fetch the hinted page (/docs/ai/concepts/neo/instructions/). The Neo Settings page states the same two layers, org-wide Custom Instructions and per-repo AGENTS.md. Both sources are pulumi.com pages, so they corroborate the claim…
pass3 · url · medium confidence
#29
✅ Verified
content/docs/ai/concepts/_index.md:34
Pulumi Neo can run with the user's own model provider credentials.
framing: The source says "your organization's existing model provider account" and the claim says "the user's own model provider credentials". It's the same…; evidence: The linked page says: "With bring your own key (BYOK), Pulumi Neo uses your organization's existing model provider account for inference. Your provider bills you directly for that usage." It covers Anthropic, Azure Foundry, and custom…; source: repo:content/docs/ai/concepts/neo/model-providers.md
source: repo:content/docs/ai/concepts/neo/model-providers.md
framing: entailed-narrower — The source says "your organization's existing model provider account" and the claim says "the user's own model provider credentials". It's the same capability, but the source describes it at the organization level, where an admin sets it…
pass1 · url · medium confidence
#30
✅ Verified
content/docs/ai/concepts/_index.md:35
Pulumi Neo settings include access controls, a default task mode, and notifications.
framing: The page covers more topics than the three the claim names. The claim says "include," so naming only three is still correct.; evidence: The Neo Settings page has sections titled "Neo access" (the enable/disable toggles), "Task modes" ("Organization administrators can set the default task mode"), and "Notifications". It also covers instructions, model providers…; source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md (default-branch location; the PR appears to move it to /docs/ai/concepts/neo/settings/)
source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md (default-branch location; the PR appears to move it to /docs/ai/concepts/neo/settings/)
framing: entailed-narrower — The page covers more topics than the three the claim names. The claim says "include," so naming only three is still correct.
pass1 · url · high confidence
#31
✅ Verified
content/docs/ai/concepts/_index.md:36
Pulumi Neo supports spend limits for an organization and its members.
framing: Target page meta_desc: "Set dollar spend limits on Pulumi Neo for your organization and members". The link text says the same thing.; evidence: The linked page exists in the repo, and its description matches the link: "You set a limit for the whole organization, and optionally a separate limit for individual members." I didn't check this against product source, so this confirms…; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
framing: exact-match — Target page meta_desc: "Set dollar spend limits on Pulumi Neo for your organization and members". The link text says the same thing.
pass1 · url · medium confidence
#33
✅ Verified
content/docs/ai/concepts/agent-skills.md:237
- [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/) - give your agent live access to your Pulumi Cloud resources and the Registry
framing: The link text "live access to your Pulumi Cloud resources and the Registry" matches the page's meta_desc: "Connect ... AI agents to Pulumi Cloud and the…; evidence: The link target exists in the repo, and the page's description matches the link text: "an agent can list your stacks, search your resources, check policy violations, look up resource schemas in the Pulumi Registry".; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — The link text "live access to your Pulumi Cloud resources and the Registry" matches the page's meta_desc: "Connect ... AI agents to Pulumi Cloud and the Pulumi Registry".
pass1 · url · high confidence
#35
✅ Verified
content/docs/ai/concepts/cli-for-agents.md:16
AI agents like Claude Code, Codex, Cursor, and GitHub Copilot can write, preview, and deploy Pulumi infrastructure directly with the Pulumi CLI, with no…
evidence: This is a general capability claim. Claude Code, Codex, Cursor and GitHub Copilot can all run shell commands, and the Pulumi CLI is an ordinary shell tool (`pulumi preview`/`pulumi up`), so agents can drive it without a dedicated…; source: repo:content/docs/ai/concepts/cli-for-agents.md (context only); general knowledge of agent shell-execution capabilities; intuition: This is positioning copy rather than a precise feature claim. The phrase "no bespoke integration required" is true in…
source: repo:content/docs/ai/concepts/cli-for-agents.md (context only); general knowledge of agent shell-execution capabilities
pass1 · feature · low confidence
#36
✅ Verified
content/docs/ai/concepts/cli-for-agents.md:18
The Agent accounts page exists at /docs/administration/concepts/agent-accounts/ and describes ephemeral Pulumi Cloud accounts provisioned automatically for…
evidence: The page content/docs/administration/concepts/agent-accounts.md exists in the repo, so it is served at /docs/administration/concepts/agent-accounts/. It says: "When the Pulumi CLI detects it is running in an agent context and no Pulumi…; source: repo:content/docs/administration/concepts/agent-accounts.md
source: repo:content/docs/administration/concepts/agent-accounts.md
framing: exact-match
pass1 · url · high confidence
#37
✅ Verified
content/docs/ai/concepts/cli-for-agents.md:70
- [Agent Skills](/docs/ai/concepts/agent-skills/) — teach your agent proven Pulumi workflows it can apply on top of the CLI.
evidence: The link target exists as content/docs/ai/concepts/agent-skills.md, and its page describes "knowledge packages that teach AI coding assistants domain-specific Pulumi workflows". That matches the link's description.; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match
pass1 · url · high confidence
#38
✅ Verified
content/docs/ai/concepts/cli-for-agents.md:71
The Model Context Protocol page exists at /what-is/mcp-for-infrastructure-as-code/.
evidence: The repo has content/what-is/mcp-for-infrastructure-as-code.md (type: what-is). It is titled "MCP for Infrastructure as Code: What It Means for Pulumi Users" and has a "What is the Model Context Protocol?" section, so the…; source: repo:content/what-is/mcp-for-infrastructure-as-code.md
source: repo:content/what-is/mcp-for-infrastructure-as-code.md
pass1 · url · high confidence
#39
✅ Verified
content/docs/ai/concepts/cli-for-agents.md:72
Pulumi agent accounts are ephemeral Pulumi Cloud accounts provisioned automatically for agents.
evidence: pulumi/pulumi source backs this up. pkg/cmd/pulumi/agentauth/format.go says "Tell the user Pulumi created an ephemeral agent account," and the comment in pkg/backend/httpstate/backend.go says agent mode "creates a new agent account when…; source: gh search code --owner pulumi --repo pulumi/pulumi "agent account" (pkg/cmd/pulumi/agentauth/format.go, pkg/backend/httpstate/backend.go, changelog/3.261.0.md)
source: gh search code --owner pulumi --repo pulumi/pulumi "agent account" (pkg/cmd/pulumi/agentauth/format.go, pkg/backend/httpstate/backend.go, changelog/3.261.0.md)
pass1 · behavior · high confidence
#41
✅ Verified
content/docs/ai/concepts/neo/_index.md:31
Neo answers questions about your infrastructure by searching your real Pulumi state (e.g., which resources run an outdated provider, why a stack failed, what…
framing: The claim's link to Tasks only supports how Neo investigates. The specific question examples rest on the editorial get-started page, not on product source…; evidence: The linked Tasks page backs up the "how it investigates" pointer: "Investigates your environment by examining existing infrastructure, reading relevant code, checking dependencies". The sibling get-started page backs up the…; source: repo:content/docs/ai/concepts/neo/tasks.md; repo:content/docs/ai/get-started/neo.md L40, L59-68
source: repo:content/docs/ai/concepts/neo/tasks.md; repo:content/docs/ai/get-started/neo.md L40, L59-68
framing: entailed-narrower — The claim's link to Tasks only supports how Neo investigates. The specific question examples rest on the editorial get-started page, not on product source, because Neo is closed-source.
pass1 · url · medium confidence
#43
✅ Verified
content/docs/ai/concepts/neo/_index.md:35
Neo changes the IaC code rather than clicking in a console, and the usual way it hands changes back is a pull request describing the problem, the resources…
framing: The source says "Every change Neo proposes goes through a PR" and lists the PR contents; the claim's softer "usual way it hands changes back is a pull…; evidence: (escalated from pass1) The cited Neo pull-requests page says "Every change Neo proposes goes through a PR, ensuring: Human review of all changes", and that Neo's PRs include a "Description of what problem it solves", a "List of modified…; source: https://www.pulumi.com/docs/ai/pull-requests/
source: https://www.pulumi.com/docs/ai/pull-requests/
framing: entailed-narrower — The source says "Every change Neo proposes goes through a PR" and lists the PR contents; the claim's softer "usual way it hands changes back is a pull request" is a special case of that. Branch protection is inferred from "human…
pass3 · url · medium confidence
#44
✅ Verified
content/docs/ai/concepts/neo/_index.md:41
Neo can run `pulumi preview` to validate a change, surface policy violations, and show the resource diff.
framing: The source says policies are only checked "If the stack executing the preview is associated with Pulumi IaC policies". The claim's "can ... surface policy…; evidence: The link target exists (content/docs/ai/concepts/neo/previews/index.md) and supports all three parts of the claim. It says previews "Validate proposed changes", "Show impact analysis: Display what resources will be created, updated, or…; source: repo:content/docs/ai/concepts/neo/previews/index.md
source: repo:content/docs/ai/concepts/neo/previews/index.md
framing: entailed-narrower — The source says policies are only checked "If the stack executing the preview is associated with Pulumi IaC policies". The claim's "can ... surface policy violations" fits that condition. Confidence is medium because the only support is…
pass1 · url · medium confidence
#47
✅ Verified
content/docs/ai/concepts/neo/_index.md:48
Any Neo task can be turned into an automation that runs on a schedule (provider freshness checks, encryption and backup audits, activity digests); some…
framing: Source: "When a run produces changes, Neo opens a pull request"; claim adds that "some automations report findings", which is implied by "activity digests"…; evidence: The linked Automations page says: "Automations turn any Neo task into recurring work... When a run produces changes, Neo opens a pull request" and lists "Provider freshness checks, encryption audits, backup audits, and activity digests"…; source: repo:content/docs/ai/concepts/neo/automations.md
source: repo:content/docs/ai/concepts/neo/automations.md
framing: entailed-narrower — Source: "When a run produces changes, Neo opens a pull request"; claim adds that "some automations report findings", which is implied by "activity digests" but not stated. This is a same-site docs page, not product source.
pass1 · url · medium confidence
#48
✅ Verified
content/docs/ai/concepts/neo/_index.md:50
Some Neo automations only report what they found, while others open a pull request when there is work to do.
framing: This rests only on a sibling page on the same site. I couldn't check the Neo automation service source, which is likely in a private repo.; evidence: The sibling Automations page agrees: "When a run produces changes, Neo opens a pull request". It also lists "activity digests" and audits as templates, and those only report. The PR creation is conditional, which matches "when there's…; source: repo:content/docs/ai/concepts/neo/automations.md L18-L22, L34
source: repo:content/docs/ai/concepts/neo/automations.md L18-L22, L34
framing: This rests only on a sibling page on the same site. I couldn't check the Neo automation service source, which is likely in a private repo.
pass1 · behavior · medium confidence
#49
✅ Verified
content/docs/ai/concepts/neo/_index.md:53
Neo ships with the Pulumi Agent Skills catalog built in, giving it proven workflows for components, ESC, migrations, and provider upgrades.
framing: The link target says "ships with the Pulumi Agent Skills catalog built in", matching the claim word for word. "Proven workflows" is the doc's own wording for…; evidence: The linked Agent Skills page says: "Neo is an Agent Skills client. It ships with the Pulumi Agent Skills catalog built in (the same skills published in pulumi/agent-skills)." It also lists pulumi-component, pulumi-esc, the migration…; source: repo:content/docs/ai/concepts/agent-skills.md; gh search code --owner pulumi --repo pulumi/agent-skills "Neo"; intuition: Only Pulumi docs pages say the skills are "built in" to Neo. Neo's internals aren't public, so the agent-skills repo…
source: repo:content/docs/ai/concepts/agent-skills.md; gh search code --owner pulumi --repo pulumi/agent-skills "Neo"
framing: exact-match — The link target says "ships with the Pulumi Agent Skills catalog built in", matching the claim word for word. "Proven workflows" is the doc's own wording for the listed skills.
pass1 · url · medium confidence
#50
✅ Verified
content/docs/ai/concepts/neo/_index.md:62
A Neo get-started documentation page exists at /docs/ai/get-started/neo/, with a #read-only-mode anchor.
evidence: The file content/docs/ai/get-started/neo.md exists and has a "### Read-only mode" heading on line 38. Hugo turns that heading into the anchor #read-only-mode, so the link /docs/ai/get-started/neo/#read-only-mode resolves.; source: repo:content/docs/ai/get-started/neo.md#L38
source: repo:content/docs/ai/get-started/neo.md#L38
framing: exact-match
pass1 · url · high confidence
#51
✅ Verified
content/docs/ai/concepts/neo/_index.md:64
Running `pulumi neo` starts an interactive session that inherits the local setup: authenticated CLIs, environment variables, kubeconfigs, and the project…
framing: The specific items (authenticated CLIs, env vars, kubeconfigs) are inferred from local shell execution, not listed in the help text. The sibling page…; evidence: The CLI reference, auto-generated from pulumi/pulumi source (pkg/cmd/pulumi/neo exists on master), says `pulumi neo` "Creates a Pulumi Neo agent task in CLI tool execution mode... Filesystem and shell tool calls from the agent run on…; source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from pulumi/pulumi pkg/cmd/pulumi/neo); gh api repos/pulumi/pulumi/contents/pkg/cmd/pulumi/neo
source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from pulumi/pulumi pkg/cmd/pulumi/neo); gh api repos/pulumi/pulumi/contents/pkg/cmd/pulumi/neo
framing: The specific items (authenticated CLIs, env vars, kubeconfigs) are inferred from local shell execution, not listed in the help text. The sibling page neo-in-the-cli.md says the same thing.
pass1 · behavior · medium confidence
#52
✅ Verified
content/docs/ai/concepts/neo/_index.md:64
Running `pulumi neo` in the terminal starts an interactive session that inherits your local setup: authenticated CLIs, environment variables, kubeconfigs…
framing: The claim closely paraphrases what the linked page says. The 'inherits env/kubeconfigs' part rests on local execution and was not confirmed line-by-line in…; evidence: The linked page says: "Running locally means Neo inherits your setup: the CLIs you've authenticated, the environment variables and kubeconfigs you've configured, and the project you're editing." Product source backs this up…; source: repo:content/docs/ai/concepts/neo/neo-in-the-cli.md; gh api repos/pulumi/pulumi/contents/pkg/cmd/pulumi/neo/neo.go
source: repo:content/docs/ai/concepts/neo/neo-in-the-cli.md; gh api repos/pulumi/pulumi/contents/pkg/cmd/pulumi/neo/neo.go
framing: exact-match — The claim closely paraphrases what the linked page says. The 'inherits env/kubeconfigs' part rests on local execution and was not confirmed line-by-line in the code.
pass1 · url · medium confidence
#53
✅ Verified
content/docs/ai/concepts/neo/_index.md:68
Neo can be used in the agent panel of Zed, JetBrains IDEs, VS Code, and Cursor through the Agent Client Protocol.
framing: The ACP capability is confirmed in product source. The editor list is supported only by a sibling docs page plus editors' generic ACP support.; evidence: The pulumi/pulumi 3.254.0 changelog says: "Add `pulumi neo acp` to run Neo as an Agent Client Protocol agent over stdio for ACP-capable editors". The list of supported editors comes from a sibling docs page, which says: "Zed and…; source: pulumi/pulumi:changelog/3.254.0.md; pulumi/pulumi:pkg/cmd/pulumi/neo/acp_adapter.go; repo:content/docs/ai/neo/editors/_index.md
source: pulumi/pulumi:changelog/3.254.0.md; pulumi/pulumi:pkg/cmd/pulumi/neo/acp_adapter.go; repo:content/docs/ai/neo/editors/_index.md
framing: The ACP capability is confirmed in product source. The editor list is supported only by a sibling docs page plus editors' generic ACP support.
pass1 · feature · medium confidence
#54
✅ Verified
content/docs/ai/concepts/neo/_index.md:68
Neo can be used in an editor's agent panel in Zed, JetBrains IDEs, VS Code, and Cursor through the Agent Client Protocol.
framing: The claim matches the linked page's meta_desc almost word for word. The `pulumi neo acp` command is confirmed in product source. The list of editors depends…; evidence: The linked page says "Use Pulumi Neo directly inside Zed, JetBrains IDEs, VS Code, and Cursor through the Agent Client Protocol (ACP)". It says Zed and JetBrains support ACP natively, and VS Code and Cursor support it through the ACP…; source: repo:content/docs/ai/concepts/neo/neo-in-your-editor.md; gh search code --owner pulumi "neo acp" (pulumi/pulumi changelog/3.254.0.md, pkg/cmd/pulumi/neo/acp_adapter.go)
source: repo:content/docs/ai/concepts/neo/neo-in-your-editor.md; gh search code --owner pulumi "neo acp" (pulumi/pulumi changelog/3.254.0.md, pkg/cmd/pulumi/neo/acp_adapter.go)
framing: exact-match — The claim matches the linked page's meta_desc almost word for word. The `pulumi neo acp` command is confirmed in product source. The list of editors depends on which editors support ACP, which the pulumi source can't confirm.
pass1 · url · medium confidence
#57
✅ Verified
content/docs/ai/concepts/neo/_index.md:77
Claude Code, Codex, Cursor, and other AI agents can hand long-running infrastructure work to Neo through the Pulumi MCP server or the Neo handoff skill.
framing: The link only backs the MCP server route ("hand tasks to Pulumi Neo"). It doesn't back the handoff-skill route or the mention of Codex.; evidence: The link target exists at content/docs/ai/guides/set-up-mcp-server.md, and the page supports the MCP part of the claim: "an agent can list your stacks, search your resources... and hand tasks to [Pulumi Neo]". It also documents…; source: repo:content/docs/ai/guides/set-up-mcp-server.md L31, L163-165
source: repo:content/docs/ai/guides/set-up-mcp-server.md L31, L163-165
framing: entailed-narrower — The link only backs the MCP server route ("hand tasks to Pulumi Neo"). It doesn't back the handoff-skill route or the mention of Codex.
pass1 · url · medium confidence
#58
✅ Verified
content/docs/ai/concepts/neo/_index.md:80
The Neo handoff skill is part of the Pulumi Agent Skills documented at /docs/ai/concepts/agent-skills/.
framing: The link target documents the pulumi-neo-handoff skill under the Delegation plugin group. I couldn't check the upstream pulumi/agent-skills repo because…; evidence: The linked page exists (content/docs/ai/concepts/agent-skills.md) and its Delegation Plugin section lists the skill: "| pulumi-neo-handoff | Transfer the current work to a Pulumi Neo task with goal, repository pointers, and a compacted…; source: repo:content/docs/ai/concepts/agent-skills.md L79-85
source: repo:content/docs/ai/concepts/agent-skills.md L79-85
framing: exact-match — The link target documents the pulumi-neo-handoff skill under the Delegation plugin group. I couldn't check the upstream pulumi/agent-skills repo because GitHub returned a rate-limit error (HTTP 429).
pass1 · url · high confidence
#59
✅ Verified
content/docs/ai/concepts/neo/_index.md:82
Neo integrations connect it to services like Datadog, PagerDuty, Linear, and Atlassian to pull in context for a task.
framing: The claim names 4 of the 6 supported integrations as examples ("services like"), which the source's full list supports.; evidence: The linked page says: "Supported integrations are Atlassian (Jira and Confluence), Datadog, Honeycomb, Linear, PagerDuty, and Supabase. Each one becomes a set of tools Neo can call during a task." All four services named in the claim are…; source: repo:content/docs/ai/integrations/external-mcp-servers.md L26-28
source: repo:content/docs/ai/integrations/external-mcp-servers.md L26-28
framing: entailed-narrower — The claim names 4 of the 6 supported integrations as examples ("services like"), which the source's full list supports.
pass1 · url · medium confidence
#62
✅ Verified
content/docs/ai/concepts/neo/_index.md:92
Neo never has more access than the user does, only less.
evidence: The permissions reference page (content/docs/ai/concepts/neo/permissions.md L23) says: "No privilege escalation: Neo never gets more access than the user has, only the same or less." The get-started page L40 also says "Neo never gets…; source: repo:content/docs/ai/concepts/neo/permissions.md L18-30; repo:content/docs/ai/get-started/neo.md L36-40; intuition: "Only less" is a bit stronger than the canonical "only the same or less." The same page also says that Neo's VCS…
source: repo:content/docs/ai/concepts/neo/permissions.md L18-30; repo:content/docs/ai/get-started/neo.md L36-40
pass1 · behavior · medium confidence
#65
✅ Verified
content/docs/ai/concepts/neo/automations.md:18
The Neo pull requests documentation page exists at /docs/ai/concepts/neo/pull-requests/ (link target of the 'pull request' reference in the Automations page).
evidence: The repo has content/docs/ai/concepts/neo/pull-requests/index.md, a page bundle titled "Pull requests" ("Pull requests with Pulumi Neo"). It renders at /docs/ai/concepts/neo/pull-requests/, so the link in automations.md L18 points to a…; source: repo:content/docs/ai/concepts/neo/pull-requests/index.md
source: repo:content/docs/ai/concepts/neo/pull-requests/index.md
framing: exact-match
pass1 · url · high confidence
#69
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:5
Pulumi Neo code reviews analyze pull requests against what Pulumi Cloud knows about your running infrastructure and leave feedback in the pull request.
framing: The only support is another pulumi.com page (the launch blog post), not product source.; evidence: The official Neo code reviews launch post (PR #19728) says the same thing: "Neo code reviews analyze pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure, providing both high-level and…; source: repo:content/blog/neo-code-reviews/index.md; gh pr view 19728 -R pulumi/docs
source: repo:content/blog/neo-code-reviews/index.md; gh pr view 19728 -R pulumi/docs
framing: exact-match — The only support is another pulumi.com page (the launch blog post), not product source.
pass1 · feature · medium confidence
#72
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:25
Neo code reviews read the `pulumi preview` output and comment inline on the specific lines of the pull request that need attention.
framing: Blog says 'code-level feedback'; the doc says 'comment inline on the specific lines' — close, but the blog doesn't explicitly say inline.; evidence: The separate launch blog backs this up only indirectly. It says Neo has access to "the `pulumi preview` output" and gives "both high-level and code-level feedback". It never says "inline on specific lines", and Neo's backend is closed…; source: repo:content/blog/neo-code-reviews/index.md
source: repo:content/blog/neo-code-reviews/index.md
framing: Blog says 'code-level feedback'; the doc says 'comment inline on the specific lines' — close, but the blog doesn't explicitly say inline.
pass1 · behavior · low confidence
#75
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:33
Neo can be scoped to review pull requests only when someone mentions `@pulumi-neo`, instead of reviewing automatically.
evidence: The separate Neo code reviews launch blog says the same thing: "Neo can review every pull request automatically, or only when someone mentions `@pulumi-neo`." I couldn't find public product source for the setting (it's likely in the…; source: pulumi/docs:content/blog/neo-code-reviews/index.md (via gh search code --owner pulumi "@pulumi-neo")
source: pulumi/docs:content/blog/neo-code-reviews/index.md (via gh search code --owner pulumi "@pulumi-neo")
pass1 · feature · low confidence
#76
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:33
Neo can be asked to walk through what a change does, including resources that change in stacks the pull request does not modify directly.
framing: The claim has no cited source. The Pulumi blog wording matches the claim almost word for word ("PR doesn't touch directly" vs "pull request does not modify…; evidence: (escalated from pass1) Pulumi's separate launch post for Neo in GitHub says the same thing: "Reviewers can ask Neo to walk through what a proposed change does, including resources that change in stacks the PR doesn't touch directly."…; source: https://www.pulumi.com/blog/neo-github-slack/
source: https://www.pulumi.com/blog/neo-github-slack/
framing: The claim has no cited source. The Pulumi blog wording matches the claim almost word for word ("PR doesn't touch directly" vs "pull request does not modify directly").
pass3 · feature · medium confidence
#79
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:39
Neo code reviews are not available on Azure DevOps, GitLab, or Bitbucket, where pull request comments come from the version control integration rather than…
framing: The link only supports the part about pull request comments coming from the version control integration. The claim that Neo is GitHub-only is a product…; evidence: The linked page exists and backs up the pull request comment half: "The native integrations — GitHub, GitLab, Bitbucket, and Azure DevOps — all provide ... Pull request previews and comments. When a pull request is opened or updated…; source: repo:content/docs/integrations/version-control/_index.md
source: repo:content/docs/integrations/version-control/_index.md
framing: entailed-narrower — The link only supports the part about pull request comments coming from the version control integration. The claim that Neo is GitHub-only is a product assertion the linked page doesn't cover.
pass1 · url · medium confidence
#80
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:39
The Pulumi Neo get-started page has an 'enabling and disabling Neo' section at /docs/ai/get-started/neo/#enabling-and-disabling-neo.
evidence: content/docs/ai/get-started/neo.md line 18 has the heading "## Enabling and Disabling Neo". Hugo turns that into the anchor #enabling-and-disabling-neo, so the link resolves.; source: repo:content/docs/ai/get-started/neo.md#L18
source: repo:content/docs/ai/get-started/neo.md#L18
framing: exact-match
pass1 · url · high confidence
#81
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:44
Setup requires granting Pulumi access to your GitHub account by completing the individual OAuth flow under Settings > Version control in Pulumi Cloud.
framing: The sibling says individual access is required to *trigger* a code review. The claim calls it a setup step. That's consistent, but the sibling page also says…; evidence: The GitHub app page backs this up, including the linked anchor: "individual users can complete an OAuth flow under **Settings** > **Version control** to grant Pulumi access to their personal GitHub account... Triggering a Neo code review…; source: repo:content/docs/integrations/version-control/github-app.md L138-146; intuition: Automatic reviews (on every PR, opened by any author) needing each user's individual OAuth looks odd. It's worth…
source: repo:content/docs/integrations/version-control/github-app.md L138-146
framing: exact-match — The sibling says individual access is required to *trigger* a code review. The claim calls it a setup step. That's consistent, but the sibling page also says other Neo tasks don't need it.
pass1 · behavior · medium confidence
#82
✅ Verified
content/docs/ai/concepts/neo/code-reviews.md:46
The GitHub App documentation page has an 'individual user setup' section at /docs/integrations/version-control/github-app/#individual-user-setup.
evidence: github-app.md line 138 has the heading "### Individual user setup", which Hugo turns into the anchor #individual-user-setup. That section also says "Triggering a [Neo code review](/docs/ai/concepts/neo/code-reviews/) requires individual…; source: repo:content/docs/integrations/version-control/github-app.md#L138-L142
source: repo:content/docs/integrations/version-control/github-app.md#L138-L142
framing: exact-match
pass1 · cross-reference · high confidence
#91
✅ Verified
content/docs/ai/concepts/neo/instructions/index.md:49
The page references an image file custom-instructions.png showing the Custom Instructions configuration, which must exist alongside the page.
evidence: The image exists next to the page. Line 49 of the page embeds ``, and reading content/docs/ai/concepts/neo/instructions/custom-instructions.png from the repo returned a real…; source: repo:content/docs/ai/concepts/neo/instructions/custom-instructions.png; repo:content/docs/ai/concepts/neo/instructions/index.md#L49
source: repo:content/docs/ai/concepts/neo/instructions/custom-instructions.png; repo:content/docs/ai/concepts/neo/instructions/index.md#L49
pass1 · cross-reference · high confidence
#95
✅ Verified
content/docs/ai/concepts/neo/instructions/index.md:82
Pulumi Neo reads an `AGENTS.md` file placed in a repository when it enters the repository and follows the instructions it contains.
framing: The settings page is the pre-split copy of this content (pulumi/docs#22261 split instructions out of neo/settings). The independent corroboration comes from…; evidence: (escalated from pass1) The Neo AGENTS.md launch blog says: "When you point Neo at a repository, it reads any AGENTS.md file it finds and applies those instructions to its work." The older Neo Settings page, which this PR's page was split…; source: https://www.pulumi.com/blog/pulumi-neo-now-supports-agentsmd/; https://www.pulumi.com/docs/ai/neo/settings/
source: https://www.pulumi.com/blog/pulumi-neo-now-supports-agentsmd/; https://www.pulumi.com/docs/ai/neo/settings/
framing: The settings page is the pre-split copy of this content (pulumi/docs#22261 split instructions out of neo/settings). The independent corroboration comes from the launch blog. The settings page also notes Neo must clone the repo first…
pass3 · behavior · medium confidence
#99
✅ Verified
content/docs/ai/concepts/neo/model-providers.md:92
The Neo usage limits documentation page exists at /docs/ai/concepts/neo/usage-limits/ (linked as 'Manage Neo usage limits' from the Neo model providers…
evidence: content/docs/ai/concepts/neo/usage-limits.md exists in the repo (h1: "Neo usage limits", parent ai-concepts-neo), so it resolves at /docs/ai/concepts/neo/usage-limits/. model-providers.md L94 links to it as "[Manage Neo usage…; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
pass1 · url · high confidence
#102
✅ Verified
content/docs/ai/concepts/neo/neo-in-the-cli.md:17
Neo can also run directly in your editor, documented at /docs/ai/concepts/neo/neo-in-your-editor/ (link target must exist).
evidence: The target file exists at content/docs/ai/concepts/neo/neo-in-your-editor.md, so it resolves to /docs/ai/concepts/neo/neo-in-your-editor/. It says: "Neo can run directly inside your editor's agent panel."; source: repo:content/docs/ai/concepts/neo/neo-in-your-editor.md
source: repo:content/docs/ai/concepts/neo/neo-in-your-editor.md
framing: exact-match
pass1 · url · high confidence
#103
✅ Verified
content/docs/ai/concepts/neo/neo-in-the-cli.md:27
Neo permission modes are default and read-only, and they govern what Neo can change; the link target /docs/ai/concepts/neo/permissions/#permission-mode-and-app…
framing: The source_hint pointed to tasks/#task-modes, but the line under review links to permissions/#permission-mode-and-approval-mode, and that anchor exists.; evidence: The auto-generated CLI reference shows `--permission-mode string Permission mode for the agent: 'default' grants full role-based capabilities, 'read-only' blocks state-mutating operations`. The link target exists: permissions.md L73 has…; source: repo:content/docs/iac/cli/commands/pulumi_neo.md L31; repo:content/docs/ai/concepts/neo/permissions.md L73-79
source: repo:content/docs/iac/cli/commands/pulumi_neo.md L31; repo:content/docs/ai/concepts/neo/permissions.md L73-79
framing: exact-match — The source_hint pointed to tasks/#task-modes, but the line under review links to permissions/#permission-mode-and-approval-mode, and that anchor exists.
pass1 · url · high confidence
#108
✅ Verified
content/docs/ai/concepts/neo/neo-in-your-editor.md:16
Neo can run directly inside an editor's agent panel, letting users chat with Neo, review its plans, and watch its edits in the same window as their code…
evidence: pulumi/pulumi#23886 (merged, ships in v3.254.0) adds `pulumi neo acp`: "Run Neo as an ACP agent over stdio so ACP-capable editors (e.g. Zed) can drive it natively." It also says "File reads/writes route through the editor (unsaved…; source: gh pr view 23886 -R pulumi/pulumi
source: gh pr view 23886 -R pulumi/pulumi
pass1 · feature · high confidence
#109
✅ Verified
content/docs/ai/concepts/neo/neo-in-your-editor.md:18
Editors connect to Neo through the Agent Client Protocol (ACP), an open standard that editors also use to host agents like Claude Code and Gemini CLI.
framing: The claim links to agentclientprotocol.com but I didn't fetch it. The verdict rests only on Pulumi's own source for the Neo part.; evidence: pulumi/pulumi PR #23886, "Add `pulumi neo acp` Agent Client Protocol adapter", was merged on 2026-07-10, along with the supporting ACP package (#23884) and the PR that translates Neo events into ACP updates (#23885). That confirms…; source: gh pr list -R pulumi/pulumi --search "neo acp" --state all
source: gh pr list -R pulumi/pulumi --search "neo acp" --state all
framing: The claim links to agentclientprotocol.com but I didn't fetch it. The verdict rests only on Pulumi's own source for the Neo part.
pass1 · feature · medium confidence
#111
✅ Verified
content/docs/ai/concepts/neo/neo-in-your-editor.md:75
Neo's permission modes (default, read-only) and plan mode are exposed as session options in the editor's agent UI; permission modes govern what Neo can…
framing: The mode names and what each mode governs match the cited section. The claim that they are exposed as editor session options is not covered by the citation.; evidence: The cited anchor exists and lists "**Permission mode** | `default` ("Use my permissions") / `read-only` | *What Neo can change.*". It also says Plan Mode "makes Neo research and agree on a plan with you before it acts". I couldn't…; source: repo:content/docs/ai/concepts/neo/permissions.md L73-92
source: repo:content/docs/ai/concepts/neo/permissions.md L73-92
framing: exact-match — The mode names and what each mode governs match the cited section. The claim that they are exposed as editor session options is not covered by the citation.
pass1 · url · medium confidence
#112
✅ Verified
content/docs/ai/concepts/neo/neo-in-your-editor.md:78
- **[Plan mode](/docs/ai/concepts/neo/tasks/#plan-mode)** lets Neo research and agree on a plan with you before executing
framing: The link target exists, and the link's summary ("research and agree on a plan with you before executing") matches the target section's description.; evidence: The tasks.md page has a "## Plan Mode" heading, which generates the #plan-mode anchor. That section says: "Neo shifts into a dedicated research-and-planning phase where it investigates your environment in depth... iterates with you" and…; source: repo:content/docs/ai/concepts/neo/tasks.md#L33-L44
source: repo:content/docs/ai/concepts/neo/tasks.md#L33-L44
framing: exact-match — The link target exists, and the link's summary ("research and agree on a plan with you before executing") matches the target section's description.
pass1 · url · high confidence
#113
✅ Verified
content/docs/ai/concepts/neo/neo-in-your-editor.md:80
Neo tool call approvals surface in the editor's agent panel, in the same way as approvals for other agents run there.
framing: The source confirms that approvals are sent to the editor as ACP permission requests. The point that they are reviewed "the same way as other agents" comes…; evidence: The ACP adapter stack (pulumi/pulumi#23885/#23886, merged) sends Neo's UIApprovalRequest to the editor as an ACP permission request: "pumpAction is one ordered step the writer performs: emit a session/update notification, launch a…; source: gh pr diff 23885 -R pulumi/pulumi (pkg/cmd/pulumi/neo/acp_pumpqueue.go); gh pr view 23886 -R pulumi/pulumi
source: gh pr diff 23885 -R pulumi/pulumi (pkg/cmd/pulumi/neo/acp_pumpqueue.go); gh pr view 23886 -R pulumi/pulumi
framing: The source confirms that approvals are sent to the editor as ACP permission requests. The point that they are reviewed "the same way as other agents" comes from ACP being a shared standard, not from code that compares Neo with other agents.
pass1 · behavior · medium confidence
#119
✅ Verified
content/docs/ai/concepts/neo/permissions.md:42
Neo scheduled automations run as the user who scheduled the automation, with RBAC evaluated at execution time so changed permissions apply.
framing: The automations page says "runs with the RBAC permissions of the user who scheduled it, evaluated at execution time." The claim says it "runs as the user who…; evidence: The linked automations page says the same thing: "A scheduled task runs with the RBAC permissions of the user who scheduled it, evaluated at execution time. If that user's permissions change between scheduling and execution, the new…; source: repo:content/docs/ai/concepts/neo/automations.md#L44
source: repo:content/docs/ai/concepts/neo/automations.md#L44
framing: exact-match — The automations page says "runs with the RBAC permissions of the user who scheduled it, evaluated at execution time." The claim says it "runs as the user who scheduled the automation, with RBAC evaluated at execution time." Same meaning.
pass1 · url · medium confidence
#122
✅ Verified
content/docs/ai/concepts/neo/permissions.md:55
Neo proposes IaC code changes via pull requests (link /docs/ai/concepts/neo/pull-requests/) and runs `pulumi preview` / `pulumi up` gated by approval mode…
framing: The linked page backs the PR part. The approval-mode gating comes from a separate Neo page, tasks.md. The "no direct state edits" part is unconfirmed.; evidence: The linked page exists (content/docs/ai/concepts/neo/pull-requests/index.md) and says "Every change Neo proposes goes through a PR". tasks.md backs the approval gating: "Review mode (default): Neo requires approval before running `pulumi…; source: repo:content/docs/ai/concepts/neo/pull-requests/index.md; repo:content/docs/ai/concepts/neo/tasks.md L58-72
source: repo:content/docs/ai/concepts/neo/pull-requests/index.md; repo:content/docs/ai/concepts/neo/tasks.md L58-72
framing: entailed-narrower — The linked page backs the PR part. The approval-mode gating comes from a separate Neo page, tasks.md. The "no direct state edits" part is unconfirmed.
pass1 · url · medium confidence
#123
✅ Verified
content/docs/ai/concepts/neo/permissions.md:56
Neo can read any ESC environment the user can open, including decrypting secrets and minting dynamic cloud credentials; environments with update approvals…
framing: The ESC rule that update approvals apply to all users proves the claim's special case for Neo, which acts as a user.; evidence: The ESC approvals doc backs the draft mechanism: "When an update approval ruleset is enabled on an environment, direct writes to the environment are blocked. Instead, users must create **drafts**... Drafts go through a review and…; source: repo:content/docs/esc/concepts/approvals.md (L56-58, L114-131); intuition: "Any environment the user can open" leaves out that open-approval rulesets also gate Neo's reads. The same page…
source: repo:content/docs/esc/concepts/approvals.md (L56-58, L114-131)
framing: entailed-narrower — The ESC rule that update approvals apply to all users proves the claim's special case for Neo, which acts as a user.
pass1 · behavior · medium confidence
#129
✅ Verified
content/docs/ai/concepts/neo/permissions.md:69
Neo's models run through Amazon Bedrock, which does not retain prompts or completions.
framing: The claim's "does not retain prompts or completions" means the same as AWS's "doesn't store or log your prompts and completions." The Neo-on-Bedrock half…; evidence: AWS says: "Amazon Bedrock doesn't store or log your prompts and completions." A separate Pulumi Neo docs page (not the file under review) backs up the Bedrock routing: Neo is "powered by Anthropic's Claude family of models accessed via…; source: https://aws.amazon.com/blogs/alps/security_bedrock/ ; https://www.pulumi.com/docs/ai/neo/; intuition: AWS's no-storage promise covers Bedrock itself. If Pulumi turns on model invocation logging in its own AWS account…
source: https://aws.amazon.com/blogs/alps/security_bedrock/ ; https://www.pulumi.com/docs/ai/neo/
framing: exact-match — The claim's "does not retain prompts or completions" means the same as AWS's "doesn't store or log your prompts and completions." The Neo-on-Bedrock half comes only from a pulumi.com page, so it's backed up but not checked against…
pass3 · entity-spec · medium confidence
#130
✅ Verified
content/docs/ai/concepts/neo/permissions.md:69
MCP integration credentials are never exposed to the language model, whereas an ESC-sourced secret value can reach the model if a task reads it directly…
framing: This is a link-existence claim, and the link resolves. The linked page is a same-site docs page, so it backs the "never exposed" wording but is not…; evidence: The link target is real: content/docs/ai/integrations/external-mcp-servers.md exists and is titled "External MCP Servers". Its Credential storage section matches the claim: "Credentials are never exposed to the language model and are…; source: repo:content/docs/ai/integrations/external-mcp-servers.md#L36-L38
source: repo:content/docs/ai/integrations/external-mcp-servers.md#L36-L38
framing: exact-match — This is a link-existence claim, and the link resolves. The linked page is a same-site docs page, so it backs the "never exposed" wording but is not product-source proof. I did not check the ESC half of the claim against product source.
pass1 · url · high confidence
#131
✅ Verified
content/docs/ai/concepts/neo/permissions.md:71
ESC open approvals put a reviewer in front of every attempt to open an environment, including Neo's, since Neo opens environments as the acting user.
framing: Small nuance: one approved access grant covers repeated opens until its time window ends, so "every attempt" really means every attempt made without an…; evidence: The ESC approvals docs say "When an open approval ruleset is enabled on an environment, users with `open` permission cannot open the environment directly" and "any attempt to open the environment without an active access grant will be…; source: repo:content/docs/esc/concepts/approvals.md (Open approvals section, L114-137); intuition: "every attempt" overstates a little, since one approved grant allows repeated opens within its time window.
source: repo:content/docs/esc/concepts/approvals.md (Open approvals section, L114-137)
framing: Small nuance: one approved access grant covers repeated opens until its time window ends, so "every attempt" really means every attempt made without an active grant.
pass1 · behavior · medium confidence
#132
✅ Verified
content/docs/ai/concepts/neo/permissions.md:89
In the `pulumi neo` CLI and API, the strictest approval mode is named `manual`, the same mode the console calls Review; the permission-mode values…
framing: The API half of the claim and the "same in both places" part are inferred from the CLI flags, not confirmed against API source.; evidence: The auto-generated CLI reference (transcribed from pulumi/pulumi) shows `--approval-mode` with values "'manual' prompts on every call, 'balanced' auto-approves low-risk calls, 'auto' executes everything without prompting", which makes…; source: repo:content/docs/iac/cli/commands/pulumi_neo.md L24-L31 (auto-generated from pulumi/pulumi pkg/cmd/pulumi/neo)
source: repo:content/docs/iac/cli/commands/pulumi_neo.md L24-L31 (auto-generated from pulumi/pulumi pkg/cmd/pulumi/neo)
framing: The API half of the claim and the "same in both places" part are inferred from the CLI flags, not confirmed against API source.
pass1 · api-surface · medium confidence
#133
✅ Verified
content/docs/ai/concepts/neo/permissions.md:92
The tasks page at /docs/ai/concepts/neo/tasks/ has a 'plan-mode' section; Plan Mode makes Neo research and agree on a plan with the user before acting and…
framing: The tasks page says Plan Mode combines with task (approval) modes. It never mentions "permission" modes, so "any permission or approval mode" stretches the…; evidence: tasks.md has a "## Plan Mode" heading (anchor #plan-mode). It says Neo "investigates your environment… iterates with you… Waits for your explicit approval before any execution begins," and "Task modes are independent of Plan Mode… You…; source: repo:content/docs/ai/concepts/neo/tasks.md L33-62
source: repo:content/docs/ai/concepts/neo/tasks.md L33-62
framing: entailed-narrower — The tasks page says Plan Mode combines with task (approval) modes. It never mentions "permission" modes, so "any permission or approval mode" stretches the source a little.
pass1 · url · medium confidence
#134
✅ Verified
content/docs/ai/concepts/neo/permissions.md:108
Neo approval (task) mode values are Review-`manual` / Balanced / Auto, set per task in the task UI or with `--approval-mode` in the CLI, with an org admin…
framing: On the default branch the Settings page is at /docs/ai/neo/settings/. The PR appears to move the Neo pages under /docs/ai/concepts/neo/, which is consistent…; evidence: The auto-generated CLI reference lists `--approval-mode string Approval mode for tool calls: 'manual' ... 'balanced' ... 'auto' ... (default "manual")`. The Neo Settings page has a "## Task modes" section, which produces the…; source: repo:content/docs/iac/cli/commands/pulumi_neo.md L24; gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md (## Task modes)
source: repo:content/docs/iac/cli/commands/pulumi_neo.md L24; gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md (## Task modes)
framing: exact-match — On the default branch the Settings page is at /docs/ai/neo/settings/. The PR appears to move the Neo pages under /docs/ai/concepts/neo/, which is consistent with permissions.md keeping the alias /docs/ai/neo/permissions/. Check that the…
pass1 · api-surface · high confidence
#135
✅ Verified
content/docs/ai/concepts/neo/permissions.md:111
| Per-automation overrides | Permission and approval mode | User who owns the automation | [Automations](/docs/ai/concepts/neo/automations/) |
framing: The link resolves, and the page supports what the table row says about it.; evidence: The link target exists at content/docs/ai/concepts/neo/automations.md (title "Automations"). That page covers per-automation overrides of approval mode and permission mode ("1. The per-automation setting, if set") and says a scheduled…; source: repo:content/docs/ai/concepts/neo/automations.md
source: repo:content/docs/ai/concepts/neo/automations.md
framing: exact-match — The link resolves, and the page supports what the table row says about it.
pass1 · url · high confidence
#136
✅ Verified
content/docs/ai/concepts/neo/permissions.md:112
The `--disable-integrations` CLI flag disables integrations for a Neo task.
framing: Flag description 'run with no integration credentials, ignoring org-enabled integrations' matches 'disables integrations for a task'.; evidence: The auto-generated `pulumi neo` CLI reference, built from pulumi/pulumi's cobra definitions, lists the flag: "--disable-integrations Run the Neo task with no integration credentials, ignoring any org-enabled integrations."; source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from github.com/pulumi/pulumi/v3/pkg/cmd/pulumi)
source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from github.com/pulumi/pulumi/v3/pkg/cmd/pulumi)
framing: Flag description 'run with no integration credentials, ignoring org-enabled integrations' matches 'disables integrations for a task'.
pass1 · api-surface · high confidence
#137
✅ Verified
content/docs/ai/concepts/neo/permissions.md:113
The page /docs/ai/integrations/ exists and covers Neo integration enablement and credentials.
framing: The link target exists and covers admin-configured integrations at the org level. The detailed enablement and credentials content now lives on the…; evidence: content/docs/ai/integrations/_index.md exists. It is the "Neo Integrations" hub page and says "All integrations are configured at the organization level by an administrator." It links to the MCP, CLI, GitHub and Slack integration…; source: repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/_index.md
framing: The link target exists and covers admin-configured integrations at the org level. The detailed enablement and credentials content now lives on the external-mcp-servers and cli-integrations subpages.
pass1 · url · medium confidence
#141
✅ Verified
content/docs/ai/concepts/neo/permissions.md:120
CLI integrations are admin-controlled: an org admin points a CLI at an ESC environment and every task in the org is offered that integration unless the user…
framing: The link existence is confirmed directly. The behavior claims are backed only by a sibling docs page, not by product source.; evidence: The link target exists at content/docs/ai/integrations/cli-integrations.md, and that page says the same thing: "CLI integrations are configured by an organization administrator and are offered to every Neo task in the organization once…; source: repo:content/docs/ai/integrations/cli-integrations.md#L75,L105,L127
source: repo:content/docs/ai/integrations/cli-integrations.md#L75,L105,L127
framing: exact-match — The link existence is confirmed directly. The behavior claims are backed only by a sibling docs page, not by product source.
pass1 · url · medium confidence
#142
✅ Verified
content/docs/ai/concepts/neo/permissions.md:128
On GitHub.com, Neo writes as the shared Pulumi GitHub App for all VCS interactions (opening PRs, pushing commits, PR comments, checks) and uses the user's…
framing: This only checks the claim against other Pulumi docs pages; I didn't check the Pulumi Cloud source code. The cited code-reviews page backs the…; evidence: The linked code-reviews page's Setup step requires "Grant Pulumi access to your GitHub account by completing the individual OAuth flow". The github-app page says the same thing: "GitHub.com integrations always use the shared app…; source: repo:content/docs/ai/concepts/neo/code-reviews.md L41-46; repo:content/docs/integrations/version-control/github-app.md L82, L140-142
source: repo:content/docs/ai/concepts/neo/code-reviews.md L41-46; repo:content/docs/integrations/version-control/github-app.md L82, L140-142
framing: exact-match — This only checks the claim against other Pulumi docs pages; I didn't check the Pulumi Cloud source code. The cited code-reviews page backs the individual-access requirement, and the github-app page backs the shared-app writes and the…
pass1 · url · medium confidence
#144
✅ Verified
content/docs/ai/concepts/neo/permissions.md:133
With Custom VCS, Neo uses the credentials from the integration's ESC environment, can clone and push (Git and Mercurial), but cannot open pull requests or…
framing: Only another editorial docs page backs this up (no product-source check), so confidence is medium rather than high.; evidence: The sibling Custom VCS integration page says the same thing: "Neo ... can clone and push to Git and Mercurial repositories registered with a Custom VCS integration using the credentials from the integration's ESC environment. Neo cannot…; source: repo:content/docs/integrations/version-control/custom-vcs.md L19
source: repo:content/docs/integrations/version-control/custom-vcs.md L19
framing: Only another editorial docs page backs this up (no product-source check), so confidence is medium rather than high.
pass1 · feature · medium confidence
#145
✅ Verified
content/docs/ai/concepts/neo/permissions.md:141
Pages exist at /docs/ai/concepts/neo/tasks/, /docs/ai/concepts/neo/automations/, and /docs/ai/integrations/ covering Plan Mode and approval modes, scheduled…
framing: The integrations index page only summarizes MCP and CLI credentials. The details are on the child pages external-mcp-servers and cli-integrations.; evidence: All three pages exist in the repo and cover the stated topics. tasks.md has "## Plan Mode" and "## Task modes", which describe the approval modes. automations.md has "Scheduled tasks default to two settings. Approval mode is **auto**...…; source: repo:content/docs/ai/concepts/neo/tasks.md; repo:content/docs/ai/concepts/neo/automations.md; repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/concepts/neo/tasks.md; repo:content/docs/ai/concepts/neo/automations.md; repo:content/docs/ai/integrations/_index.md
framing: exact-match — The integrations index page only summarizes MCP and CLI credentials. The details are on the child pages external-mcp-servers and cli-integrations.
pass1 · url · high confidence
#146
✅ Verified
content/docs/ai/concepts/neo/permissions.md:143
- [Integrations](/docs/ai/integrations/) — MCP and CLI integration credentials
evidence: The link target content/docs/ai/integrations/_index.md exists, titled "Integrations". It covers "[MCP integrations] and [CLI integrations]", and CLI integrations use "credentials managed in Pulumi ESC", so the link's description fits the…; source: repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/_index.md
framing: exact-match
pass1 · url · high confidence
#149
✅ Verified
content/docs/ai/concepts/neo/pull-requests/index.md:26
On GitHub, Neo also analyzes pull requests that your team opens and leaves its feedback right in the PR. See [Neo code reviews](/docs/ai/concepts/neo/code-revi…
framing: The linked page backs both points: the reviews are GitHub-only, and Neo leaves its feedback in the PR. "PRs your team opens" is a little loose, since…; evidence: The link target is the file content/docs/ai/concepts/neo/code-reviews.md, which exists. It says: "Neo code reviews analyze pull requests against what Pulumi Cloud knows about your running infrastructure and leave feedback in the pull…; source: repo:content/docs/ai/concepts/neo/code-reviews.md
source: repo:content/docs/ai/concepts/neo/code-reviews.md
framing: exact-match — The linked page backs both points: the reviews are GitHub-only, and Neo leaves its feedback in the PR. "PRs your team opens" is a little loose, since automated reviews skip drafts and bot-opened PRs.
pass1 · url · medium confidence
#151
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:21
'/docs/ai/concepts/neo/instructions/': ['custom-instructions', 'what-to-include', 'example', 'configuring-custom-instructions'…
framing: This is a link and anchor check: the redirect target path and all 12 anchors resolve to headings on the target page.; evidence: The target page content/docs/ai/concepts/neo/instructions/index.md exists. Every anchor in the redirect map matches a heading on that page: "## Custom instructions", "### What to include", "### Example" (twice, so the second one becomes…; source: repo:content/docs/ai/concepts/neo/instructions/index.md
source: repo:content/docs/ai/concepts/neo/instructions/index.md
framing: exact-match — This is a link and anchor check: the redirect target path and all 12 anchors resolve to headings on the target page.
pass1 · url · high confidence
#152
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:35
Pulumi Neo can be configured at the organization, repository, and user level.
evidence: The sibling instructions page backs up the organization and repository levels: "Custom Instructions set organization-wide defaults that apply to every task" and "Repository instructions (`AGENTS.md`) add project-specific conventions".…; source: repo:content/docs/ai/concepts/neo/instructions/index.md (L70-82); intuition: The 'repository level' is set in AGENTS.md files rather than in Neo Settings, so saying Neo is 'configured' at that…
source: repo:content/docs/ai/concepts/neo/instructions/index.md (L70-82)
pass1 · feature · low confidence
#158
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:57
Neo code reviews can be disabled by selecting the 'Code reviews' tab in Neo Settings and turning off 'Enable code reviews'.
framing: The source says to disable code reviews under the Code reviews tab; the claim adds a specific toggle label that the source doesn't name.; evidence: The linked page backs up the navigation path: "To turn them off, disable code reviews under **Settings** > **Neo settings** > **Code reviews**." It doesn't name the toggle, so the exact label "Enable code reviews" is not confirmed. That…; source: repo:content/docs/ai/concepts/neo/code-reviews.md (L45, L50)
source: repo:content/docs/ai/concepts/neo/code-reviews.md (L45, L50)
framing: exact-match — The source says to disable code reviews under the Code reviews tab; the claim adds a specific toggle label that the source doesn't name.
pass1 · url · medium confidence
#160
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:65
A Neo usage limits page at /docs/ai/concepts/neo/usage-limits/ describes how to cap organization spending on Neo.
evidence: The target page exists at content/docs/ai/concepts/neo/usage-limits.md, which resolves to /docs/ai/concepts/neo/usage-limits/. It says: "A Neo usage limit caps what your organization spends on Neo in a monthly billing period."; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
framing: exact-match
pass1 · url · high confidence
#161
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:71
The 'Model provider' tab in Neo Settings lets users run Neo tasks with their own model provider credentials.
framing: The live /docs/ai/neo/settings/ page shows the same text, but it is the page under review, so it was not used as evidence. Note that BYOK is Enterprise-only…; evidence: (escalated from pass1) A separate Pulumi docs page (the BYOK guide, not the page under review) says to open "your organization's **Neo Settings**" and then "Select **Model provider**, then **Add model provider**". It adds that Neo "uses…; source: https://www.pulumi.com/docs/ai/neo/model-providers/
source: https://www.pulumi.com/docs/ai/neo/model-providers/
framing: The live /docs/ai/neo/settings/ page shows the same text, but it is the page under review, so it was not used as evidence. Note that BYOK is Enterprise-only (plus legacy Business Critical).
pass3 · feature · medium confidence
#163
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:73
The page /docs/ai/concepts/neo/model-providers/ covers setup steps, billing behavior, and instructions to switch providers.
evidence: The target page content/docs/ai/concepts/neo/model-providers.md exists. It has an "## Add a model provider" section with setup steps, a "## Switch or remove a provider" section ("choose **Set as default** to switch to it"), and a "##…; source: repo:content/docs/ai/concepts/neo/model-providers.md
source: repo:content/docs/ai/concepts/neo/model-providers.md
framing: exact-match
pass1 · url · high confidence
#165
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:81
Neo integrations are configured in the 'Integrations' tab of Neo Settings, where administrators can enable services and provide credentials.
framing: This is only backed by other pulumi.com docs pages that agree with it, not by product source.; evidence: The sibling Integrations docs say the same thing: "To enable an integration, navigate to **Neo Settings**, select **Integrations**, select the integration, and provide the required credentials." They also say "MCP integrations are…; source: repo:content/docs/ai/integrations/external-mcp-servers.md (L22, L32); repo:content/docs/ai/integrations/_index.md (L32)
source: repo:content/docs/ai/integrations/external-mcp-servers.md (L22, L32); repo:content/docs/ai/integrations/_index.md (L32)
framing: This is only backed by other pulumi.com docs pages that agree with it, not by product source.
pass1 · behavior · medium confidence
#166
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:81
Neo can connect to third-party services like issue trackers, observability platforms, and incident response tools, and integrations are configured in the…
framing: This only matches other Pulumi docs pages. The Pulumi Cloud UI source is private, so I couldn't check it directly.; evidence: The sibling docs page backs this up: "To enable an integration, navigate to **Neo Settings**, select **Integrations**, select the integration, and provide the required credentials." It also says the supported integrations are Atlassian…; source: repo:content/docs/ai/integrations/external-mcp-servers.md (L17-32); repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md (L17-32); repo:content/docs/ai/integrations/_index.md
framing: This only matches other Pulumi docs pages. The Pulumi Cloud UI source is private, so I couldn't check it directly.
pass1 · feature · medium confidence
#168
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:87
Neo task modes are presets that control what actions Neo can take automatically; new tasks start with a default mode, which users can adjust or override…
framing: Only another docs page supports this (it agrees with the claim). Pulumi Cloud is closed source, so there was no product code to check.; evidence: The sibling Neo tasks page backs this up independently: "Task modes control how much autonomy Neo has during execution. At any time during a task, the operating mode can be set to: Review mode (default)… Balanced mode… Auto mode." That…; source: repo:content/docs/ai/concepts/neo/tasks.md L54-60
source: repo:content/docs/ai/concepts/neo/tasks.md L54-60
framing: Only another docs page supports this (it agrees with the claim). Pulumi Cloud is closed source, so there was no product code to check.
pass1 · behavior · medium confidence
#170
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:93
Neo Review mode is the default task mode and requires approval before running `pulumi preview`, running `pulumi up`, and opening a pull request.
evidence: Pulumi Cloud is closed-source, so I could only find corroboration on other pages. content/docs/ai/neo/tasks/_index.md and permissions/_index.md use the same three modes, and what-is-agentic-infrastructure.md says "Review mode, the…; source: gh search code --repo pulumi/docs "Balanced mode" (content/what-is/what-is-agentic-infrastructure.md; content/docs/ai/neo/tasks/_index.md; static-prebuilt cloud-sdk AgentBackendEvent.UserApprovalRequest reference); intuition: Only Pulumi editorial pages support this. The product-generated SDK docs don't mention Review mode's default status…
source: gh search code --repo pulumi/docs "Balanced mode" (content/what-is/what-is-agentic-infrastructure.md; content/docs/ai/neo/tasks/_index.md; static-prebuilt cloud-sdk AgentBackendEvent.UserApprovalRequest reference)
pass1 · behavior · low confidence
#172
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:113
Plan Mode is a separate, opt-in Neo feature that controls what happens before execution, and it can be used with any task mode.
framing: The source says task modes are "independent of Plan Mode" and "You can combine them" (its example pairs Plan Mode with Auto mode). This supports the claim…; evidence: The tasks page backs this up: "Task modes are independent of Plan Mode. Task modes control what approvals Neo requires during execution, while Plan Mode controls what happens before execution. You can combine them". It also shows Plan…; source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/tasks/_index.md
source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/tasks/_index.md
framing: entailed-narrower — The source says task modes are "independent of Plan Mode" and "You can combine them" (its example pairs Plan Mode with Auto mode). This supports the claim that Plan Mode works "with any task mode". Corroborated only by another Pulumi…
pass1 · url · medium confidence
#183
✅ Verified
content/docs/ai/concepts/neo/settings/index.md:138
Neo browser notifications also require the operating system to allow notifications for the user's browser.
evidence: (escalated from pass1) This is how web notifications generally work, and several vendor help pages confirm it. BoldDesk says notifications "must be enabled for the browser in the Windows or Mac notification settings and allowed in the…; source: https://support.bolddesk.com/kb/article/18196/how-to-enable-browser-notifications-on-windows-and-mac; https://documentation.onesignal.com/docs/en/notifications-not-shown-web-push
source: https://support.bolddesk.com/kb/article/18196/how-to-enable-browser-notifications-on-windows-and-mac; https://documentation.onesignal.com/docs/en/notifications-not-shown-web-push
pass3 · behavior · medium confidence
#185
✅ Verified
content/docs/ai/concepts/neo/slash-commands/index.md:14
Typing `/` in a Pulumi Neo conversation displays the list of available slash commands.
framing: Only Pulumi's own pages back this up. The settings page is where this text came from before the split, so the blog is the only independent source. The Pulumi…; evidence: (escalated from pass1) The Pulumi Slash Commands launch blog says "When you type / in Neo, you'll see available commands, select one, and Neo receives the full prompt behind it." The current Neo Settings page, which PR #22261 splits this…; source: https://www.pulumi.com/blog/slash-commands-custom-instructions/ ; https://www.pulumi.com/docs/ai/neo/settings/
source: https://www.pulumi.com/blog/slash-commands-custom-instructions/ ; https://www.pulumi.com/docs/ai/neo/settings/
framing: Only Pulumi's own pages back this up. The settings page is where this text came from before the split, so the blog is the only independent source. The Pulumi Cloud console UI source isn't public, so this can't be checked against product…
pass3 · behavior · medium confidence
#186
✅ Verified
content/docs/ai/concepts/neo/slash-commands/index.md:18
Pulumi Neo includes several built-in slash commands for common infrastructure tasks.
framing: Both supporting pages are on pulumi.com, so they back the claim but are not product source. Medium confidence because product source (Neo is closed-source…; evidence: (escalated from pass1) The Neo Settings docs page says: "Neo includes several built-in commands for common infrastructure tasks." It lists four of them: /get-started, /policy-issues-report, /component-version-report and…; source: https://www.pulumi.com/docs/ai/neo/settings/ ; https://www.pulumi.com/blog/slash-commands-custom-instructions/
source: https://www.pulumi.com/docs/ai/neo/settings/ ; https://www.pulumi.com/blog/slash-commands-custom-instructions/
framing: Both supporting pages are on pulumi.com, so they back the claim but are not product source. Medium confidence because product source (Neo is closed-source Pulumi Cloud) was not checked.
pass3 · feature · medium confidence
#187
✅ Verified
content/docs/ai/concepts/neo/slash-commands/index.md:22
The built-in Pulumi Neo slash command `/component-version-report` exists and lists components that are outdated in the user's private registry.
framing: The only support is other pulumi.com pages that agree with this one. That backs up the claim but isn't product source.; evidence: The PR's wording matches two other Pulumi pages word for word: the slash-commands launch blog post and the Neo settings page both say "| `/component-version-report` | Lists components that are outdated in your private registry |". Neo's…; source: gh search code --owner pulumi component-version-report → pulumi/docs:content/blog/slash-commands-custom-instructions/index.md, pulumi/docs:content/docs/ai/neo/settings/_index.md
source: gh search code --owner pulumi component-version-report → pulumi/docs:content/blog/slash-commands-custom-instructions/index.md, pulumi/docs:content/docs/ai/neo/settings/_index.md
framing: The only support is other pulumi.com pages that agree with this one. That backs up the claim but isn't product source.
pass1 · feature · medium confidence
#188
✅ Verified
content/docs/ai/concepts/neo/slash-commands/index.md:29
Pulumi Neo supports creating organization-specific custom slash commands that capture a team's prompts.
framing: The Settings page is where this content lived before PR #22261 split it out, so it is effectively the same text. The blog post gives more independent…; evidence: (escalated from pass1) Pulumi's launch blog says "Slash Commands capture proven prompts so anyone on your team can use them," and Neo ships built-in commands while "You can also create your own" in Pulumi Cloud. The existing Neo Settings…; source: https://www.pulumi.com/blog/slash-commands-custom-instructions/ ; https://www.pulumi.com/docs/ai/neo/settings/
source: https://www.pulumi.com/blog/slash-commands-custom-instructions/ ; https://www.pulumi.com/docs/ai/neo/settings/
framing: The Settings page is where this content lived before PR #22261 split it out, so it is effectively the same text. The blog post gives more independent corroboration, but it is also a pulumi.com page, so confidence is medium rather than high.
pass3 · feature · medium confidence
#196
✅ Verified
content/docs/ai/concepts/neo/tasks.md:66
In Neo tasks, depending on the task mode, Neo seeks approval before taking certain actions like running `pulumi up` or opening a PR.
framing: The live tasks page (the reviewed file) has the same sentence, so I didn't rely on it. I used the generated REST schema and sibling pages instead.; evidence: (escalated from pass1) The auto-generated Cloud REST API reference lists the task approval modes (manual/balanced/auto). Its approval-request schema says sensitive operations "(e.g., pulumi up) that still require manual approval in…; source: https://www.pulumi.com/docs/reference/cloud-rest-api/schema/agentbackendeventuserapprovalrequest/ ; https://www.pulumi.com/docs/ai/neo/settings/ ; https://www.pulumi.com/docs/ai/neo/permissions/
source: https://www.pulumi.com/docs/reference/cloud-rest-api/schema/agentbackendeventuserapprovalrequest/ ; https://www.pulumi.com/docs/ai/neo/settings/ ; https://www.pulumi.com/docs/ai/neo/permissions/
framing: The live tasks page (the reviewed file) has the same sentence, so I didn't rely on it. I used the generated REST schema and sibling pages instead.
pass3 · behavior · medium confidence
#198
✅ Verified
content/docs/ai/concepts/neo/tasks.md:72
If a Neo task results in code modifications, Neo will offer to open a pull request once the user is satisfied with the implementation.
framing: Both pages agree that Neo offers to open a PR. They differ on when: the linked page says "after a preview is run", while tasks.md says "once you are…; evidence: The link target exists locally at content/docs/ai/concepts/neo/pull-requests/index.md, so it resolves, and that page says Neo offers to open PRs: "Neo will offer to open a pull request after a preview is run. You can also ask Neo to open…; source: repo:content/docs/ai/concepts/neo/pull-requests/index.md; intuition: The two pages describe the trigger differently ("after a preview is run" vs "once you are satisfied"). Worth making…
source: repo:content/docs/ai/concepts/neo/pull-requests/index.md
framing: exact-match — Both pages agree that Neo offers to open a PR. They differ on when: the linked page says "after a preview is run", while tasks.md says "once you are satisfied with the implementation".
pass1 · url · medium confidence
#199
✅ Verified
content/docs/ai/concepts/neo/tasks.md:76
If an organization has integrations enabled, Neo can read from external services like issue trackers, observability platforms, and runbooks during tasks.
framing: Source: "brings context in from issue trackers, observability platforms, runbook wikis" + "Once enabled, they're available to every Neo task". Claim…; evidence: The linked integrations page says: "MCP brings context in from issue trackers, observability platforms, runbook wikis, and on-call tools" and "All integrations are configured at the organization level by an administrator. Once enabled…; source: repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/_index.md
framing: exact-match — Source: "brings context in from issue trackers, observability platforms, runbook wikis" + "Once enabled, they're available to every Neo task". Claim: org-enabled integrations let Neo read from issue trackers, observability platforms, and…
pass1 · url · medium confidence
#201
✅ Verified
content/docs/ai/concepts/neo/usage-limits.md:19
Requests served through [bring your own key (BYOK)](/docs/ai/concepts/neo/model-providers/) do not count toward these limits and can continue after a limit…
framing: Source: "Pulumi does not charge Neo tokens for those requests". Claim: BYOK requests "do not count toward these limits". That holds because the limits cover…; evidence: The link works and goes to the BYOK page, which says: "Your model provider bills you for requests served through BYOK. Pulumi does not charge Neo tokens for those requests." The limits page says limits cover "Neo usage billed by Pulumi"…; source: repo:content/docs/ai/concepts/neo/model-providers.md (L86-88); intuition: I couldn't confirm that BYOK requests keep running while Neo is paused at a limit. Confirm with the Neo team.
source: repo:content/docs/ai/concepts/neo/model-providers.md (L86-88)
framing: entailed-narrower — Source: "Pulumi does not charge Neo tokens for those requests". Claim: BYOK requests "do not count toward these limits". That holds because the limits cover only usage Pulumi bills. "Can continue after a limit is reached" is an inference…
pass1 · url · medium confidence
#203
✅ Verified
content/docs/ai/get-started/_index.md:14
Pulumi Neo works with an organization's context, policy guardrails, and approvals.
framing: Sibling Neo concept pages say the same thing almost word for word: "organizational context, policy guardrails, human-in-the-loop approvals."; evidence: The Neo concepts overview says Neo "adds organizational context, policy guardrails, human-in-the-loop approvals, and scheduled autonomous work." The permissions page describes the approval modes ("Review mode: Neo requires approval…; source: repo:content/docs/ai/concepts/neo/_index.md L19-22, L41-43; repo:content/docs/ai/concepts/neo/permissions.md L73-86
source: repo:content/docs/ai/concepts/neo/_index.md L19-22, L41-43; repo:content/docs/ai/concepts/neo/permissions.md L73-86
framing: Sibling Neo concept pages say the same thing almost word for word: "organizational context, policy guardrails, human-in-the-loop approvals."
pass1 · feature · medium confidence
#204
✅ Verified
content/docs/ai/get-started/_index.md:14
Pulumi works with the AI agent a team already uses (i.e., third-party coding agents can be used with Pulumi) as well as with Pulumi Neo.
evidence: The official pulumi/agent-skills README says skills "teach AI coding assistants" and "work with: Claude Code, GitHub Copilot, Cursor, VS Code, OpenAI Codex, Gemini CLI." It also includes a "delegation/ # Hand off work to Pulumi Neo"…; source: gh api repos/pulumi/agent-skills/readme
source: gh api repos/pulumi/agent-skills/readme
pass1 · feature · high confidence
#205
✅ Verified
content/docs/ai/get-started/_index.md:18
Coding agents such as Claude Code, Codex, Cursor, and GitHub Copilot can write, preview, and deploy Pulumi programs directly.
framing: The README confirms the skills support these agents. The "write, preview, and deploy" ability depends on agents running the CLI with shell access; I inferred…; evidence: The pulumi/agent-skills README says the skills "work with: Claude Code, GitHub Copilot, Cursor, VS Code, OpenAI Codex, Gemini CLI", and its Pulumi skills cover writing programs and running `pulumi preview`/`pulumi up`. That backs the…; source: gh api repos/pulumi/agent-skills/readme (README.md L7-14, L44-56)
source: gh api repos/pulumi/agent-skills/readme (README.md L7-14, L44-56)
framing: The README confirms the skills support these agents. The "write, preview, and deploy" ability depends on agents running the CLI with shell access; I inferred that rather than finding it stated word for word.
pass1 · feature · medium confidence
#206
✅ Verified
content/docs/ai/get-started/_index.md:20
A page exists at /docs/ai/concepts/cli-for-agents/ describing how the Pulumi CLI works for agents, covering `npx pulumi`, `pulumi do`, and `--json` output.
evidence: The file content/docs/ai/concepts/cli-for-agents.md exists and its menu parent is ai-concepts, so it renders at /docs/ai/concepts/cli-for-agents/. Its meta_desc reads: "run it with npx pulumi, do one-shot resource operations with pulumi…; source: repo:content/docs/ai/concepts/cli-for-agents.md
source: repo:content/docs/ai/concepts/cli-for-agents.md
pass1 · url · high confidence
#207
✅ Verified
content/docs/ai/get-started/_index.md:22
The Pulumi CLI supports structured `--json` output.
framing: CLI source shows `--json` on several commands. The claim's general statement 'supports structured --json output' holds, though not every command has the flag.; evidence: The auto-generated CLI reference for `pulumi preview` lists `-j, --json Serialize the preview diffs, operations, and overall output as JSON`. The same flag string also appears in pulumi/pulumi source (pkg/cmd/pulumi/events/replay.go).…; source: repo:content/docs/iac/cli/commands/pulumi_preview.md L48; gh search code --repo pulumi/pulumi "Serialize the preview diffs, operations, and overall output as JSON"
source: repo:content/docs/iac/cli/commands/pulumi_preview.md L48; gh search code --repo pulumi/pulumi "Serialize the preview diffs, operations, and overall output as JSON"
framing: entailed-narrower — CLI source shows `--json` on several commands. The claim's general statement 'supports structured --json output' holds, though not every command has the flag.
pass1 · api-surface · high confidence
#208
✅ Verified
content/docs/ai/get-started/_index.md:26
Pulumi Neo works with an organization's context, policy guardrails, and approvals.
evidence: The Neo concept page (a separate doc from the one under review) says Neo "adds organizational context, policy guardrails, human-in-the-loop approvals, and scheduled autonomous work". It also says task modes "control which steps need your…; source: repo:content/docs/ai/concepts/neo/_index.md L19-22, L86-92; repo:content/docs/ai/_index.md L27
source: repo:content/docs/ai/concepts/neo/_index.md L19-22, L86-92; repo:content/docs/ai/_index.md L27
pass1 · feature · medium confidence
#209
✅ Verified
content/docs/ai/get-started/_index.md:26
Pulumi Neo can run long or scheduled tasks on its own.
evidence: The canonical editions data lists a Neo scheduled-tasks feature: "id: neo-scheduled-tasks / name: Scheduled tasks / min_edition: pro". That supports the scheduled part of the claim. I didn't separately confirm the "long tasks on its own"…; source: repo:data/pulumi_editions.yaml (L209-211); intuition: Scheduled tasks need the Pro edition, but the get-started line doesn't mention that limit.
source: repo:data/pulumi_editions.yaml (L209-211)
pass1 · feature · medium confidence
#210
✅ Verified
content/docs/ai/get-started/_index.md:28
Pulumi Neo can be enabled for an organization, and users can run a first task, per the guide at /docs/ai/get-started/neo/.
framing: The page says Neo is on by default for paid editions, so "enabling" here means getting access to Neo. That fits the page's own heading, "Enable Neo for Your…; evidence: The linked page exists and covers both parts of the claim. Its meta_desc reads "Learn how to set up Pulumi Neo for your organization and run your first infrastructure task", and its sections include "Enable Neo for Your Organization" and…; source: repo:content/docs/ai/get-started/neo.md
source: repo:content/docs/ai/get-started/neo.md
framing: exact-match — The page says Neo is on by default for paid editions, so "enabling" here means getting access to Neo. That fits the page's own heading, "Enable Neo for Your Organization".
pass1 · url · high confidence
#212
✅ Verified
content/docs/ai/get-started/neo.md:20
Pulumi Neo is enabled by default for an organization, and can be disabled in the Pulumi Cloud console under Settings > Neo Settings > General.
evidence: The Neo Settings page backs both halves of the claim: "Neo and all of its features are enabled by default," and you disable it by going to "Neo Settings ... Select the 'General' tab ... Toggle 'Enable Neo for organization' on or off".…; source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md (L18-28)
source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md (L18-28)
pass1 · behavior · medium confidence
#214
✅ Verified
content/docs/ai/get-started/neo.md:24
Pulumi supports GitHub, Azure DevOps, GitLab, Bitbucket, and Custom VCS as version control integrations for Neo.
evidence: The version-control index lists GitHub, GitLab, Bitbucket, Azure DevOps and Custom VCS. custom-vcs.md says "Neo... can clone and push to Git and Mercurial repositories registered with a Custom VCS integration" but "cannot open pull…; source: repo:content/docs/integrations/version-control/_index.md; repo:content/docs/integrations/version-control/custom-vcs.md L19, L209-211; intuition: The page lists Custom VCS next to the bullet "Enables pull request creation", but Custom VCS can't create PRs for…
source: repo:content/docs/integrations/version-control/_index.md; repo:content/docs/integrations/version-control/custom-vcs.md L19, L209-211
pass1 · feature · medium confidence
#215
✅ Verified
content/docs/ai/get-started/neo.md:26
A VCS integration allows Neo to read repository content for better context and enables pull request creation.
framing: The only support is another pulumi.com docs page, so confidence is low.; evidence: A sibling Neo docs page backs this up. It says Neo makes changes "through code and pull requests" and "authenticates as the shared app installation for its VCS interactions". The reviewed page's own line 24 says the same thing ("With one…; source: repo:content/docs/ai/concepts/neo/permissions.md (L45, L51, L55)
source: repo:content/docs/ai/concepts/neo/permissions.md (L45, L51, L55)
framing: The only support is another pulumi.com docs page, so confidence is low.
pass1 · feature · low confidence
#217
✅ Verified
content/docs/ai/get-started/neo.md:36
See the Neo tasks concept page section 'ownership-and-sharing' at /docs/ai/concepts/neo/tasks/#ownership-and-sharing, and Neo's permissions model page at…
framing: Internal links point to existing pages and an existing heading anchor; the RBAC link (/docs/administration/concepts/rbac/) is used the same way in both…; evidence: Both link targets resolve: content/docs/ai/concepts/neo/tasks.md has the heading "### Ownership and sharing" (L84), which produces the anchor #ownership-and-sharing, and content/docs/ai/concepts/neo/permissions.md exists with the title…; source: repo:content/docs/ai/concepts/neo/tasks.md#L84-L92; repo:content/docs/ai/concepts/neo/permissions.md#L1-L24
source: repo:content/docs/ai/concepts/neo/tasks.md#L84-L92; repo:content/docs/ai/concepts/neo/permissions.md#L1-L24
framing: exact-match — Internal links point to existing pages and an existing heading anchor; the RBAC link (/docs/administration/concepts/rbac/) is used the same way in both sibling pages.
pass1 · url · high confidence
#218
✅ Verified
content/docs/ai/get-started/neo.md:40
When creating a Neo task, the user can choose to run Neo with their full permissions ('Use my permissions', which is the default) or in read-only mode.
evidence: The Pulumi product announcement blog says the same thing: "When you create a Neo task, you now choose between two permission levels: | **Use my permissions** | Full access (current default behavior) | ... | **Read-only** |". Neo's…; source: repo:content/blog/neo-read-only-mode/index.md (gh api repos/pulumi/docs/contents/content/blog/neo-read-only-mode/index.md)
source: repo:content/blog/neo-read-only-mode/index.md (gh api repos/pulumi/docs/contents/content/blog/neo-read-only-mode/index.md)
pass1 · behavior · medium confidence
#221
✅ Verified
content/docs/ai/get-started/neo.md:42
Neo's read-only mode is scoped to Pulumi Cloud and does not, on its own, prevent Neo from opening ESC environments the user can open or reaching the cloud…
framing: The /docs/esc/ link only points to the ESC product. The claim's substance comes from the permissions#esc-secrets-and-downstream-cloud-access page linked in…; evidence: This line matches the canonical Neo permissions page the claim links to: "Read-only mode blocks writes in Pulumi Cloud and instructs Neo not to make modifications, but it does not technically prevent Neo from opening ESC environments or…; source: repo:content/docs/ai/concepts/neo/permissions.md L62-L68
source: repo:content/docs/ai/concepts/neo/permissions.md L62-L68
framing: exact-match — The /docs/esc/ link only points to the ESC product. The claim's substance comes from the permissions#esc-secrets-and-downstream-cloud-access page linked in the same sentence, and it restates that page closely.
pass1 · url · low confidence
#223
✅ Verified
content/docs/ai/get-started/neo.md:48
Pulumi Neo is included in the Essentials, Pro, and Enterprise editions of Pulumi Cloud and is on by default.
evidence: The canonical editions data lists `id: neo, name: Pulumi Neo, min_edition: essentials`, with editions in the order free → essentials → pro → enterprise. So Neo is included in Essentials, Pro, and Enterprise. I couldn't independently…; source: repo:data/pulumi_editions.yaml (lines 12-20, 194-196); intuition: "On by default" isn't backed by any independent source. Only the reviewed page says it, so a reviewer may want to…
source: repo:data/pulumi_editions.yaml (lines 12-20, 194-196)
pass1 · entity-spec · medium confidence
#224
✅ Verified
content/docs/ai/get-started/neo.md:48
Organizations on the Free edition, or on legacy Starter, Pro, or per-stack plans that predate the current editions, need to move to a paid edition to use Neo.
evidence: (escalated from pass3) The canonical editions data lists Neo as `min_edition: essentials` ("id: neo / name: Pulumi Neo / min_edition: essentials"), so Free-edition orgs do need to move to a paid edition. I found nothing in the repo or…; source: repo:data/pulumi_editions.yaml L194-196; intuition: The legacy-plan exclusion (Starter/Pro/per-stack) has no source in the repo. It's worth checking with the…
source: repo:data/pulumi_editions.yaml L194-196
pass1 · entity-spec · medium confidence
#225
✅ Verified
content/docs/ai/get-started/neo.md:51
In Pulumi Cloud, Neo is accessed by clicking 'Agent Tasks' within the 'Neo' section in the left navigation menu.
evidence: (escalated from pass1) A separate Pulumi docs page, the Neo get-started page at /docs/ai/neo/get-started/, gives the same step: "Click on Agent Tasks within the Neo section in the left navigation menu." The tasks page also says tasks…; source: https://www.pulumi.com/docs/ai/neo/get-started/; intuition: The cited page may be the pre-move published copy of the file under review, which would make it circular rather than…
source: https://www.pulumi.com/docs/ai/neo/get-started/
pass3 · behavior · low confidence
#227
✅ Verified
content/docs/ai/get-started/neo.md:57
Each conversation with Neo is called a 'task'.
evidence: The Neo Tasks concept page agrees: "Tasks are Neo's primary unit of work. Each task is a conversation where you describe what you want to accomplish, and Neo handles the infrastructure changes." This only shows the two pages are…; source: repo:content/docs/ai/concepts/neo/tasks.md#L19
source: repo:content/docs/ai/concepts/neo/tasks.md#L19
pass1 · behavior · medium confidence
#228
✅ Verified
content/docs/ai/get-started/neo.md:59
A Neo tasks concept page exists at /docs/ai/concepts/neo/tasks/.
evidence: content/docs/ai/concepts/neo/tasks.md exists, so it renders at /docs/ai/concepts/neo/tasks/. Its front matter reads "title: Tasks", "h1: Tasks in Pulumi Neo".; source: repo:content/docs/ai/concepts/neo/tasks.md
source: repo:content/docs/ai/concepts/neo/tasks.md
pass1 · url · high confidence
#231
✅ Verified
content/docs/ai/get-started/neo.md:87
Where Pulumi Cloud configuration (deployment settings, stack configuration, environment definitions) is managed in IaC, Neo changes it through code and pull…
framing: The source's general rule covers "anything you manage in IaC" vs. "anything you don't". The claim applies that rule to three examples: deployment settings…; evidence: The linked permissions page says Neo "makes changes two ways: through code and pull requests for anything you manage in IaC, and directly through the Pulumi Cloud APIs for anything you don't." Its table names deployment settings and ESC…; source: repo:content/docs/ai/concepts/neo/permissions.md L51-57; intuition: This only checks consistency with another Pulumi docs page, not product source. Stack configuration isn't named on…
source: repo:content/docs/ai/concepts/neo/permissions.md L51-57
framing: entailed-narrower — The source's general rule covers "anything you manage in IaC" vs. "anything you don't". The claim applies that rule to three examples: deployment settings, stack configuration and environment definitions.
pass1 · url · medium confidence
#232
✅ Verified
content/docs/ai/get-started/neo.md:88
Neo creates repositories as the user's own connected version control account, not as the shared Pulumi app, so individual access must be granted to the…
framing: Only other pulumi.com docs pages support this, not product source. On GitHub Enterprise Server with individual auth turned on, all Neo writes run as the…; evidence: Two other docs pages say the same thing. permissions.md L124 says: "Neo authenticates as the shared app installation for its VCS interactions... Creating a repository is the exception: that runs as your connected individual account…; source: repo:content/docs/ai/concepts/neo/permissions.md L122-133; repo:content/docs/integrations/version-control/github-app.md L138-142
source: repo:content/docs/ai/concepts/neo/permissions.md L122-133; repo:content/docs/integrations/version-control/github-app.md L138-142
framing: Only other pulumi.com docs pages support this, not product source. On GitHub Enterprise Server with individual auth turned on, all Neo writes run as the user, not just repo creation, but that doesn't contradict the claim.
pass1 · behavior · medium confidence
#233
✅ Verified
content/docs/ai/get-started/neo.md:88
The GitHub app integration page has an 'individual-user-setup' section at /docs/integrations/version-control/github-app/#individual-user-setup.
evidence: The target page has the heading "### Individual user setup" (L138), which Hugo turns into the anchor #individual-user-setup. That section covers granting individual access, which supports the link in neo.md L88 ("grant individual…; source: repo:content/docs/integrations/version-control/github-app.md L138-142
source: repo:content/docs/integrations/version-control/github-app.md L138-142
framing: exact-match
pass1 · cross-reference · high confidence
#234
✅ Verified
content/docs/ai/get-started/neo.md:88
Custom VCS servers do not support repository creation by Neo at all.
framing: This only shows that two Pulumi docs pages agree. Neither one is product source.; evidence: The dedicated Custom VCS docs page agrees with this claim: "Neo cannot open pull requests or create new repositories on Custom VCS servers at this time. Those operations require VCS-specific APIs only available through native…; source: repo:content/docs/integrations/version-control/custom-vcs.md L19, L211
source: repo:content/docs/integrations/version-control/custom-vcs.md L19, L211
framing: This only shows that two Pulumi docs pages agree. Neither one is product source.
pass1 · feature · medium confidence
#236
✅ Verified
content/docs/ai/guides/_index.md:5
A guide page exists at /docs/ai/guides/set-up-mcp-server/ titled 'Set up the MCP server' (cross-reference target of the Guides index).
framing: The front matter has title "MCP server", h1 "Pulumi Model Context Protocol server", and menu name "Set up the MCP server". The link text matches the menu name.; evidence: The file content/docs/ai/guides/set-up-mcp-server.md exists, so the URL /docs/ai/guides/set-up-mcp-server/ resolves. Its front matter has `name: Set up the MCP server` under `parent: ai-guides`, which matches the link text in the index.…; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: The front matter has title "MCP server", h1 "Pulumi Model Context Protocol server", and menu name "Set up the MCP server". The link text matches the menu name.
pass1 · url · high confidence
#237
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:17
The page is reachable via the alias /docs/ai/mcp-server/ (redirect from that path to the MCP server setup guide).
framing: This is a site-routing setting from the page's own front matter, not a claim about the product. I couldn't check whether a leftover page at…; evidence: The page's front matter `aliases:` list includes `- /docs/ai/mcp-server/` at L17. Hugo turns each alias into a redirect page, so that path will redirect to this guide. About 30 internal links across the repo still point to…; source: repo:content/docs/ai/guides/set-up-mcp-server.md L12-17; gh search code --repo pulumi/docs "/docs/ai/mcp-server/"
source: repo:content/docs/ai/guides/set-up-mcp-server.md L12-17; gh search code --repo pulumi/docs "/docs/ai/mcp-server/"
framing: This is a site-routing setting from the page's own front matter, not a claim about the product. I couldn't check whether a leftover page at content/docs/ai/mcp-server still exists in the PR branch, which would clash with the alias.
pass1 · url · medium confidence
#238
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:23
The page's content for the anchors 'tools', 'pulumi-cloud', 'neo', 'pulumi-registry', 'code-generation', and 'prompts' moved to the MCP server tools…
framing: Hugo auto-generated heading IDs (tools, pulumi-cloud, neo, pulumi-registry, code-generation, prompts) match the redirect list in the guide's script; evidence: The target page content/docs/ai/reference/mcp-server-tools.md exists and has headings for all six anchors: "## Tools", "### Pulumi Cloud", "### Neo", "### Pulumi Registry", "### Code generation", "## Prompts". The guide's own "## Tools…; source: repo:content/docs/ai/reference/mcp-server-tools.md L16-54
source: repo:content/docs/ai/reference/mcp-server-tools.md L16-54
framing: exact-match — Hugo auto-generated heading IDs (tools, pulumi-cloud, neo, pulumi-registry, code-generation, prompts) match the redirect list in the guide's script
pass1 · url · high confidence
#239
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:31
The Pulumi docs page /docs/ai/concepts/neo/ (Pulumi Neo) exists as a link target.
evidence: The file content/docs/ai/concepts/neo/_index.md exists, and its front matter includes "title: Pulumi Neo". That means it renders at /docs/ai/concepts/neo/, so the link target resolves.; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
pass1 · cross-reference · high confidence
#241
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:33
Pulumi hosts the MCP server at `https://mcp.ai.pulumi.com/mcp`, so there is nothing to install or run locally.
framing: This is a Pulumi blog page, not product source. I couldn't check product source because gh code search hit a rate limit and the pulumi/mcp-server repo wasn't…; evidence: The Pulumi Remote MCP Server launch blog says: "a hosted service ... Connect your favorite AI assistant to `https://mcp.ai.pulumi.com/mcp`" and "No installation required—just configure and connect." That matches the claim. The blog also…; source: repo:content/blog/remote-mcp-server/index.md L15, L35, L179
source: repo:content/blog/remote-mcp-server/index.md L15, L35, L179
framing: This is a Pulumi blog page, not product source. I couldn't check product source because gh code search hit a rate limit and the pulumi/mcp-server repo wasn't found.
pass1 · entity-spec · medium confidence
#242
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:36
An External MCP servers page exists at /docs/ai/integrations/external-mcp-servers/ describing connecting Neo to other services' MCP servers (Jira, Datadog…
evidence: The page content/docs/ai/integrations/external-mcp-servers.md exists, titled "External MCP Servers". It says: "This page is about connecting Neo to other services' MCP servers." It also lists "Atlassian (Jira and Confluence), Datadog…; source: repo:content/docs/ai/integrations/external-mcp-servers.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md
framing: exact-match
pass1 · url · high confidence
#243
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:162
The `resource-search` MCP tool relies on Pulumi resource search, which is available in the Pulumi Cloud editions listed by the 'resource-search' editions…
framing: The source_hint (/docs/ai/concepts/neo/) belongs to the next table row (neo-bridge), not to this claim.; evidence: data/pulumi_editions.yaml has a matching entry, "id: resource-search / name: Resource search / min_edition: essentials", so the shortcode resolves to Essentials and higher editions. I couldn't confirm from source that the MCP…; source: repo:data/pulumi_editions.yaml (L149-151)
source: repo:data/pulumi_editions.yaml (L149-151)
framing: The source_hint (/docs/ai/concepts/neo/) belongs to the next table row (neo-bridge), not to this claim.
pass1 · entity-spec · medium confidence
#244
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:165
Pulumi Cloud admins can cap Neo spend with Neo usage limits, documented at /docs/ai/concepts/neo/usage-limits/.
framing: The page says "Admin or Billing Manager" can set limits. The claim mentions only admins, which is a correct subset. Also, limits only exist on paid plans.; evidence: The linked page is there and says "A Neo usage limit caps what your organization spends on Neo in a monthly billing period," and "Members with the **Admin** or **Billing Manager** role can view and change Neo usage limits." So admins can…; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
framing: entailed-narrower — The page says "Admin or Billing Manager" can set limits. The claim mentions only admins, which is a correct subset. Also, limits only exist on paid plans.
pass1 · feature · medium confidence
#248
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:167
In Cursor, the Pulumi MCP tool can be turned off under the **Tools & MCP** settings.
evidence: (escalated from pass1) Several recent third-party guides and Cursor forum threads confirm that you can toggle MCP servers on and off in Cursor Settings → Tools & MCP, e.g. "In Settings > Tools & MCP, you can toggle individual servers…; source: https://toolradar.com/blog/best-mcp-servers-cursor; https://forum.cursor.com/t/mcp-servers-configured-but-agent-cannot-use-their-tools/153150; https://cursor.com/docs/context/mcp; intuition: The official Cursor docs now point to a "Customize" sidebar instead of Settings → Tools & MCP, so the UI path may be…
source: https://toolradar.com/blog/best-mcp-servers-cursor; https://forum.cursor.com/t/mcp-servers-configured-but-agent-cannot-use-their-tools/153150; https://cursor.com/docs/context/mcp
pass3 · behavior · medium confidence
#250
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:193
Neo tasks started via the MCP server may fail to start if Neo is not enabled for the organization or the organization has reached its Neo usage limit.
framing: Source: Neo pauses for the whole org (or member) once the limit is reached. Claim: Neo tasks started through the MCP neo-bridge tool may fail to start. The…; evidence: The linked usage-limits page backs up the usage-limit half: "When the month's Neo usage reaches the limit, Neo pauses for the entire organization until usage resets at the start of the next billing period." It doesn't mention MCP, and I…; source: repo:content/docs/ai/concepts/neo/usage-limits.md
source: repo:content/docs/ai/concepts/neo/usage-limits.md
framing: entailed-narrower — Source: Neo pauses for the whole org (or member) once the limit is reached. Claim: Neo tasks started through the MCP neo-bridge tool may fail to start. The claim follows as a special case.
pass1 · url · medium confidence
#251
✅ Verified
content/docs/ai/guides/set-up-mcp-server.md:197
Pages exist at /docs/ai/concepts/agent-skills/ (Pulumi Agent Skills) and /docs/ai/concepts/neo/ (Pulumi Neo, described as Pulumi's infrastructure agent).
evidence: Both pages are in the repo. content/docs/ai/concepts/agent-skills.md has the h1 "Pulumi Agent Skills", and content/docs/ai/concepts/neo/_index.md has the h1 "Pulumi Neo" and says "Pulumi Neo is Pulumi's own infrastructure agent".; source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match
pass1 · url · high confidence
#253
✅ Verified
content/docs/ai/integrations/_index.md:18
// The MCP integrations content moved to /docs/ai/integrations/external-mcp-servers/.
evidence: The target page exists at content/docs/ai/integrations/external-mcp-servers.md (title "External MCP Servers"). Its front matter has aliases from the old MCP paths, "/docs/ai/integrations/mcp/" and "/docs/ai/neo/integrations/mcp/", which…; source: repo:content/docs/ai/integrations/external-mcp-servers.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md
pass1 · url · high confidence
#254
✅ Verified
content/docs/ai/integrations/_index.md:23
window.location.replace('/docs/ai/integrations/external-mcp-servers/#' + anchor);
evidence: The redirect target content/docs/ai/integrations/external-mcp-servers.md exists ("title: External MCP Servers"). Its headings (e.g. "## What you can do with MCP integrations", "## Credential storage", "### Datadog", "### Supabase") match…; source: repo:content/docs/ai/integrations/external-mcp-servers.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md
pass1 · url · high confidence
#255
✅ Verified
content/docs/ai/integrations/_index.md:30
[MCP integrations](/docs/ai/integrations/external-mcp-servers/) and [CLI integrations](/docs/ai/integrations/cli-integrations/) handle the first part. MCP…
evidence: Both link targets exist in the repo. external-mcp-servers.md (title "External MCP Servers") says MCP integrations give Neo access to "issue trackers, observability platforms, runbook wikis, and on-call tooling", which matches the link…; source: repo:content/docs/ai/integrations/external-mcp-servers.md; repo:content/docs/ai/integrations/cli-integrations.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md; repo:content/docs/ai/integrations/cli-integrations.md
framing: exact-match
pass1 · url · high confidence
#257
✅ Verified
content/docs/ai/integrations/cli-integrations.md:75
CLI integrations are configured by an organization administrator and are offered to every Neo task in the organization once enabled. Using one still takes…
framing: The linked page resolves and states the same admin-enablement and acting-user `pulumi env run` model. This is same-site corroboration only: I did not check…; evidence: The link target /docs/ai/concepts/neo/permissions/ exists (content/docs/ai/concepts/neo/permissions.md) and its L120 says the same thing: "an organization admin points a CLI at an ESC environment, and every task in the organization is…; source: repo:content/docs/ai/concepts/neo/permissions.md#L120
source: repo:content/docs/ai/concepts/neo/permissions.md#L120
framing: exact-match — The linked page resolves and states the same admin-enablement and acting-user `pulumi env run` model. This is same-site corroboration only: I did not check the behavior against product source.
pass1 · url · medium confidence
#259
✅ Verified
content/docs/ai/integrations/external-mcp-servers.md:17
MCP integrations connect Neo to external services that expose a [Model Context Protocol](https://modelcontextprotocol.io/) server — the same open standard…
framing: The anchor text "Model Context Protocol" links to the official MCP site, whose page title is "What is the Model Context Protocol (MCP)?"; evidence: The cited URL returns HTTP 200 and is the official MCP documentation home page, titled "What is the Model Context Protocol (MCP)? - Model Context Protocol Documentation". The link anchor "Model Context Protocol" matches the page. The…; source: https://modelcontextprotocol.io/
source: https://modelcontextprotocol.io/
framing: exact-match — The anchor text "Model Context Protocol" links to the official MCP site, whose page title is "What is the Model Context Protocol (MCP)?"
pass2 · url · high confidence
#260
✅ Verified
content/docs/ai/integrations/external-mcp-servers.md:20
> This page is about connecting Neo to other services' MCP servers. To connect your own AI agent (Claude Code, Cursor, and others) to Pulumi, see the [Pulumi…
evidence: The link target is the page content/docs/ai/guides/set-up-mcp-server.md, which exists in the repo. Its meta_desc reads "Connect Claude Code, Cursor, Windsurf, and other AI agents to Pulumi Cloud... with Pulumi's hosted Model Context…; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match
pass1 · url · high confidence
#262
✅ Verified
content/docs/ai/integrations/slack/index.md:17
Mention `@Neo` in any channel where Neo has been added to start a Neo [task](/docs/ai/concepts/neo/tasks/) without leaving Slack. The response lands in the…
framing: This is a URL claim: the anchor "task" links to the Neo Tasks concept page, which exists.; evidence: The link target is there: content/docs/ai/concepts/neo/tasks.md exists, so it serves /docs/ai/concepts/neo/tasks/. Its frontmatter reads "title: Tasks", "h1: Tasks in Pulumi Neo", which is what a link on the word "task" should point to.…; source: repo:content/docs/ai/concepts/neo/tasks.md
source: repo:content/docs/ai/concepts/neo/tasks.md
framing: exact-match — This is a URL claim: the anchor "task" links to the Neo Tasks concept page, which exists.
pass1 · url · high confidence
#263
✅ Verified
content/docs/ai/reference/_index.md:5
The page /docs/ai/reference/mcp-server-tools/ exists and documents the tools and prompts the Pulumi MCP server exposes.
evidence: content/docs/ai/reference/mcp-server-tools.md exists in the repo (menu parent ai-reference). Its meta_desc reads "Reference for the tools and prompts the Pulumi MCP server exposes to AI agents", and the page has Tools and Prompts sections.; source: repo:content/docs/ai/reference/mcp-server-tools.md
source: repo:content/docs/ai/reference/mcp-server-tools.md
framing: exact-match
pass1 · url · high confidence
#264
✅ Verified
content/docs/ai/reference/_index.md:5
The `pulumi neo` CLI command starts an interactive Neo session from the terminal.
framing: The source says "Start a Pulumi Neo agent task with local tool execution; TUI starts" and the claim says "starts an interactive Neo session from the…; evidence: The auto-generated CLI reference page says: "Start a Pulumi Neo agent task with local tool execution ... If no prompt is provided, the TUI starts and waits for your first message." It also lists a `-p/--print` non-interactive mode, which…; source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from pulumi/pulumi cobra)
source: repo:content/docs/iac/cli/commands/pulumi_neo.md (auto-generated from pulumi/pulumi cobra)
framing: entailed-narrower — The source says "Start a Pulumi Neo agent task with local tool execution; TUI starts" and the claim says "starts an interactive Neo session from the terminal". The claim restates the default interactive mode in other words.
pass1 · url · high confidence
#265
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:14
The Pulumi MCP server docs have a 'Costs and edition requirements' section at /docs/ai/guides/set-up-mcp-server/#costs-and-edition-requirements describing…
evidence: I found the section in set-up-mcp-server.md at L154: "## Costs and edition requirements". Its table lists each tool with "What they need" and "Cost" columns, and it opens with "What the tools need from your organization:", so the…; source: repo:content/docs/ai/guides/set-up-mcp-server.md#L154-L165
source: repo:content/docs/ai/guides/set-up-mcp-server.md#L154-L165
framing: exact-match
pass1 · url · high confidence
#266
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:18
Users do not call Pulumi MCP server tools directly; the user describes what they want and the agent picks the tool.
framing: This matches the spec's default model-controlled design. The absolute wording ("do not call directly") goes slightly further than the spec, which lets…; evidence: (escalated from pass1) The MCP spec says tools are model-controlled: "the language model can discover and invoke tools automatically based on its contextual understanding and the user's prompts." It also adds that "the protocol itself…; source: https://modelcontextprotocol.io/specification/2025-06-18/server/tools
source: https://modelcontextprotocol.io/specification/2025-06-18/server/tools
framing: This matches the spec's default model-controlled design. The absolute wording ("do not call directly") goes slightly further than the spec, which lets implementations expose tools in any interface pattern.
pass3 · behavior · medium confidence
#268
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:25
Pulumi resource search queries accept `package:aws` to match AWS package resources and `-.tags:` to match resources without tags.
framing: The cited concept page sends readers to the guide for syntax. The guide documents negation + existence in general terms, and `-.tags:` is a special case of…; evidence: The cited querying-resources page has no syntax examples itself, but it links to the Search resources guide, which documents both. On `package`, the guide says "This is `aws` for a resource of type `aws:s3/bucket:Bucket`" and gives the…; source: repo:content/docs/discovery-governance/guides/search-resources.md L141-153, L320-336 (linked from repo:content/docs/discovery-governance/concepts/discovery/querying-resources.md)
source: repo:content/docs/discovery-governance/guides/search-resources.md L141-153, L320-336 (linked from repo:content/docs/discovery-governance/concepts/discovery/querying-resources.md)
framing: entailed-narrower — The cited concept page sends readers to the guide for syntax. The guide documents negation + existence in general terms, and `-.tags:` is a special case of that. One nuance: existence queries skip empty `{}` tags, so `-.tags:` also…
pass1 · url · medium confidence
#269
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:26
| `get-policy-violations` | List [policy as code](/docs/discovery-governance/concepts/policy-as-code/) violations for your stacks. |
framing: The anchor "policy as code" links to the page titled "Policy as code".; evidence: The link target resolves: content/docs/discovery-governance/concepts/policy-as-code/_index.md exists with title "Policy as code" and covers policy violations. That fits the anchor text for get-policy-violations. I only checked that the…; source: repo:content/docs/discovery-governance/concepts/policy-as-code/_index.md
source: repo:content/docs/discovery-governance/concepts/policy-as-code/_index.md
framing: exact-match — The anchor "policy as code" links to the page titled "Policy as code".
pass1 · url · high confidence
#271
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:35
The Pulumi MCP server exposes a `neo-reset-conversation` tool that clears the server's tracked state for a Neo task, or for all tasks.
evidence: (escalated from pass1) The tool exists. Pulumi's MCP server docs list "neo-reset-conversation - Reset the conversation context for Neo tasks", and third-party catalogs list it too (MintMCP: "Reset the Neo conversation for a specific…; source: https://www.pulumi.com/docs/ai/mcp-server/; https://www.mintmcp.com/servers/pulumi; intuition: The "or for all tasks" scope (presumably an optional taskId parameter) isn't in any public description. Check it…
source: https://www.pulumi.com/docs/ai/mcp-server/; https://www.mintmcp.com/servers/pulumi
pass3 · api-surface · medium confidence
#272
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:42
The Pulumi MCP server exposes a `list-resources` tool that lists the resource types in a Pulumi Registry provider or module.
evidence: (escalated from pass1) The pulumi/mcp-server source (mirrored on Glama) defines a 'list-resources' registry command described as "List all resource types for a given provider and module". It takes a required `provider` (a cloud provider…; source: https://glama.ai/mcp/servers/pulumi/mcp-server/tools/pulumi-registry-list-resources; https://hub.docker.com/r/mcp/pulumi; https://github.com/mcp-research/pulumi__mcp-server; intuition: The tool name depends on the deployment: the local npm/Docker server prefixes it as `pulumi-registry-list-resources`…
source: https://glama.ai/mcp/servers/pulumi/mcp-server/tools/pulumi-registry-list-resources; https://hub.docker.com/r/mcp/pulumi; https://github.com/mcp-research/pulumi__mcp-server
pass3 · api-surface · medium confidence
#273
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:52
The Pulumi MCP server exposes a `deploy-to-aws` tool that returns step-by-step instructions the agent follows to analyze the application and write Pulumi…
evidence: (escalated from pass1) The official Pulumi MCP server catalog lists a `deploy-to-aws` tool: "Deploy application code to AWS by generating Pulumi infrastructure... No prior analysis needed - just invoke directly." Third-party catalogs…; source: https://www.speakeasy.com/product/mcp-gateway/catalog/pulumi; https://archestra.ai/mcp-catalog/pulumi__mcp-server; WebSearch ran query "Pulumi MCP server deploy-to-aws tool"; intuition: The claim's mechanism (the tool returns instructions and the agent writes the code) is not stated directly in what I…
source: https://www.speakeasy.com/product/mcp-gateway/catalog/pulumi; https://archestra.ai/mcp-catalog/pulumi__mcp-server; WebSearch ran query "Pulumi MCP server deploy-to-aws tool"
pass3 · api-surface · medium confidence
#274
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:56
Pulumi MCP server prompts are reusable instructions the agent can load, usually from a slash-command or prompt menu.
framing: The spec says the user is the one who selects a prompt. "The agent can load" is a bit loose, but the slash-command/menu wording still points to a…; evidence: (escalated from pass1) The MCP spec describes prompts as server-provided templates that are "designed to be user-controlled, meaning they are exposed from servers to clients with the intention of the user being able to explicitly select…; source: https://modelcontextprotocol.io/specification/2025-03-26/server/prompts#user-interaction-model (quoted via https://mcpindotnet.github.io/docs/concepts/server-concepts/prompts/ and github.com/modelcontextprotocol/modelcontextprotocol/discussions/1097); intuition: "The agent can load" could be read as the model choosing prompts on its own, but the spec says prompts are…
source: https://modelcontextprotocol.io/specification/2025-03-26/server/prompts#user-interaction-model (quoted via https://mcpindotnet.github.io/docs/concepts/server-concepts/prompts/ and github.com/modelcontextprotocol/modelcontextprotocol/discussions/1097)
framing: The spec says the user is the one who selects a prompt. "The agent can load" is a bit loose, but the slash-command/menu wording still points to a user-triggered action.
pass3 · behavior · medium confidence
#275
✅ Verified
content/docs/ai/reference/mcp-server-tools.md:58
The Pulumi MCP server provides a prompt named `convert-terraform-to-typescript` that converts Terraform HCL to a Pulumi TypeScript program.
evidence: Pulumi's own Terraform-converter benchmark fetches this prompt by name from the published MCP server package and uses it to have Claude convert Terraform to TypeScript: `readMcpPrompt("@pulumi/mcp-server@latest"…; source: gh api repos/pulumi/pulumi-converter-terraform/contents/tests/benchmark/pul.go (L68-77)
source: gh api repos/pulumi/pulumi-converter-terraform/contents/tests/benchmark/pul.go (L68-77)
pass1 · api-surface · medium confidence
#276
✅ Verified
content/docs/discovery-governance/concepts/discovery/querying-resources.md:30
- **Natural language**: Ask a question in plain language, such as "How many VPCs do I have?", and Pulumi Cloud writes the search query for you. You can also…
evidence: The link target /docs/ai/concepts/neo/ resolves to content/docs/ai/concepts/neo/_index.md, which has "title: Pulumi Neo" and describes Neo as an agent that "investigates your live infrastructure, explains what it finds", so the link text…; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match
pass1 · url · high confidence
#277
✅ Verified
content/docs/discovery-governance/concepts/discovery/visual-import.md:22
1. **Visual Import generates code.** It writes a program in the language you choose: TypeScript, Python, Go, C#, Java, or YAML. You can have [Pulumi…
framing: Only the link was checked: the target page exists and is the Neo concept page. I did not verify the wording about Neo refining Visual Import code.; evidence: The link target /docs/ai/concepts/neo/ resolves to content/docs/ai/concepts/neo/_index.md, whose title is "Pulumi Neo". That matches the anchor text "Pulumi Neo".; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match — Only the link was checked: the target page exists and is the Neo concept page. I did not verify the wording about Neo refining Visual Import code.
pass1 · url · high confidence
#278
✅ Verified
content/docs/discovery-governance/get-started/explore-resources.md:62
AI Assist's queries are a starting point: review them, and refine the query if it doesn't quite match what you meant. To ask broader questions about your…
framing: The link text "Pulumi Neo" matches the target page's title, "Pulumi Neo".; evidence: The link target is real: /docs/ai/concepts/neo/ resolves to content/docs/ai/concepts/neo/_index.md, which has the title "Pulumi Neo" and the meta_desc "Pulumi Neo is a purpose-built infrastructure agent that investigates your live…; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match — The link text "Pulumi Neo" matches the target page's title, "Pulumi Neo".
pass1 · url · high confidence
#279
✅ Verified
content/docs/discovery-governance/guides/context-api.md:34
You can use [Pulumi Neo](/docs/ai/concepts/neo/), Claude Code, Cursor, Codex, or another agent that can run authenticated Pulumi CLI commands. Neo uses the…
framing: The anchor text "Pulumi Neo" matches the target page's title "Pulumi Neo".; evidence: The link target /docs/ai/concepts/neo/ resolves to content/docs/ai/concepts/neo/_index.md, which has "title: Pulumi Neo", so the link points to the page the anchor names. This check covers only the link. The separate statement that "Neo…; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match — The anchor text "Pulumi Neo" matches the target page's title "Pulumi Neo".
pass1 · url · high confidence
#280
✅ Verified
content/docs/get-started/_index.md:74
To go further with agents, see [Agent Skills](/docs/ai/concepts/agent-skills/), the [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/), and [Pulumi…
framing: Each link points to the page its anchor text names, and "purpose-built infrastructure agent" is word-for-word from the Neo page's meta_desc.; evidence: I checked all three internal links and each one resolves to an existing page: content/docs/ai/concepts/agent-skills.md ("title: Agent Skills"), content/docs/ai/guides/set-up-mcp-server.md ("h1: Pulumi Model Context Protocol server") and…; source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md; repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md; repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match — Each link points to the page its anchor text names, and "purpose-built infrastructure agent" is word-for-word from the Neo page's meta_desc.
pass1 · url · high confidence
#281
✅ Verified
content/docs/iac/cli/direct-resource-operations/get-started.md:177
Keeping this same command shape and output format across all Pulumi providers makes `pulumi do` work especially well for coding agents, too. See [Pulumi CLI…
framing: Only the link was checked: it resolves to a page about using `pulumi do` with agents. The page says commands are "generated dynamically from each provider's…; evidence: The link target is there: content/docs/ai/concepts/cli-for-agents.md lives at /docs/ai/concepts/ (old alias /docs/ai/cli-for-agents/). It covers `pulumi do` for agents: "`pulumi do` writes structured JSON to stdout as well, with progress…; source: repo:content/docs/ai/concepts/cli-for-agents.md
source: repo:content/docs/ai/concepts/cli-for-agents.md
framing: entailed-narrower — Only the link was checked: it resolves to a page about using `pulumi do` with agents. The page says commands are "generated dynamically from each provider's schema". That fits the "same command shape across all Pulumi providers" wording…
pass1 · url · high confidence
#283
✅ Verified
content/docs/iac/comparisons/tacos.md:51
| AI and agents | [Pulumi Neo](/product/neo/), the [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/), and [Agent Skills](/docs/ai/concepts/agent-skills/)…
framing: Internal link target; the product page isn't built in this repo, so I couldn't check it directly. Verified only by consistent internal usage and the redirect…; evidence: This repo has no page at /product/neo/. The path is still used as a link target in many pulumi/docs pages, the home-b layout, and the registry theme. In pulumi/docs infrastructure/cloudfrontLambdaAssociations.ts it is also a redirect…; source: gh search code --owner pulumi "/product/neo/"; repo:infrastructure/cloudfrontLambdaAssociations.ts
source: gh search code --owner pulumi "/product/neo/"; repo:infrastructure/cloudfrontLambdaAssociations.ts
framing: Internal link target; the product page isn't built in this repo, so I couldn't check it directly. Verified only by consistent internal usage and the redirect target.
pass1 · url · medium confidence
#284
✅ Verified
content/docs/iac/comparisons/tacos.md:77
AI is arriving across the category. Spacelift has added [Intelligence and Intent](https://spacelift.io/platform/intelligence) for natural-language…
framing: The page confirms Spacelift Intelligence as an AI-assisted deployment product. The "Intent" product name and the natural-language provisioning detail aren't…; evidence: The cited page loads (HTTP 200) and is titled "AI-assisted Deployment | Spacelift Intelligence". It also says "Spacelift Intelligence Now Deploys Modules Straight From Your Module Registry", which supports the claim that Spacelift has…; source: https://spacelift.io/platform/intelligence
source: https://spacelift.io/platform/intelligence
framing: exact-match — The page confirms Spacelift Intelligence as an AI-assisted deployment product. The "Intent" product name and the natural-language provisioning detail aren't in the truncated excerpt.
pass2 · url · medium confidence
#285
✅ Verified
content/docs/iac/comparisons/terraform-cloud.md:48
| AI assistance | [Pulumi Neo](/docs/ai/), [Agent Skills](/docs/ai/concepts/agent-skills/), and the [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/) |…
evidence: All three internal links resolve to existing pages whose content matches their anchors: content/docs/ai/_index.md (title "Infrastructure AI", which mentions Neo), content/docs/ai/concepts/agent-skills.md (title "Agent Skills"), and…; source: repo:content/docs/ai/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match
pass1 · url · high confidence
#286
✅ Verified
content/docs/iac/comparisons/terraform-cloud.md:68
* Terraform-managed resources appear in [Pulumi Discovery](/docs/discovery-governance/) alongside Pulumi-managed ones, and…
framing: The Discovery page covers resources from Pulumi, Terraform, CloudFormation, and manual creation, so the claim that Terraform-managed resources appear…; evidence: The linked /docs/discovery-governance/ page exists (content/docs/discovery-governance/_index.md) and says: "Pulumi Cloud provides complete visibility and control over your cloud infrastructure, whether resources were provisioned by…; source: repo:content/docs/discovery-governance/_index.md; repo:content/docs/ai/concepts/neo/code-reviews.md; intuition: Nothing on the linked Neo code-reviews page backs the second part, that Neo can review Terraform/OpenTofu pull…
source: repo:content/docs/discovery-governance/_index.md; repo:content/docs/ai/concepts/neo/code-reviews.md
framing: entailed-narrower — The Discovery page covers resources from Pulumi, Terraform, CloudFormation, and manual creation, so the claim that Terraform-managed resources appear alongside Pulumi-managed ones is a special case.
pass1 · url · medium confidence
#287
✅ Verified
content/docs/iac/comparisons/terraform-cloud.md:155
Yes. Coding agents such as Claude Code, Codex, Cursor, and GitHub Copilot can write Pulumi programs, and [Agent Skills](/docs/ai/concepts/agent-skills/) and…
framing: The link targets resolve, and the descriptions of skills and MCP as sources of Pulumi-specific context match what those pages say.; evidence: Both linked targets exist in the repo: the agent-skills.md page ("Pulumi Agent Skills are knowledge packages that teach AI coding assistants domain-specific Pulumi workflows") lists Claude Code, OpenAI Codex, Cursor, and GitHub Copilot…; source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — The link targets resolve, and the descriptions of skills and MCP as sources of Pulumi-specific context match what those pages say.
pass1 · url · high confidence
#288
✅ Verified
content/docs/iac/concepts/converters.md:16
For most conversions, using an LLM is the recommended first option. [Pulumi Neo](/docs/ai/), part of Pulumi Cloud, can convert your infrastructure code using…
framing: Neo's own page is /docs/ai/concepts/neo/, so linking the "Pulumi Neo" text to it may fit better. The "recommended first option" line is an editorial…; evidence: Both link targets exist. The agent-skills page says Neo "ships with the Pulumi Agent Skills catalog built in" and that catalog includes "pulumi-terraform-to-pulumi | Migrate Terraform projects to Pulumi". /docs/ai/ is the Infrastructure…; source: repo:content/docs/ai/concepts/agent-skills.md L33-L49; repo:content/docs/ai/_index.md
source: repo:content/docs/ai/concepts/agent-skills.md L33-L49; repo:content/docs/ai/_index.md
framing: entailed-narrower — Neo's own page is /docs/ai/concepts/neo/, so linking the "Pulumi Neo" text to it may fit better. The "recommended first option" line is an editorial recommendation, not a checkable fact.
pass1 · url · medium confidence
#289
✅ Verified
content/docs/iac/operations/stack-management/drift.md:106
A task description as direct as *"Adopt the drift on the `production` stack into the program"* is enough to get Neo started. By default Neo runs in [Review…
framing: Source: Review mode (the default) requires approval for preview, up, and PR. The claim names only up and PR, which is a subset the source proves.; evidence: The link target exists and has a "## Task modes" heading, so #task-modes resolves. It says: "**Review mode** (default): Neo requires approval before running `pulumi preview`, running `pulumi up`, and opening a pull request."; source: repo:content/docs/ai/concepts/neo/tasks.md#L54-L60
source: repo:content/docs/ai/concepts/neo/tasks.md#L54-L60
framing: entailed-narrower — Source: Review mode (the default) requires approval for preview, up, and PR. The claim names only up and PR, which is a subset the source proves.
pass1 · url · high confidence
#290
✅ Verified
content/docs/iac/operations/stack-management/drift.md:175
- [Pulumi Neo tasks](/docs/ai/concepts/neo/tasks/) — let Neo handle the code-edit step of adoption.
framing: The page describes tasks in general, covering code changes and PRs. The claim applies that to the code-edit step of adoption, which is a special case.; evidence: The link target exists at content/docs/ai/concepts/neo/tasks.md, titled "Tasks in Pulumi Neo". It says tasks are where "Neo handles the infrastructure changes", including "Create code changes" and opening PRs, so describing it as letting…; source: repo:content/docs/ai/concepts/neo/tasks.md
source: repo:content/docs/ai/concepts/neo/tasks.md
framing: entailed-narrower — The page describes tasks in general, covering code changes and PRs. The claim applies that to the code-edit step of adoption, which is a special case.
pass1 · url · high confidence
#291
✅ Verified
content/docs/install/_index.md:666
You can also connect your assistant to the [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/) for live access to your Pulumi Cloud stacks, resources…
framing: The target page says the server gives access to stacks, resources, and the Registry, which is what the link text says.; evidence: The link target is there: content/docs/ai/guides/set-up-mcp-server.md is the MCP server page. It says that "an agent can list your stacks, search your resources, check policy violations, look up resource schemas in the Pulumi Registry"…; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — The target page says the server gives access to stacks, resources, and the Registry, which is what the link text says.
pass1 · url · high confidence
#292
✅ Verified
content/docs/integrations/terraform/convert-hcl.md:1230
For most conversions, use a coding agent rather than `pulumi convert`. The converter is deterministic, so it handles what it recognizes and leaves a TODO for…
framing: This check only confirms that the link target exists and is relevant. The converter-behavior assertions (TODOs for for_each/dynamic blocks) are not checked…; evidence: The link target /docs/ai/concepts/neo/ resolves to content/docs/ai/concepts/neo/_index.md, which describes "Pulumi Neo is a purpose-built infrastructure agent that ... can propose changes to your IaC code." That fits the "coding agent"…; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: entailed-narrower — This check only confirms that the link target exists and is relevant. The converter-behavior assertions (TODOs for for_each/dynamic blocks) are not checked against this link.
pass1 · url · high confidence
#293
✅ Verified
content/docs/integrations/terraform/convert-hcl.md:1232
Whichever agent you use, the [Pulumi MCP (Model Context Protocol) server](/docs/ai/guides/set-up-mcp-server/) gives it access to the Pulumi Registry, your…
framing: The link target exists (set-up-mcp-server.md has the alias /docs/ai/mcp-server/). Registry and stacks access are stated on that page, and the prompt name is…; evidence: The linked MCP page says the server lets an agent "list your stacks... look up resource schemas in the Pulumi Registry," and mentions "reusable prompts for deployment and migration work." Product source confirms the prompt exists…; source: repo:content/docs/ai/guides/set-up-mcp-server.md L31,L171; gh search code --owner pulumi convert-terraform-to-typescript (pulumi/pulumi-converter-terraform:tests/benchmark/pul.go)
source: repo:content/docs/ai/guides/set-up-mcp-server.md L31,L171; gh search code --owner pulumi convert-terraform-to-typescript (pulumi/pulumi-converter-terraform:tests/benchmark/pul.go)
framing: exact-match — The link target exists (set-up-mcp-server.md has the alias /docs/ai/mcp-server/). Registry and stacks access are stated on that page, and the prompt name is confirmed in pulumi product code.
pass1 · url · high confidence
#294
✅ Verified
content/docs/integrations/terraform/convert-hcl.md:1236
The [Pulumi MCP server](/docs/ai/guides/set-up-mcp-server/) works with any agent that speaks MCP, including [Claude Code](https://www.anthropic.com/claude-code…
framing: The link text 'Claude Code' points to Anthropic's Claude Code product page.; evidence: The cited Claude Code link resolves (HTTP 200) to Anthropic's product page, titled "Claude Code by Anthropic | AI Coding Agent, Terminal, IDE", so the link target is correct. This page doesn't cover the other assertions in the sentence…; source: https://www.anthropic.com/claude-code
source: https://www.anthropic.com/claude-code
framing: exact-match — The link text 'Claude Code' points to Anthropic's Claude Code product page.
pass2 · url · high confidence
#295
✅ Verified
content/docs/integrations/terraform/convert-hcl.md:1238
Beyond conversion, the server exposes tools for listing your stacks, searching your deployed resources, reading Registry schemas, checking policy findings…
framing: The tool descriptions match the linked page. But "The MCP server docs list every tool" points to the setup guide, which hands the full list off to…; evidence: Both link targets exist (content/docs/ai/concepts/neo/_index.md, "Pulumi Neo"; content/docs/ai/guides/set-up-mcp-server.md). The MCP page says an agent "can list your stacks, search your resources, check policy violations, look up…; source: repo:content/docs/ai/guides/set-up-mcp-server.md L31, L171; repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md L31, L171; repo:content/docs/ai/concepts/neo/_index.md
framing: entailed-narrower — The tool descriptions match the linked page. But "The MCP server docs list every tool" points to the setup guide, which hands the full list off to /docs/ai/reference/mcp-server-tools/. Linking to the reference page would be more exact.
pass1 · url · medium confidence
#296
✅ Verified
content/docs/integrations/terraform/convert-hcl.md:1248
Other agents configure it differently — see [Configuration](/docs/ai/guides/set-up-mcp-server/#configuration) in the MCP server docs.
framing: The link resolves to a "Configuration" section that sets up the MCP server separately for each agent, which matches "Other agents configure it differently".; evidence: The target page content/docs/ai/guides/set-up-mcp-server.md exists and has a "## Configuration" heading at L38, which produces the #configuration anchor. That section covers how to set up each agent: Claude Code, Cursor, Claude Desktop…; source: repo:content/docs/ai/guides/set-up-mcp-server.md#L38-L105
source: repo:content/docs/ai/guides/set-up-mcp-server.md#L38-L105
framing: exact-match — The link resolves to a "Configuration" section that sets up the MCP server separately for each agent, which matches "Other agents configure it differently".
pass1 · url · high confidence
#297
✅ Verified
content/docs/integrations/version-control/azure-devops-integration.md:111
These comments come from Pulumi Deployments. [Neo code reviews](/docs/ai/concepts/neo/code-reviews/), which analyze a pull request and leave inline feedback…
framing: The linked page carries the same GitHub-only availability and inline-feedback statements. It is a same-site page, and I did not check product source.; evidence: The linked page exists and says: "Neo code reviews run on GitHub.com. They are not available on Azure DevOps, GitLab, or Bitbucket, where pull request comments come from the version control integration rather than from Neo." It also says…; source: repo:content/docs/ai/concepts/neo/code-reviews.md#L25-L39
source: repo:content/docs/ai/concepts/neo/code-reviews.md#L25-L39
framing: exact-match — The linked page carries the same GitHub-only availability and inline-feedback statements. It is a same-site page, and I did not check product source.
pass1 · url · medium confidence
#298
✅ Verified
content/docs/integrations/version-control/bitbucket.md:82
These comments come from Pulumi Deployments. [Neo code reviews](/docs/ai/concepts/neo/code-reviews/), which analyze a pull request and leave inline feedback…
framing: "Available on GitHub only" fits the source's "run on GitHub.com", but the source also excludes GitHub Enterprise Server, which the claim leaves out. This was…; evidence: The linked page exists and says the same thing: "Neo code reviews run on GitHub.com. They are not available on Azure DevOps, GitLab, or Bitbucket, where pull request comments come from the version control integration rather than from…; source: repo:content/docs/ai/concepts/neo/code-reviews.md
source: repo:content/docs/ai/concepts/neo/code-reviews.md
framing: exact-match — "Available on GitHub only" fits the source's "run on GitHub.com", but the source also excludes GitHub Enterprise Server, which the claim leaves out. This was checked against a Pulumi docs page only, not product source.
pass1 · url · medium confidence
#299
✅ Verified
content/docs/integrations/version-control/github-app.md:142
Individual access lets Pulumi create repositories on your behalf — for example, cloning project templates into a new repository or letting [Neo](/docs/ai/)…
framing: The anchor text 'Neo' links to the general Infrastructure AI landing page, not the dedicated Neo page (/docs/ai/concepts/neo/).; evidence: The link target /docs/ai/ exists (content/docs/ai/_index.md) and covers Neo: "Pulumi works with the AI agents you already use and provides Neo, a purpose-built infrastructure agent". A more specific Neo page also exists at…; source: repo:content/docs/ai/_index.md; intuition: Consider linking 'Neo' to /docs/ai/concepts/neo/ instead of the general AI landing page.
source: repo:content/docs/ai/_index.md
framing: entailed-narrower — The anchor text 'Neo' links to the general Infrastructure AI landing page, not the dedicated Neo page (/docs/ai/concepts/neo/).
pass1 · url · high confidence
#301
✅ Verified
content/docs/integrations/version-control/gitlab.md:81
These comments come from Pulumi Deployments. [Neo code reviews](/docs/ai/concepts/neo/code-reviews/), which analyze a pull request and leave inline feedback…
framing: Small nuance: the claim says "GitHub only," but the source says "GitHub.com" and notes GitHub Enterprise Server is not supported. The GitLab exclusion…; evidence: The linked page resolves and backs the claim: "Neo code reviews run on GitHub.com. They are not available on Azure DevOps, GitLab, or Bitbucket, where pull request comments come from the version control integration rather than from Neo."…; source: repo:content/docs/ai/concepts/neo/code-reviews.md L25, L39
source: repo:content/docs/ai/concepts/neo/code-reviews.md L25, L39
framing: exact-match — Small nuance: the claim says "GitHub only," but the source says "GitHub.com" and notes GitHub Enterprise Server is not supported. The GitLab exclusion matches exactly. This is a same-site docs page, not product source, so confidence is…
pass1 · url · medium confidence
#302
✅ Verified
content/docs/support/faq/pulumi-cloud.md:165
[Pulumi Discovery](/docs/discovery-governance/concepts/discovery/), and [Pulumi Neo](/docs/ai/concepts/neo/). [Contact us](/contact/?form=sales) to move to a
framing: The links point to existing internal docs pages whose titles match the anchor text.; evidence: Both link targets exist in the repo: content/docs/discovery-governance/concepts/discovery/_index.md (title: "Discovery") and content/docs/ai/concepts/neo/_index.md (title: "Pulumi Neo"). Each page's subject matches its link text.; source: repo:content/docs/discovery-governance/concepts/discovery/_index.md; repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/discovery-governance/concepts/discovery/_index.md; repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match — The links point to existing internal docs pages whose titles match the anchor text.
pass1 · url · high confidence
#303
✅ Verified
content/product/neo.md:35
Pulumi's code-first platform already works great with the coding agents your team loves — Claude Code, Codex, Cursor, and more — and our [agent…
framing: I only checked that the URL resolves and the linked page covers agent skills for these agents. The marketing line "the industry's first AI" infrastructure…; evidence: The link target is real: content/docs/ai/concepts/agent-skills.md exists (h1 "Pulumi Agent Skills"), so /docs/ai/concepts/agent-skills/ resolves. The page also says the skills "work with: ... Claude Code ... OpenAI Codex ... Cursor"…; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match — I only checked that the URL resolves and the linked page covers agent skills for these agents. The marketing line "the industry's first AI" infrastructure agent was not checked.
pass1 · url · high confidence
#304
✅ Verified
content/product/neo.md:117
cta_link: /docs/ai/concepts/neo/
evidence: The internal link target exists: content/docs/ai/concepts/neo/_index.md has the front matter "title: Pulumi Neo" and sits under the ai-concepts menu, so it renders at /docs/ai/concepts/neo/.; source: repo:content/docs/ai/concepts/neo/_index.md
source: repo:content/docs/ai/concepts/neo/_index.md
framing: exact-match
pass1 · url · high confidence
#305
✅ Verified
content/releases/agentic-infrastructure-era.md:165
link: /docs/ai/concepts/agent-skills/
evidence: The internal link target exists in the repo at content/docs/ai/concepts/agent-skills.md, titled "Agent Skills" (h1: "Pulumi Agent Skills"), so /docs/ai/concepts/agent-skills/ resolves.; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
pass1 · url · high confidence
#306
✅ Verified
content/releases/changelog/2026-06-22-neo-code-reviews.md:11
As of today, [Pulumi Neo code reviews](/docs/ai/concepts/neo/code-reviews/) are available in public preview.
framing: The linked page's preview note says the same thing as the changelog. This is a sibling page, not product source, so the launch date ("as of today") was not…; evidence: The link target is valid: content/docs/ai/concepts/neo/code-reviews.md is the page for /docs/ai/concepts/neo/code-reviews/. It also backs up the preview status: "Neo code reviews are currently in public preview and will be generally…; source: repo:content/docs/ai/concepts/neo/code-reviews.md
source: repo:content/docs/ai/concepts/neo/code-reviews.md
framing: exact-match — The linked page's preview note says the same thing as the changelog. This is a sibling page, not product source, so the launch date ("as of today") was not checked.
pass1 · url · medium confidence
#308
✅ Verified
content/releases/terraform-state-backend-modules-hcl.md:77
link: /docs/ai/concepts/neo/code-reviews/
evidence: The target page exists in the repo at content/docs/ai/concepts/neo/code-reviews.md (title: "Code reviews", h1: "Neo code reviews"), so the link resolves to /docs/ai/concepts/neo/code-reviews/.; source: repo:content/docs/ai/concepts/neo/code-reviews.md
source: repo:content/docs/ai/concepts/neo/code-reviews.md
pass1 · url · high confidence
#309
✅ Verified
content/state-of-agentic-infrastructure/_index.md:329
href: /docs/ai/integrations/external-mcp-servers/
evidence: The internal link target is in the repo at content/docs/ai/integrations/external-mcp-servers.md, so it builds to /docs/ai/integrations/external-mcp-servers/. Its front matter reads "title: External MCP Servers".; source: repo:content/docs/ai/integrations/external-mcp-servers.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md
pass1 · url · high confidence
#310
✅ Verified
content/state-of-agentic-infrastructure/_index.md:334
href: /docs/ai/concepts/agent-skills/
evidence: The internal link target is in the repo at content/docs/ai/concepts/agent-skills.md. Its title is "Agent Skills", it sits under the ai-concepts menu, and it has no redirect. So /docs/ai/concepts/agent-skills/ resolves to a live page.; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
pass1 · url · high confidence
#313
✅ Verified
content/what-is/mcp-for-infrastructure-as-code.md:144
[Neo](/product/neo/) is Pulumi's infrastructure engineering agent, and MCP is one of the ways it connects to the rest of your toolchain, alongside its own…
framing: This checks only the link: it resolves and the page calls Neo an infrastructure agent that connects through MCP. The rest of the sentence, about Neo's direct…; evidence: The /product/neo/ link resolves to content/product/neo.md, a live page titled "Pulumi Neo - Your AI Infrastructure Agent". The page supports the link text: it says "Meet Neo, your new AI infrastructure agent" and "Neo works inside VS…; source: repo:content/product/neo.md
source: repo:content/product/neo.md
framing: entailed-narrower — This checks only the link: it resolves and the page calls Neo an infrastructure agent that connects through MCP. The rest of the sentence, about Neo's direct integrations and granular MCP tools, was not checked against product source.
pass1 · url · high confidence
#314
✅ Verified
content/what-is/mcp-for-infrastructure-as-code.md:186
- [Pulumi MCP Server documentation](/docs/ai/guides/set-up-mcp-server/)
evidence: The internal link target is there: content/docs/ai/guides/set-up-mcp-server.md has h1 "Pulumi Model Context Protocol server" and the menu name "Set up the MCP server", so it matches the "Pulumi MCP Server documentation" link text.; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match
pass1 · url · high confidence
#315
✅ Verified
content/what-is/mcp-for-infrastructure-as-code.md:189
- [External MCP Servers for Neo](/docs/ai/integrations/external-mcp-servers/)
evidence: The target page is in the repo at content/docs/ai/integrations/external-mcp-servers.md, so it resolves to /docs/ai/integrations/external-mcp-servers/. Its frontmatter includes "title_tag: Neo External MCP Server Integrations", which…; source: repo:content/docs/ai/integrations/external-mcp-servers.md
source: repo:content/docs/ai/integrations/external-mcp-servers.md
framing: exact-match
pass1 · url · high confidence
#316
✅ Verified
content/what-is/mcp-for-infrastructure-as-code.md:190
- [CLI for AI Agents](/docs/ai/concepts/cli-for-agents/)
evidence: The target page exists in the repo at content/docs/ai/concepts/cli-for-agents.md, with frontmatter "title: CLI for agents" and "h1: The Pulumi CLI for agents". So the link resolves, and the anchor text matches the page.; source: repo:content/docs/ai/concepts/cli-for-agents.md
source: repo:content/docs/ai/concepts/cli-for-agents.md
framing: exact-match
pass1 · url · high confidence
#317
✅ Verified
content/what-is/what-is-agentic-infrastructure.md:58
**Your coding agent, equipped.** [Pulumi Agent Skills](/docs/ai/concepts/agent-skills/) teach agents proven Pulumi workflows (migrations, component…
framing: The link text matches what each target page covers. Migrations, component authoring, and secrets/ESC are all listed skill areas.; evidence: Both link targets exist in the repo. The agent-skills page says skills "help with infrastructure migrations, secret management, and code translation" and lists pulumi-component ("Guide for authoring ComponentResource classes"). The…; source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — The link text matches what each target page covers. Migrations, component authoring, and secrets/ESC are all listed skill areas.
pass1 · url · high confidence
#318
✅ Verified
content/what-is/what-is-agentic-infrastructure.md:62
The options compose. Teams often use Neo for scheduled, longer-horizon infrastructure work and their everyday coding agent for interactive development, and…
framing: Linked page: "Hand off in-progress work from coding agents to Pulumi Neo" vs claim: "hand off from one agent to Neo mid-session"; evidence: The link target exists. It has a Delegation plugin section, "Hand off in-progress work from coding agents to Pulumi Neo", which lists the `pulumi-neo-handoff` skill ("Transfer the current work to a Pulumi Neo task with goal, repository…; source: repo:content/docs/ai/concepts/agent-skills.md L79-85; gh api repos/pulumi/agent-skills/contents/delegation
source: repo:content/docs/ai/concepts/agent-skills.md L79-85; gh api repos/pulumi/agent-skills/contents/delegation
framing: exact-match — Linked page: "Hand off in-progress work from coding agents to Pulumi Neo" vs claim: "hand off from one agent to Neo mid-session"
pass1 · url · medium confidence
#319
✅ Verified
content/what-is/what-is-agentic-infrastructure.md:142
**Step 2: Pick your agent, or use both.** To work with the agent you already use, install [Pulumi Agent Skills](/docs/ai/concepts/agent-skills/) and connect…
evidence: The link target exists in the repo at content/docs/ai/concepts/agent-skills.md (h1 "Pulumi Agent Skills"). It has an "## Installation" section with install steps for agents like Claude Code, Codex and Gemini, so it fits "install Pulumi…; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match
pass1 · url · high confidence
#320
✅ Verified
content/what-is/what-is-agentic-infrastructure.md:176
No. Any coding agent can manage Pulumi infrastructure directly, and [Pulumi Agent Skills](/docs/ai/concepts/agent-skills/) and the [Pulumi MCP…
evidence: The link target is real: content/docs/ai/concepts/agent-skills.md exists at /docs/ai/concepts/agent-skills/ (it sits in the ai-concepts menu). The page says Agent Skills "teach AI coding assistants domain-specific Pulumi workflows" and…; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match
pass1 · url · high confidence
#321
✅ Verified
content/what-is/what-is-agentic-infrastructure.md:216
[The Agentic Infrastructure Era](/blog/the-agentic-infrastructure-era/) is Duffy's companion essay on where infrastructure is headed. [Grounded AI: Why Neo…
framing: Duffy is the author of the first post, so "Duffy's essay" holds up. Calling it a "companion essay on where infrastructure is headed" is a fair summary of a…; evidence: Both linked posts are live. /blog/the-agentic-infrastructure-era/ is a Joe Duffy post dated May 19, 2026, and it explains "Why infrastructure as code is the natural substrate for AI agents".…; source: https://www.pulumi.com/blog/the-agentic-infrastructure-era/ ; https://www.pulumi.com/blog/grounded-ai-why-neo-knows-your-infrastructure/
source: https://www.pulumi.com/blog/the-agentic-infrastructure-era/ ; https://www.pulumi.com/blog/grounded-ai-why-neo-knows-your-infrastructure/
framing: exact-match — Duffy is the author of the first post, so "Duffy's essay" holds up. Calling it a "companion essay on where infrastructure is headed" is a fair summary of a vision post. The second post does explain the context lake approach Neo uses.
pass3 · url · high confidence
#322
✅ Verified
content/what-is/what-is-ai-infrastructure.md:99
Pulumi's [MCP server](/docs/ai/guides/set-up-mcp-server/) and [Neo](/product/neo/) are built around that same principle: give an agent grounded access to…
framing: URL claim: the link resolves to the MCP server setup guide, which matches the anchor text.; evidence: The link target exists at content/docs/ai/guides/set-up-mcp-server.md (title "MCP server", menu "Set up the MCP server"), so the anchor text matches the page. The page says the server lets "an agent can list your stacks, search your…; source: repo:content/docs/ai/guides/set-up-mcp-server.md; intuition: The MCP page says the server "never runs `pulumi up`". So the "route what it proposes through the same preview and…
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — URL claim: the link resolves to the MCP server setup guide, which matches the anchor text.
pass1 · url · high confidence
#323
✅ Verified
content/what-is/what-is-an-internal-developer-platform.md:181
Code-first platforms have an edge here: agents reason far better about real programming languages than about bespoke DSLs or click-through UIs. Standards…
framing: This only checks the link target. The editorial point that agents reason better about real programming languages than about DSLs is opinion and wasn't verified.; evidence: The link target exists at content/docs/ai/guides/set-up-mcp-server.md. Its title is "Pulumi Model Context Protocol server" and the page says it "gives the AI agent you already use access to Pulumi", which fits the anchor text "Model…; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — This only checks the link target. The editorial point that agents reason better about real programming languages than about DSLs is opinion and wasn't verified.
pass1 · url · high confidence
#324
✅ Verified
data/glossary.toml:112
link = "/docs/ai/guides/set-up-mcp-server/"
evidence: The target file content/docs/ai/guides/set-up-mcp-server.md exists. It has no custom url override, so Hugo publishes it at /docs/ai/guides/set-up-mcp-server/. Its front matter reads "title: MCP server" with menu name "Set up the MCP…; source: repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/guides/set-up-mcp-server.md
pass1 · url · high confidence
#325
✅ Verified
data/glossary.toml:207
link = "/docs/ai/concepts/neo/tasks/"
evidence: The file content/docs/ai/concepts/neo/tasks.md exists in the repo, with "title: Tasks" and "h1: Tasks in Pulumi Neo". Hugo will render it at /docs/ai/concepts/neo/tasks/, so the glossary link resolves.; source: repo:content/docs/ai/concepts/neo/tasks.md
source: repo:content/docs/ai/concepts/neo/tasks.md
pass1 · url · high confidence
#326
✅ Verified
layouts/agent-start/list.html:15
<p class="mb-0 body-base text-center text-gray-primary">To go further with agents, see <a href="/docs/ai/concepts/agent-skills/">Agent Skills</a>, the <a…
evidence: The internal link /docs/ai/concepts/agent-skills/ goes to an existing page, content/docs/ai/concepts/agent-skills.md, whose front matter reads "title: Agent Skills". That matches the link text "Agent Skills".; source: repo:content/docs/ai/concepts/agent-skills.md
source: repo:content/docs/ai/concepts/agent-skills.md
framing: exact-match
pass1 · url · high confidence
#327
✅ Verified
layouts/index.llms.txt:77
- **Doing infrastructure work as an agent** — the Pulumi CLI is designed for agents: run any command with `npx pulumi`, perform one-shot resource operations…
framing: The link target exists and covers `pulumi do`. "One-shot resource operations" is a fair summary of "direct operations... without requiring a project…; evidence: The linked page exists in the repo at content/docs/iac/cli/direct-resource-operations/_index.md and documents `pulumi do`: "The `pulumi do` command provides direct operations on cloud resources through the Pulumi CLI without requiring a…; source: repo:content/docs/iac/cli/direct-resource-operations/_index.md
source: repo:content/docs/iac/cli/direct-resource-operations/_index.md
framing: exact-match — The link target exists and covers `pulumi do`. "One-shot resource operations" is a fair summary of "direct operations... without requiring a project, program, or state file" (stateful mode is the default, so "one-shot" is a loose but…
pass1 · url · high confidence
#328
✅ Verified
layouts/index.llms.txt:102
- [Infrastructure AI](https://www.pulumi.com/docs/ai/): Using AI agents with Pulumi — bring your own agent via [Agent Skills](https://www.pulumi.com/docs/ai/co…
framing: The link description matches the target page's own meta_desc.; evidence: All three link targets exist in the local repo: content/docs/ai/_index.md (title "Infrastructure AI", meta_desc: "Use AI agents with Pulumi. Bring Claude Code, Codex, or Cursor via Agent Skills and the MCP server, or use Neo")…; source: repo:content/docs/ai/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
source: repo:content/docs/ai/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md
framing: exact-match — The link description matches the target page's own meta_desc.
pass1 · url · high confidence
#329
✅ Verified
scripts/redirects/general-broken-links-redirects.txt:4
docs/iac/guides/ai-integration/index.html|/docs/ai/guides/set-up-mcp-server/
evidence: The redirect target exists at content/docs/ai/guides/set-up-mcp-server.md (title "MCP server"). Its aliases include "/docs/iac/guides/ai-integration/mcp-server/" and "/docs/ai/mcp-server/", so the target resolves. On the default branch…; source: repo:content/docs/ai/guides/set-up-mcp-server.md; gh search code --repo pulumi/docs "docs/iac/guides/ai-integration/"
source: repo:content/docs/ai/guides/set-up-mcp-server.md; gh search code --repo pulumi/docs "docs/iac/guides/ai-integration/"
pass1 · url · high confidence
#10
🤝 Matches
content/docs/ai/_index.md:25
The page links to /docs/ai/concepts/cli-for-agents/, /docs/iac/cli/direct-resource-operations/, /docs/ai/concepts/agent-skills/…
evidence: All six link targets exist in the repo as content pages: ai/concepts/cli-for-agents.md, iac/cli/direct-resource-operations/_index.md, ai/concepts/agent-skills.md, ai/guides/set-up-mcp-server.md, what-is/mcp-for-infrastructure-as-code.md…; source: repo:content/docs/ai/concepts/cli-for-agents.md; repo:content/docs/iac/cli/direct-resource-operations/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md; repo:content/what-is/mcp-for-infrastructure-as-code.md; repo:content/docs/administration/concepts/agent-accounts.md
source: repo:content/docs/ai/concepts/cli-for-agents.md; repo:content/docs/iac/cli/direct-resource-operations/_index.md; repo:content/docs/ai/concepts/agent-skills.md; repo:content/docs/ai/guides/set-up-mcp-server.md; repo:content/what-is/mcp-for-infrastructure-as-code.md; repo:content/docs/administration/concepts/agent-accounts.md
pass1 · cross-reference · high confidence
#45
🤝 Matches
content/docs/ai/concepts/neo/_index.md:44
Neo comments on pull requests using what Pulumi Cloud knows about your running infrastructure, flagging issues inline, and it never blocks the merge.
framing: The summary on the index page matches the linked page on all three points: it uses what Pulumi Cloud knows about running infrastructure, it comments inline…; evidence: The linked page says the same thing as the summary: "Neo code reviews analyze pull requests against what Pulumi Cloud knows about your running infrastructure and leave feedback in the pull request. They read the `pulumi preview` output…; source: repo:content/docs/ai/concepts/neo/code-reviews.md
source: repo:content/docs/ai/concepts/neo/code-reviews.md
framing: exact-match — The summary on the index page matches the linked page on all three points: it uses what Pulumi Cloud knows about running infrastructure, it comments inline, and it does not block the merge.
pass1 · url · high confidence
#56
🤝 Matches
content/docs/ai/concepts/neo/_index.md:74
Neo reviews pull requests automatically, and you can mention @pulumi-neo in a PR description, a review comment, or an issue to ask for something specific.
framing: The sibling page lists the same mention locations, but it presents mention-only reviews as a mode that replaces automatic reviews, not as something available…; evidence: The linked sibling page supports both parts: "By default, Neo reviews every pull request automatically, skipping drafts and pull requests opened by bots." It also says "Mention it in a pull request description, a review comment…; source: repo:content/docs/ai/concepts/neo/code-reviews.md; intuition: The sibling page doesn't say whether @pulumi-neo mentions also work while automatic reviews are on. Check the product…
source: repo:content/docs/ai/concepts/neo/code-reviews.md
framing: entailed-narrower — The sibling page lists the same mention locations, but it presents mention-only reviews as a mode that replaces automatic reviews, not as something available alongside them.
pass1 · url · medium confidence
#64
🤝 Matches
content/docs/ai/concepts/neo/automations.md:12
The Automations page's menu entry sits under the parent menu identifier 'ai-concepts-neo' in the AI menu.
evidence: The front matter of automations.md has `menu: ai: ... parent: ai-concepts-neo`. That identifier exists: the Neo section index (`content/docs/ai/concepts/neo/_index.md`) defines `identifier: ai-concepts-neo` in the `ai` menu, so the…; source: repo:content/docs/ai/concepts/neo/automations.md L9-13; repo:content/docs/ai/concepts/neo/_index.md L11-16
source: repo:content/docs/ai/concepts/neo/automations.md L9-13; repo:content/docs/ai/concepts/neo/_index.md L11-16
pass1 · cross-reference · high confidence
#78
🤝 Matches
content/docs/ai/concepts/neo/code-reviews.md:35
The Pulumi accounts documentation page has an 'adding new identities' section at /docs/administration/concepts/accounts/#adding-new-identities explaining how…
evidence: The accounts page has the heading `### Adding new identities {#adding-new-identities}` (L83). That section says "you can connect GitHub, GitLab, Google, Atlassian, and SAML SSO identities" and gives the steps to connect one from Account…; source: repo:content/docs/administration/concepts/accounts.md#L83-L93
source: repo:content/docs/administration/concepts/accounts.md#L83-L93
framing: exact-match
pass1 · cross-reference · high confidence
#85
🤝 Matches
content/docs/ai/concepts/neo/code-reviews.md:54
The GitHub App documentation page has a 'link an existing installation' section at /docs/integrations/version-control/github-app/#link-an-existing-installation.
evidence: The GitHub App page has the heading "### Link an existing installation" at line 48, which Hugo turns into the anchor #link-an-existing-installation. The page lives at content/docs/integrations/version-control/github-app.md, which matches…; source: repo:content/docs/integrations/version-control/github-app.md#L48
source: repo:content/docs/integrations/version-control/github-app.md#L48
pass1 · cross-reference · high confidence
#86
🤝 Matches
content/docs/ai/concepts/neo/instructions/index.md:1
The Neo Instructions docs page is located in the AI docs menu under parent ai-concepts-neo with identifier ai-instructions.
evidence: The page's front matter has `menu: ai: name: Instructions, parent: ai-concepts-neo, identifier: ai-instructions, weight: 50`. The parent exists: content/docs/ai/concepts/neo/_index.md declares `identifier: ai-concepts-neo` in the ai menu.; source: repo:content/docs/ai/concepts/neo/instructions/index.md L6-11; repo:content/docs/ai/concepts/neo/_index.md L11-16
source: repo:content/docs/ai/concepts/neo/instructions/index.md L6-11; repo:content/docs/ai/concepts/neo/_index.md L11-16
pass1 · cross-reference · high confidence
#101
🤝 Matches
content/docs/ai/concepts/neo/neo-in-the-cli.md:12
The docs menu parent identifier 'ai-concepts-neo' exists as a menu entry in the ai menu, under which 'Neo in the CLI' is nested.
evidence: In content/docs/ai/concepts/neo/_index.md, the `ai` menu defines "identifier: ai-concepts-neo" (name: Pulumi Neo, parent: ai-concepts). neo-in-the-cli.md lists "parent: ai-concepts-neo" under `menu: ai:`, so the page sits under that entry.; source: repo:content/docs/ai/concepts/neo/_index.md L11-16
source: repo:content/docs/ai/concepts/neo/_index.md L11-16
pass1 · cross-reference · high confidence
#106
🤝 Matches
content/docs/ai/concepts/neo/neo-in-your-editor.md:9
The Hugo menu parent identifier 'ai-concepts-neo' exists as a menu entry in the AI docs menu hierarchy.
evidence: The menu identifier exists: content/docs/ai/concepts/neo/_index.md declares `identifier: ai-concepts-neo` (parent: ai-concepts) under the `ai` menu. The sibling page neo-in-the-cli.md also uses `parent: ai-concepts-neo`, the same parent…; source: repo:content/docs/ai/concepts/neo/_index.md (L11-16); repo:content/docs/ai/concepts/neo/neo-in-the-cli.md (L9-14)
source: repo:content/docs/ai/concepts/neo/_index.md (L11-16); repo:content/docs/ai/concepts/neo/neo-in-the-cli.md (L9-14)
pass1 · cross-reference · high confidence
#110
🤝 Matches
content/docs/ai/concepts/neo/neo-in-your-editor.md:20
A Neo editor session runs locally and inherits the user's setup: their `pulumi login`, authenticated CLIs, environment variables and kubeconfigs, and the…
framing: The sibling page lists the same items (login, authenticated CLIs, env vars/kubeconfigs, project) for CLI sessions, and the editor page carries them over to…; evidence: The linked sibling page says the same thing: "Running locally means Neo inherits your setup: the CLIs you've authenticated, the environment variables and kubeconfigs you've configured, and the project you're editing." It also says…; source: repo:content/docs/ai/concepts/neo/neo-in-the-cli.md
source: repo:content/docs/ai/concepts/neo/neo-in-the-cli.md
framing: exact-match — The sibling page lists the same items (login, authenticated CLIs, env vars/kubeconfigs, project) for CLI sessions, and the editor page carries them over to ACP sessions through the "Like Neo in the CLI" comparison.
pass1 · url · medium confidence
#117
🤝 Matches
content/docs/ai/concepts/neo/permissions.md:24
Neo tasks are private to the user who created them; that user can share a task with the rest of the organization as a read-only link, viewers see the…
framing: This is a sibling-consistency check against a Pulumi docs page, not against product source. The claim's "the rest of the organization" is a close paraphrase…; evidence: The target anchor says the same thing: "By default, tasks are private, but you can share any task with others in your organization by generating a read-only link." It also says "Viewers can see the conversation but cannot trigger any…; source: repo:content/docs/ai/concepts/neo/tasks.md#L84-L92
source: repo:content/docs/ai/concepts/neo/tasks.md#L84-L92
framing: exact-match — This is a sibling-consistency check against a Pulumi docs page, not against product source. The claim's "the rest of the organization" is a close paraphrase of the source's "others in your organization."
pass1 · url · high confidence
#143
🤝 Matches
content/docs/ai/concepts/neo/permissions.md:130
Neo does not comment on Azure DevOps pull requests, GitLab merge requests, or Bitbucket pull requests; Neo code reviews are GitHub-only, and the…
framing: code-reviews.md credits the PR comments to "the version control integration"; gitlab.md and this claim name "Pulumi Deployments". The pages agree; I didn't…; evidence: The linked code-reviews page agrees: "Neo code reviews run on GitHub.com. They are not available on Azure DevOps, GitLab, or Bitbucket, where pull request comments come from the version control integration rather than from Neo." The…; source: repo:content/docs/ai/concepts/neo/code-reviews.md (Availability); repo:content/docs/integrations/version-control/gitlab.md L81
source: repo:content/docs/ai/concepts/neo/code-reviews.md (Availability); repo:content/docs/integrations/version-control/gitlab.md L81
framing: exact-match — code-reviews.md credits the PR comments to "the version control integration"; gitlab.md and this claim name "Pulumi Deployments". The pages agree; I didn't check product source.
pass1 · url · medium confidence
#164
🤝 Matches
content/docs/ai/concepts/neo/settings/index.md:77
Neo Settings has an 'Organization instructions' tab, and the 'General' tab has a slash commands section, which configure the standing guidance Neo follows.
framing: Sibling pages name the same tabs: 'Organization instructions' tab and 'General' tab → 'Slash commands' section.; evidence: The linked instructions page says "Navigate to Neo Settings in Pulumi Cloud / Select the \"Organization instructions\" tab". The slash-commands sibling page says "Select the \"General\" tab / Scroll to the \"Slash commands\" section". So…; source: repo:content/docs/ai/concepts/neo/instructions/index.md; repo:content/docs/ai/concepts/neo/slash-commands/index.md (L31-33)
source: repo:content/docs/ai/concepts/neo/instructions/index.md; repo:content/docs/ai/concepts/neo/slash-commands/index.md (L31-33)
framing: exact-match — Sibling pages name the same tabs: 'Organization instructions' tab and 'General' tab → 'Slash commands' section.
pass1 · url · medium confidence
#190
🤝 Matches
content/docs/ai/concepts/neo/slash-commands/index.md:39
The page references an image file slash-commands.png showing the Slash Commands configuration, which must exist alongside the page.
evidence: Line 39 of the page has ``. The file content/docs/ai/concepts/neo/slash-commands/slash-commands.png is in the same directory as the page: it's a valid PNG (IHDR header, about 58 KB), so…; source: repo:content/docs/ai/concepts/neo/slash-commands/slash-commands.png
source: repo:content/docs/ai/concepts/neo/slash-commands/slash-commands.png
pass1 · cross-reference · high confidence
#194
🤝 Matches
content/docs/ai/concepts/neo/tasks.md:14
The Tasks page menu entry has parent identifier ai-concepts-neo, which must exist as a menu identifier in the ai menu.
evidence: tasks.md declares `parent: ai-concepts-neo` in the ai menu. The sibling content/docs/ai/concepts/neo/_index.md defines `menu: ai: identifier: ai-concepts-neo` (L11-15), so the parent identifier exists.; source: repo:content/docs/ai/concepts/neo/_index.md (L11-16)
source: repo:content/docs/ai/concepts/neo/_index.md (L11-16)
pass1 · cross-reference · high confidence
#213
🤝 Matches
content/docs/ai/get-started/neo.md:24
The link target /docs/integrations/version-control/github-app/ exists as the GitHub integration page.
evidence: content/docs/integrations/version-control/github-app.md exists, so it renders at /docs/integrations/version-control/github-app/. Its front matter has title "Pulumi GitHub App" and the menu entry "name: GitHub" under…; source: repo:content/docs/integrations/version-control/github-app.md
source: repo:content/docs/integrations/version-control/github-app.md
pass1 · cross-reference · high confidence
#222
🤝 Matches
content/docs/ai/get-started/neo.md:48
Pulumi pricing information is at /pricing/.
evidence: L48 links "see [pricing](/pricing/)". That matches the site's standard pricing route, which pulumi/marketing-web builds from apps/www/src/data/pricing/. It's the same relative link pattern other docs pages use. I didn't fetch the live…; source: repo:content/docs/ai/get-started/neo.md L48; https://www.pulumi.com/pricing/
source: repo:content/docs/ai/get-started/neo.md L48; https://www.pulumi.com/pricing/
pass1 · cross-reference · medium confidence
#249
🤝 Matches
content/docs/ai/guides/set-up-mcp-server.md:171
The Pulumi MCP server exposes tools for Pulumi Cloud, Neo, the Pulumi Registry, and code generation, plus reusable prompts for deployment and migration work.
framing: Reference page meta_desc: "tools and prompts the Pulumi MCP server exposes to AI agents, covering Pulumi Cloud, Neo, the Pulumi Registry, and code generation"; evidence: The linked reference page lists tool sections "Pulumi Cloud", "Neo", "Pulumi Registry", and "Code generation", and a Prompts section with deploy-to-aws, convert-terraform-to-typescript, and the cdk-migration-* prompts. That matches how…; source: repo:content/docs/ai/reference/mcp-server-tools.md
source: repo:content/docs/ai/reference/mcp-server-tools.md
framing: exact-match — Reference page meta_desc: "tools and prompts the Pulumi MCP server exposes to AI agents, covering Pulumi Cloud, Neo, the Pulumi Registry, and code generation"
pass1 · url · medium confidence
#300
🤝 Matches
content/docs/integrations/version-control/github-app.md:160
[Neo code reviews](/docs/ai/concepts/neo/code-reviews/) are configured separately, under **Settings** > **Neo settings** > **Code reviews**, not in the…
framing: Link target resolves; the target page states the same settings path, "Settings > Neo settings > Code reviews".; evidence: The linked page exists, and its settings path matches the claim: "Confirm code reviews are enabled under **Settings** > **Neo settings** > **Code reviews**." The two pages agree with each other, but neither is product source, so this…; source: repo:content/docs/ai/concepts/neo/code-reviews.md L45, L50
source: repo:content/docs/ai/concepts/neo/code-reviews.md L45, L50
framing: exact-match — Link target resolves; the target page states the same settings path, "Settings > Neo settings > Code reviews".
pass1 · url · medium confidence
#32
➖ Not a claim
content/docs/ai/concepts/agent-skills.md:14
- /docs/ai/skills/
framing: Frontmatter alias (a redirect path), not a cited link; evidence: Line 14 is an entry under the page's frontmatter `aliases:` list (L12-14: `- /docs/ai/agent-skills/`, `- /docs/ai/skills/`). That makes it a Hugo redirect path pointing to this page, not a link to another page and not something that can…; source: repo:content/docs/ai/concepts/agent-skills.md#L12-L14
source: repo:content/docs/ai/concepts/agent-skills.md#L12-L14
framing: Frontmatter alias (a redirect path), not a cited link
pass1 · url · high confidence
#34
➖ Not a claim
content/docs/ai/concepts/cli-for-agents.md:13
The page previously at /docs/ai/cli-for-agents/ is aliased to the new location under ai-concepts.
framing: The claim describes the PR's own redirect/alias setup. It is not an assertion about a third party.; evidence: This line is the page's own alias metadata, not a factual claim. The frontmatter (L12-13) declares `aliases: - /docs/ai/cli-for-agents/`, and the menu sets `parent: ai-concepts`, so the alias exists exactly as described.; source: repo:content/docs/ai/concepts/cli-for-agents.md
source: repo:content/docs/ai/concepts/cli-for-agents.md
framing: The claim describes the PR's own redirect/alias setup. It is not an assertion about a third party.
pass1 · url · high confidence
#40
➖ Not a claim
content/docs/ai/concepts/neo/_index.md:10
The Pulumi Neo concepts page (docs/ai/concepts/neo/_index.md) declares /docs/ai/neo/ as an alias URL that redirects to it.
evidence: This describes the page's own front matter, not a factual statement about the product. The front matter does list it: line 10 under `aliases:` is "- /docs/ai/neo/", alongside /docs/pulumi-cloud/neo/, /docs/iac/neo/ and /docs/neo/, and…; source: repo:content/docs/ai/concepts/neo/_index.md#L6-L10
source: repo:content/docs/ai/concepts/neo/_index.md#L6-L10
pass1 · url · high confidence
#63
➖ Not a claim
content/docs/ai/concepts/neo/automations.md:8
The Neo Automations page is reachable via the alias /docs/ai/neo/automations/ in addition to /docs/ai/automations/.
framing: Both paths are aliases. The page itself lives at /docs/ai/concepts/neo/automations/, not at /docs/ai/automations/.; evidence: This line is the page's own Hugo front-matter alias. The `aliases:` list contains both `- /docs/ai/automations/` and `- /docs/ai/neo/automations/`, so both paths redirect to the page's actual URL, /docs/ai/concepts/neo/automations/. That…; source: repo:content/docs/ai/concepts/neo/automations.md L6-8
source: repo:content/docs/ai/concepts/neo/automations.md L6-8
framing: Both paths are aliases. The page itself lives at /docs/ai/concepts/neo/automations/, not at /docs/ai/automations/.
pass1 · url · high confidence
#70
➖ Not a claim
content/docs/ai/concepts/neo/code-reviews.md:11
- /docs/ai/neo/code-reviews/
evidence: L11 sits in the page's front-matter `aliases:` list (L6–L11), next to other old paths such as `/docs/ai/code-reviews/`. It sets up a redirect from the page's old URL, which is the PR author's own site-structure choice. It doesn't assert…; source: repo:content/docs/ai/concepts/neo/code-reviews.md#L6-L11
source: repo:content/docs/ai/concepts/neo/code-reviews.md#L6-L11
pass1 · url · high confidence
#96
➖ Not a claim
content/docs/ai/concepts/neo/instructions/index.md:104
- Tool requirements: Node.js 20+, Python 3.11+
evidence: This line sits inside a fenced markdown block (L99+) headed "# Project Instructions". It's a made-up sample of what a user might write in an instructions file, not a statement about what Neo or Pulumi actually requires.; source: repo:content/docs/ai/concepts/neo/instructions/index.md L97-112
source: repo:content/docs/ai/concepts/neo/instructions/index.md L97-112
pass1 · version · high confidence
#98
➖ Not a claim
content/docs/ai/concepts/neo/model-providers.md:13
- /docs/ai/neo/model-providers/
evidence: Line 13 sits in the page's Hugo frontmatter `aliases:` list. It sets up a redirect from the old path /docs/ai/neo/model-providers/ to this page. It doesn't assert any fact, and it isn't a link to an outside source that needs to resolve.; source: repo:content/docs/ai/concepts/neo/model-providers.md L12-13
source: repo:content/docs/ai/concepts/neo/model-providers.md L12-13
pass1 · url · high confidence
#100
➖ Not a claim
content/docs/ai/concepts/neo/neo-in-the-cli.md:8
The page 'Neo in the CLI' is reachable via the alias URL path /docs/ai/neo/pulumi-cli/ (redirect alias to this page).
framing: The claim just restates a redirect the page sets up for itself in its front matter.; evidence: (re-verified after own-file-only) This is the page's own Hugo front-matter alias (`aliases: - /docs/ai/neo/pulumi-cli/`). It is site configuration that the PR author wrote, not a statement about the product or anything outside the page…; source: repo:content/docs/ai/concepts/neo/neo-in-the-cli.md L6-8
source: repo:content/docs/ai/concepts/neo/neo-in-the-cli.md L6-8
framing: The claim just restates a redirect the page sets up for itself in its front matter.
pass1 · url · high confidence
#107
➖ Not a claim
content/docs/ai/concepts/neo/neo-in-your-editor.md:12
The page 'Neo in your editor (ACP)' is aliased from the old URL /docs/ai/neo/editors/ so that the old URL redirects to the new location.
framing: Self-description of page metadata (a Hugo alias), not a third-party assertion.; evidence: (re-verified after own-file-only) This is a description of the reviewed page's own front-matter `aliases` entry, i.e. how the PR author set up the redirect. It says nothing about the product or the outside world, so no independent source…; source: repo:content/docs/ai/concepts/neo/neo-in-your-editor.md (front matter L12-13)
source: repo:content/docs/ai/concepts/neo/neo-in-your-editor.md (front matter L12-13)
framing: Self-description of page metadata (a Hugo alias), not a third-party assertion.
pass1 · url · medium confidence
#114
➖ Not a claim
content/docs/ai/concepts/neo/permissions.md:9
The page menu parent is changed to ai-concepts-neo and an alias /docs/ai/neo/permissions/ is added.
evidence: This is diff metadata about front-matter edits, not a factual claim. The file does match it: L9 reads `parent: ai-concepts-neo` and L12-13 read `aliases: - /docs/ai/neo/permissions/`.; source: repo:content/docs/ai/concepts/neo/permissions.md
source: repo:content/docs/ai/concepts/neo/permissions.md
pass1 · url · high confidence
#147
➖ Not a claim
content/docs/ai/concepts/neo/previews/index.md:10
- /docs/ai/neo/running-previews/
evidence: The line is a Hugo frontmatter `aliases:` entry ("- /docs/ai/neo/running-previews/"). It sets up a redirect from an old path to this page. It does not link to a target page that has to exist, and it makes no factual assertion.; source: repo:content/docs/ai/concepts/neo/previews/index.md (frontmatter aliases, L6-10)
source: repo:content/docs/ai/concepts/neo/previews/index.md (frontmatter aliases, L6-10)
pass1 · url · high confidence
#148
➖ Not a claim
content/docs/ai/concepts/neo/pull-requests/index.md:10
- /docs/ai/neo/pull-requests/
evidence: Line 10 sits in the page's frontmatter `aliases:` list (lines 6–10). It's a redirect path the PR author set up for their own page, not a factual claim or an outbound link to check.; source: repo:content/docs/ai/concepts/neo/pull-requests/index.md#L6-L10
source: repo:content/docs/ai/concepts/neo/pull-requests/index.md#L6-L10
pass1 · url · high confidence
#150
➖ Not a claim
content/docs/ai/concepts/neo/settings/index.md:7
- /docs/ai/neo/settings/
evidence: The "claim" is a Hugo front-matter `aliases:` entry (`- /docs/ai/neo/settings/`, listed next to `/docs/ai/settings/`). It sets up a redirect path for the page and doesn't assert anything that can be checked as true or false.; source: repo:content/docs/ai/concepts/neo/settings/index.md (front matter, aliases L6-8)
source: repo:content/docs/ai/concepts/neo/settings/index.md (front matter, aliases L6-8)
pass1 · url · high confidence
#193
➖ Not a claim
content/docs/ai/concepts/neo/tasks.md:10
The Neo tasks page has an alias at /docs/ai/neo/tasks/ so the old URL redirects to this page.
evidence: This is the page's own Hugo front-matter config, which the PR author controls, so it isn't a factual claim to check. The file does list `- /docs/ai/neo/tasks/` under `aliases:` (L10). No file exists at content/docs/ai/neo/tasks.md, so…; source: repo:content/docs/ai/concepts/neo/tasks.md L6-10; read_file content/docs/ai/neo/tasks.md (does not exist)
source: repo:content/docs/ai/concepts/neo/tasks.md L6-10; read_file content/docs/ai/neo/tasks.md (does not exist)
pass1 · url · high confidence
#200
➖ Not a claim
content/docs/ai/concepts/neo/usage-limits.md:8
- /docs/ai/neo/usage-limits/
evidence: Line 8 is an entry in the page's Hugo front-matter `aliases:` list (the redirect path for the old URL `/docs/ai/neo/usage-limits/`). It's site routing metadata, not a factual assertion that can be checked.; source: repo:content/docs/ai/concepts/neo/usage-limits.md#L6-L8
source: repo:content/docs/ai/concepts/neo/usage-limits.md#L6-L8
pass1 · url · high confidence
#211
➖ Not a claim
content/docs/ai/get-started/neo.md:9
The page is also reachable at the alias /docs/ai/neo/get-started/ (redirect to the Neo getting-started page).
framing: The claim restates site config (an alias entry in the front matter). It isn't an assertion about a third party.; evidence: This describes the page's own Hugo front matter. Line 9 of `aliases:` lists `- /docs/ai/neo/get-started/`, and Hugo turns each alias into a redirect to this page. No file exists at content/docs/ai/neo/get-started.md, so nothing else…; source: repo:content/docs/ai/get-started/neo.md L6-9; read_file content/docs/ai/neo/get-started.md (does not exist)
source: repo:content/docs/ai/get-started/neo.md L6-9; read_file content/docs/ai/neo/get-started.md (does not exist)
framing: The claim restates site config (an alias entry in the front matter). It isn't an assertion about a third party.
pass1 · url · high confidence
#252
➖ Not a claim
content/docs/ai/integrations/_index.md:7
- /docs/ai/neo/integrations/
evidence: Line 7 is a Hugo frontmatter `aliases:` entry (`- /docs/ai/neo/integrations/`), which is a redirect from an old path, not a link target or a factual assertion.; source: repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/_index.md
pass1 · url · high confidence
#256
➖ Not a claim
content/docs/ai/integrations/cli-integrations.md:8
- /docs/ai/neo/integrations/cli/
evidence: The flagged line is a Hugo front-matter `aliases:` entry (`- /docs/ai/neo/integrations/cli/`). It sets up a redirect from the page's old path to this page. It's routing configuration that the author chose, not a factual assertion that…; source: repo:content/docs/ai/integrations/cli-integrations.md (front matter aliases, L6-8)
source: repo:content/docs/ai/integrations/cli-integrations.md (front matter aliases, L6-8)
pass1 · url · medium confidence
#258
➖ Not a claim
content/docs/ai/integrations/external-mcp-servers.md:8
- /docs/ai/neo/integrations/mcp/
evidence: Line 8 is a Hugo front-matter `aliases:` entry ("- /docs/ai/neo/integrations/mcp/"). It sets up a redirect from that old path to this page and makes no factual statement that could be true or false.; source: repo:content/docs/ai/integrations/external-mcp-servers.md#L6-L8
source: repo:content/docs/ai/integrations/external-mcp-servers.md#L6-L8
pass1 · url · high confidence
#261
➖ Not a claim
content/docs/ai/integrations/slack/index.md:7
- /docs/ai/neo/integrations/slack/
evidence: Line 7 sits in the front matter under `aliases:`. It is a Hugo redirect alias that sends the old /docs/ai/neo/integrations/slack/ path to this page. It is site routing config, not a factual assertion or an outbound link that needs checking.; source: repo:content/docs/ai/integrations/slack/index.md L6-7
source: repo:content/docs/ai/integrations/slack/index.md L6-7
pass1 · url · high confidence
#42
🤷 Unverifiable
content/docs/ai/concepts/neo/_index.md:35
When a task calls for changing infrastructure, Neo changes the IaC code rather than making changes in a console.
evidence: Only the page under review says this ("Neo changes the IaC code rather than clicking in a console"). Neo's agent runs in Pulumi Cloud, which is closed source, so there's no public pulumi/* code to check it against, and I couldn't find a…; source: repo:content/docs/ai/concepts/neo/_index.md L35-36 (reviewed file only); gh search code --repo pulumi/docs returned nothing; intuition: The 'rather than' is absolute. It may overstate things for CLI or Slack sessions, where Neo has authenticated cloud…
source: repo:content/docs/ai/concepts/neo/_index.md L35-36 (reviewed file only); gh search code --repo pulumi/docs returned nothing
pass1 · behavior · low confidence
#46
🤷 Unverifiable
content/docs/ai/concepts/neo/_index.md:46
Neo's pull request reviews never block the merge.
evidence: The sibling page content/docs/ai/concepts/neo/code-reviews.md:25 says the same thing ("Neo does not block the merge."). But that is another Pulumi docs page, not product source. Searching the public pulumi org turned up no Neo review…; source: repo:content/docs/ai/concepts/neo/code-reviews.md#L25; gh search code --owner pulumi "neo code review REQUEST_CHANGES" (no results); intuition: "Never" is an absolute word: it holds only if Neo always posts reviews as COMMENT and never as REQUEST_CHANGES, and…
source: repo:content/docs/ai/concepts/neo/code-reviews.md#L25; gh search code --owner pulumi "neo code review REQUEST_CHANGES" (no results)
pass1 · behavior · medium confidence
#55
🤷 Unverifiable
content/docs/ai/concepts/neo/_index.md:71
Mentioning @Neo in any Slack channel makes Neo reply in the thread, allowing you to check stack state or investigate a failure.
evidence: I couldn't find or read the target page (/docs/ai/integrations/slack/) in the repo. The integrations index only says "mention Neo from a PR thread or a Slack channel to start a task." That supports mentioning Neo in a Slack channel, but…; source: repo:content/docs/ai/integrations/_index.md L30; content/docs/ai/integrations/slack.md and slack/_index.md not found; intuition: "Any channel" may be too broad: Slack bots usually have to be invited to a channel before they can respond there.
source: repo:content/docs/ai/integrations/_index.md L30; content/docs/ai/integrations/slack.md and slack/_index.md not found
pass1 · url · low confidence
#66
🤷 Unverifiable
content/docs/ai/concepts/neo/automations.md:26
Neo scheduled tasks (automations) default to permission mode 'read-only', so the task can read state and propose changes through pull requests but cannot…
framing: Target mismatch: the claim is tied to tasks#task-modes (approval modes), but the read-only fact comes from the permissions page. The permissions page also…; evidence: The cited target (/docs/ai/concepts/neo/tasks/#task-modes) covers approval modes only ("Review mode (default)… Balanced mode… Auto mode") and never mentions a read-only permission mode, so it doesn't support this claim. In the doc line…; source: repo:content/docs/ai/concepts/neo/tasks.md L54-60; repo:content/docs/ai/concepts/neo/permissions.md L68, L79, L116; intuition: "Can't write directly to your infrastructure" overstates read-only mode. The permissions page says it doesn't stop…
source: repo:content/docs/ai/concepts/neo/tasks.md L54-60; repo:content/docs/ai/concepts/neo/permissions.md L68, L79, L116
framing: shifted — Target mismatch: the claim is tied to tasks#task-modes (approval modes), but the read-only fact comes from the permissions page. The permissions page also narrows read-only to "no Pulumi Cloud mutations", not "can't write directly to…
pass1 · url · medium confidence
#67
🤷 Unverifiable
content/docs/ai/concepts/neo/automations.md:40
In Neo automations, MCP integrations use the credentials of whoever configured the integration (the OAuth identity for OAuth-based integrations, the API…
evidence: The sibling external-mcp-servers page backs up the token half: "All actions Neo takes through this integration are attributed to the user who created the token, regardless of who creates the Neo task." It doesn't back up the OAuth half.…; source: repo:content/docs/ai/integrations/external-mcp-servers.md L22-L38, L88-L116; gh search code --owner pulumi (no results); intuition: The claim describes OAuth identities for MCP integrations, but the sibling docs say every current integration uses an…
source: repo:content/docs/ai/integrations/external-mcp-servers.md L22-L38, L88-L116; gh search code --owner pulumi (no results)
pass1 · behavior · low confidence
#68
🤷 Unverifiable
content/docs/ai/concepts/neo/automations.md:40
Neo MCP integrations used by automations use the credentials of whoever configured the integration: the OAuth identity for OAuth-based integrations, and the…
framing: The linked MCP page says token credentials are attributed to "the user who created the token". The claim says "whoever configured the integration", which can…; evidence: The claim was matched to the wrong link. The source hint points to the Custom Instructions anchor, but the credentials sentence links to /docs/ai/integrations/external-mcp-servers/. That page supports the token part: "All actions Neo…; source: repo:content/docs/ai/integrations/external-mcp-servers.md (L22, L36-38, L88-115); repo:content/docs/ai/concepts/neo/automations.md L40; intuition: The claim mentions "OAuth-based integrations", but the sibling MCP page lists every supported integration as token or…
source: repo:content/docs/ai/integrations/external-mcp-servers.md (L22, L36-38, L88-115); repo:content/docs/ai/concepts/neo/automations.md L40
framing: overclaim-broader — The linked MCP page says token credentials are attributed to "the user who created the token". The claim says "whoever configured the integration", which can be a different person (an admin can enter someone else's token), and it adds an…
pass1 · url · medium confidence
#71
🤷 Unverifiable
content/docs/ai/concepts/neo/code-reviews.md:22
Neo code reviews are currently in public preview and will be generally available on July 1, 2026.
evidence: This is a future-dated GA commitment (July 1, 2026), which can't be checked against product source. Searching pulumi/* code turned up no mention of the preview status or the GA date. data/pulumi_editions.yaml only lists…; source: gh search code --owner pulumi "Neo code reviews July 1, 2026" (no results); repo:data/pulumi_editions.yaml L203-205; intuition: A hard-coded future GA date in docs will go stale. A product owner should confirm the date, and the note needs to be…
source: gh search code --owner pulumi "Neo code reviews July 1, 2026" (no results); repo:data/pulumi_editions.yaml L203-205
pass1 · temporal · low confidence
#73
🤷 Unverifiable
content/docs/ai/concepts/neo/code-reviews.md:29
By default, Neo reviews every pull request automatically, skipping draft pull requests and pull requests opened by bots.
evidence: Neo code review triggering (automatic by default, skipping drafts and bot-opened PRs) is implemented in the closed-source Pulumi Cloud service. Searching the public pulumi org on GitHub found no matching source. The only place the claim…; source: gh search code --owner pulumi "neo code review draft bot" (no results); repo:content/docs/ai/concepts/neo/code-reviews.md L29 (reviewed file, not evidence); intuition: Internal product behavior. Needs confirmation from the Neo/Pulumi Cloud team, since neither public source nor the web…
source: gh search code --owner pulumi "neo code review draft bot" (no results); repo:content/docs/ai/concepts/neo/code-reviews.md L29 (reviewed file, not evidence)
pass1 · behavior · low confidence
#74
🤷 Unverifiable
content/docs/ai/concepts/neo/code-reviews.md:33
Mentioning `@pulumi-neo` in a pull request description, a review comment (top-level or inline), or an issue causes Neo to reply in the same thread.
framing: The PR appears to move the existing code-reviews page to a new path with this text unchanged; other Pulumi pages say the same, but none of that is…; evidence: The Neo GitHub mention handling is in Pulumi Cloud's private service, so I couldn't check the product source. Other Pulumi pages say the same thing, which supports the claim but can't confirm it: the existing…; source: gh search code --repo pulumi/docs pulumi-neo; gh search code --owner pulumi "@pulumi-neo" (no product-source hits)
source: gh search code --repo pulumi/docs pulumi-neo; gh search code --owner pulumi "@pulumi-neo" (no product-source hits)
framing: The PR appears to move the existing code-reviews page to a new path with this text unchanged; other Pulumi pages say the same, but none of that is independent proof.
pass1 · behavior · medium confidence
#77
🤷 Unverifiable
content/docs/ai/concepts/neo/code-reviews.md:35
Neo matches your GitHub identity to your Pulumi user; if you signed in to Pulumi with GitHub, that link already exists.
evidence: The accounts doc backs up the identity-linking half: it says you can link GitHub identities to your account, and signing up with GitHub uses that identity. I found nothing public showing that Neo maps a GitHub user to a Pulumi user. That…; source: repo:content/docs/administration/concepts/accounts.md (L83-93); gh search code --owner pulumi "pulumi-neo GitHub identity" (no results)
source: repo:content/docs/administration/concepts/accounts.md (L83-93); gh search code --owner pulumi "pulumi-neo GitHub identity" (no results)
pass1 · behavior · low confidence
#83
🤷 Unverifiable
content/docs/ai/concepts/neo/code-reviews.md:50
Neo code reviews run with the same governance as any other Neo task, including the role-based access control, guardrails, and audit logging your organization…
framing: The cited tasks page only covers RBAC on shared links. The claim adds guardrails and audit logging, and says code reviews are governed the same way as other…; evidence: The cited tasks page mentions RBAC only for shared task links ("Links to stacks or resources within the shared task still enforce the viewer's existing RBAC permissions"). It says nothing about guardrails or audit logging, and nothing…; source: repo:content/docs/ai/concepts/neo/tasks.md; repo:content/docs/ai/concepts/neo/_index.md; intuition: Code reviews run automatically from the GitHub App, not as user-created tasks, so it's unclear whose RBAC applies.…
source: repo:content/docs/ai/concepts/neo/tasks.md; repo:content/docs/ai/concepts/neo/_index.md
framing: overclaim-broader — The cited tasks page only covers RBAC on shared links. The claim adds guardrails and audit logging, and says code reviews are governed the same way as other tasks. The cited page supports neither.
pass1 · url · low confidence
#84
🤷 Unverifiable
content/docs/ai/concepts/neo/code-reviews.md:54
When a Pulumi GitHub App installation is not linked to an organization, the Pulumi preview comment on the pull request includes a note with a link to finish…
evidence: I couldn't find a product source for the note in the preview comment. A search of public pulumi code for "finish connecting" only returned the docs page itself, and the GitHub App code that writes PR comments lives in the private Pulumi…; source: gh search code --owner pulumi "finish connecting"; repo:content/docs/integrations/version-control/github-app.md L44-52; intuition: If the installation isn't linked to any Pulumi org, it's unclear how a preview comment would get posted on the PR in…
source: gh search code --owner pulumi "finish connecting"; repo:content/docs/integrations/version-control/github-app.md L44-52
pass1 · behavior · low confidence
#87
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:14
Pulumi Neo applies custom (organization-wide) instructions automatically to every task, so users don't need to repeat context in each task or conversation.
evidence: The claim restates the reviewed page ("applied automatically to every task. Instead of repeating context in each task, you define it once"), and that page can't serve as its own evidence. Neo's backend isn't public, so no product source…; source: repo:content/docs/ai/concepts/neo/instructions/index.md; gh api repos/pulumi/docs/contents/content/docs/ai/neo?ref=master; intuition: This looks like content moved during the IA restructure (PR #22261), probably taken from the existing neo/settings…
source: repo:content/docs/ai/concepts/neo/instructions/index.md; gh api repos/pulumi/docs/contents/content/docs/ai/neo?ref=master
pass1 · behavior · low confidence
#88
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:22
Pulumi Neo Custom Instructions can define naming conventions, compliance requirements, technology preferences, cost guidelines, and automatic actions such as…
evidence: I couldn't find a source outside the reviewed page, and the page can't verify its own claim. The page describes Custom Instructions as free text entered on the "Organization instructions" tab, so listing naming, compliance, tech, cost…; source: repo:content/docs/ai/concepts/neo/instructions/index.md (reviewed file, not evidence); gh pr list -R pulumi/docs --search "Neo custom instructions"; intuition: The list just gives examples of what you can type into a free-text instruction box, so the risk is low. It's likely…
source: repo:content/docs/ai/concepts/neo/instructions/index.md (reviewed file, not evidence); gh pr list -R pulumi/docs --search "Neo custom instructions"
pass1 · feature · low confidence
#89
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:40
When asked to create resources, Pulumi Neo automatically applies the organization's Custom Instructions without the user repeating them in every conversation.
framing: Claim is consistent with the page's own framing ("applied automatically to every task") and with the announcing docs PR; no independent product source was…; evidence: This product-behavior claim can't be checked against public code because Neo's implementation is in the private Pulumi Cloud service. The only support comes from Pulumi's own docs. Merged docs PR pulumi/docs#16767 describes the same…; source: gh pr view 16767 -R pulumi/docs; repo:content/docs/ai/concepts/neo/instructions/index.md
source: gh pr view 16767 -R pulumi/docs; repo:content/docs/ai/concepts/neo/instructions/index.md
framing: Claim is consistent with the page's own framing ("applied automatically to every task") and with the announcing docs PR; no independent product source was available.
pass1 · behavior · low confidence
#90
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:44
Custom Instructions are configured in Pulumi Cloud by navigating to Neo Settings, selecting the "Organization instructions" tab, entering standards and…
evidence: The only source for the Neo Settings → "Organization instructions" tab steps is the page under review (L44-47 plus its screenshot), and that can't verify itself. The Pulumi Cloud console UI is closed source, and the gh code search for…; source: repo:content/docs/ai/concepts/neo/instructions/index.md; gh search code --owner pulumi "Organization instructions" (HTTP 429); intuition: This looks like a page move or reorganization. If the steps are unchanged from the earlier Neo custom-instructions…
source: repo:content/docs/ai/concepts/neo/instructions/index.md; gh search code --owner pulumi "Organization instructions" (HTTP 429)
pass1 · behavior · low confidence
#92
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:59
Adding a bootstrapping instruction to Neo Custom Instructions (to immediately clone the associated repository and follow AGENTS.md setup instructions)…
evidence: The page itself is the only source (L59-68). Neo's agent runtime isn't public, so nothing outside the page can confirm that this prompt makes Neo clone the repo and apply AGENTS.md setup before it starts working. The underlying premise…; source: repo:content/docs/ai/concepts/neo/instructions/index.md L59-68 (reviewed file; not independent evidence); intuition: "Ensures" overstates what a natural-language prompt can guarantee from an LLM agent. Something like "helps ensure" or…
source: repo:content/docs/ai/concepts/neo/instructions/index.md L59-68 (reviewed file; not independent evidence)
pass1 · behavior · low confidence
#93
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:68
With the bootstrapping Custom Instruction, environment setup, git hooks, and coding standards defined in `AGENTS.md` are applied before Neo starts working.
evidence: The claim describes how Pulumi Neo behaves when given a recommended Custom Instruction ("immediately clone the associated repository... Follow any setup instructions it contains before proceeding"). Neo's agent implementation is…; source: repo:content/docs/ai/concepts/neo/instructions/index.md L57-68, L86 (context only; Neo source is not public); intuition: "This ensures" is a strong promise for a natural-language prompt to an LLM agent. Wording like "helps ensure" or…
source: repo:content/docs/ai/concepts/neo/instructions/index.md L57-68, L86 (context only; Neo source is not public)
pass1 · behavior · low confidence
#94
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:72
Pulumi Neo applies configuration in layers with later layers taking priority: Custom Instructions (organization-wide defaults), then repository AGENTS.md…
evidence: I couldn't check the precedence order (Custom Instructions → AGENTS.md → conversation) against any independent source. Neo is a closed-source Pulumi Cloud service, the only statement of the order is the page under review, and GitHub code…; source: repo:content/docs/ai/concepts/neo/instructions/index.md (the reviewed file, so circular); gh search code attempts returned HTTP 429; intuition: An exact precedence order for an LLM agent's prompt layers is likely a description of prompt assembly, not a…
source: repo:content/docs/ai/concepts/neo/instructions/index.md (the reviewed file, so circular); gh search code attempts returned HTTP 429
pass1 · behavior · low confidence
#97
🤷 Unverifiable
content/docs/ai/concepts/neo/instructions/index.md:123
Pulumi Neo supports `AGENTS.md` files in subdirectories; when working in a subdirectory it reads the nearest `AGENTS.md` file, and subdirectory files take…
evidence: Neo's agent runtime is part of the closed-source Pulumi Cloud service, so there is no public product source to show how it resolves subdirectory AGENTS.md files or which file takes precedence. The only statement of this behavior is the…; source: repo:content/docs/ai/concepts/neo/instructions/index.md L121-123; gh pr list -R pulumi/docs --search "AGENTS.md Neo subdirectory"; intuition: "Nearest AGENTS.md wins" is how the AGENTS.md convention is usually described, so the docs may be restating that…
source: repo:content/docs/ai/concepts/neo/instructions/index.md L121-123; gh pr list -R pulumi/docs --search "AGENTS.md Neo subdirectory"
pass1 · behavior · low confidence
#104
🤷 Unverifiable
content/docs/ai/concepts/neo/neo-in-the-cli.md:31
In the `pulumi neo` terminal session, Plan mode is toggled with Shift+Tab before sending your first message.
framing: The anchor /docs/ai/concepts/neo/tasks/#plan-mode exists and covers the Plan mode concept. The Shift+Tab detail and the "before your first message" limit…; evidence: The linked anchor is real: tasks.md has a "## Plan Mode" section. But that page only says "To enable Plan Mode, select the plan button when starting a task" and says nothing about a CLI keybinding. pulumi/pulumi has a TUI in…; source: repo:content/docs/ai/concepts/neo/tasks.md L33-44; gh api repos/pulumi/pulumi/contents/pkg/cmd/pulumi/neo/tui_welcome.go
source: repo:content/docs/ai/concepts/neo/tasks.md L33-44; gh api repos/pulumi/pulumi/contents/pkg/cmd/pulumi/neo/tui_welcome.go
framing: The anchor /docs/ai/concepts/neo/tasks/#plan-mode exists and covers the Plan mode concept. The Shift+Tab detail and the "before your first message" limit aren't backed by the linked page. To settle it, grep pkg/cmd/pulumi/neo/tui.go or…
pass1 · url · low confidence
#105
🤷 Unverifiable
content/docs/ai/concepts/neo/neo-in-the-cli.md:35
Neo integrations carry over from Pulumi Cloud to the terminal; GitHub, Slack, and the rest of the integration catalog work the same way from the `pulumi neo`…
framing: The source says integrations are "available to every Neo task in the organization". The claim says GitHub and Slack "work the same way from the terminal"…; evidence: The integrations page says "All integrations are configured at the organization level by an administrator. Once enabled, they're available to every Neo task in the organization." That loosely supports MCP/CLI integrations applying to…; source: repo:content/docs/ai/integrations/_index.md; gh search code (HTTP 429); intuition: Slack and GitHub are ways to start a Neo task, so it's unclear what "work the same way from the terminal" means for…
source: repo:content/docs/ai/integrations/_index.md; gh search code (HTTP 429)
framing: overclaim-broader — The source says integrations are "available to every Neo task in the organization". The claim says GitHub and Slack "work the same way from the terminal", but the source describes them as ways to start a task, not context sources for a…
pass1 · url · low confidence
#115
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:22
Neo operates within the acting user's RBAC entitlements and cannot perform actions that user couldn't perform.
evidence: Neo's authorization is implemented in the closed-source Pulumi Cloud service, so there's no public product source to check this against. The sibling Neo overview page agrees, but only loosely: "Your permissions, approval controls, and…; source: repo:content/docs/ai/concepts/neo/_index.md L59-60; gh search code hit HTTP 429 (rate limited); intuition: The same page says read-only mode "does not technically prevent" opening ESC environments, and that VCS writes go…
source: repo:content/docs/ai/concepts/neo/_index.md L59-60; gh search code hit HTTP 429 (rate limited)
pass1 · behavior · medium confidence
#116
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:23
Neo never gets more access than the acting user has (no privilege escalation).
evidence: I couldn't check this independently. Neo's authorization logic lives in the private Pulumi Cloud service, and my one gh code search was rate-limited (HTTP 429). The page backs the claim only for Pulumi Cloud RBAC, and it limits that…; source: repo:content/docs/ai/concepts/neo/permissions.md L23, L45, L122-133; gh search code --owner pulumi "neo privilege escalation" (HTTP 429); intuition: "Never gets more access than the user" has no qualifier, but the same page says VCS writes (PRs, commits, checks) go…
source: repo:content/docs/ai/concepts/neo/permissions.md L23, L45, L122-133; gh search code --owner pulumi "neo privilege escalation" (HTTP 429)
pass1 · behavior · low confidence
#120
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:43
Neo tasks created via API or MCP run as the Pulumi user whose token created the task, with that user's RBAC.
framing: Wrong link target: the MCP link points to the external (outbound) MCP integrations page, not to a page about MCP clients creating Neo tasks. A link to the…; evidence: I couldn't confirm this. The linked page (external-mcp-servers.md) covers outbound integrations, where Neo connects to third-party MCP servers. It doesn't cover Neo tasks created through the API or MCP, or whose RBAC they run with. Its…; source: repo:content/docs/ai/integrations/external-mcp-servers.md; gh search code (rate-limited, HTTP 429); intuition: The claim is plausible, since Pulumi access tokens are tied to a user. But Pulumi Cloud's code isn't public, so the…
source: repo:content/docs/ai/integrations/external-mcp-servers.md; gh search code (rate-limited, HTTP 429)
framing: Wrong link target: the MCP link points to the external (outbound) MCP integrations page, not to a page about MCP clients creating Neo tasks. A link to the Pulumi MCP server page would likely fit better.
pass1 · url · low confidence
#124
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:58
Neo has no direct management of policy packs.
evidence: Line 58 of the permissions table says "Policy packs | Packs and results the user can read | No direct management of policy packs." I couldn't check this against anything independent. Neo's tool set lives in Pulumi's private service code…; source: repo:content/docs/ai/concepts/neo/permissions.md L58; gh search code --owner pulumi "neo policy pack tool" (HTTP 429); intuition: Neo acts with the user's RBAC through Pulumi Cloud APIs, and the rest of the table says it edits anything not managed…
source: repo:content/docs/ai/concepts/neo/permissions.md L58; gh search code --owner pulumi "neo policy pack tool" (HTTP 429)
pass1 · feature · low confidence
#125
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:68
Neo's read-only permission mode blocks writes in Pulumi Cloud and instructs Neo not to make modifications, but does not technically prevent Neo from opening…
evidence: I couldn't find an independent source to check this against. The only place the behavior is described is the reviewed page itself (L68, consistent with L79: "Read-only removes the ability to trigger Pulumi Cloud writes"), which can't…; source: repo:content/docs/ai/concepts/neo/permissions.md L68, L79 (the reviewed file, not counted as evidence); gh search code --owner pulumi "neo read-only mode" (HTTP 429); intuition: This security-boundary claim (read-only enforced on the server for Pulumi Cloud writes, but only by prompt…
source: repo:content/docs/ai/concepts/neo/permissions.md L68, L79 (the reviewed file, not counted as evidence); gh search code --owner pulumi "neo read-only mode" (HTTP 429)
pass1 · behavior · low confidence
#126
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:69
Neo is instructed never to run `pulumi env open` or `pulumi env get --show-secrets`, and where possible moves secret values without reading them into context.
evidence: The claim describes Neo's internal system-prompt instructions, meaning what Neo is told not to run and how it handles secrets. That behavior lives in Neo's private service code, not in any public pulumi/* source I could reach. The GitHub…; source: repo:content/docs/ai/concepts/neo/permissions.md L69 (reviewed file, not evidence); gh search code --owner pulumi "pulumi env open show-secrets Neo" (HTTP 429); intuition: Neo's prompt-level behavior is internal-only. A Neo team owner should confirm the exact commands it is told never to…
source: repo:content/docs/ai/concepts/neo/permissions.md L69 (reviewed file, not evidence); gh search code --owner pulumi "pulumi env open show-secrets Neo" (HTTP 429)
pass1 · behavior · low confidence
#127
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:69
Pulumi scans the events a Neo task produces for credential patterns and replaces detected values with `[REDACTED]` before storing them, so detected values…
evidence: I couldn't check this outside the PR. Neo's event redaction pipeline lives in Pulumi Cloud's service code, which isn't public. GitHub code search for "[REDACTED] neo" was rate-limited (HTTP 429). The only statement of the behavior is the…; source: repo:content/docs/ai/concepts/neo/permissions.md L69 (reviewed file only); gh search code --owner pulumi "[REDACTED] neo" → HTTP 429; intuition: This sentence lists specific places where redacted values stay out (task history, shared views, Slack, PR output). A…
source: repo:content/docs/ai/concepts/neo/permissions.md L69 (reviewed file only); gh search code --owner pulumi "[REDACTED] neo" → HTTP 429
pass1 · behavior · low confidence
#128
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:69
An idle Neo task's runtime session is torn down, and the next turn rebuilds context from the stored, redacted history.
evidence: Neo's runtime and session lifecycle are implemented in the private Pulumi Cloud service, so there is no public source to check this against. The only statement I found is the reviewed page itself (L69: "an idle task's runtime session is…; source: repo:content/docs/ai/concepts/neo/permissions.md L69 (the reviewed file, not independent); gh search code was rate-limited; intuition: This is a security claim about internal behavior: how long sessions last and whether the stored history is the…
source: repo:content/docs/ai/concepts/neo/permissions.md L69 (the reviewed file, not independent); gh search code was rate-limited
pass1 · behavior · low confidence
#138
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:116
For scheduled Neo automations, settings resolve in order: the per-automation setting, then the org-level default, then the built-in fallback of auto approval…
evidence: The sibling page automations.md L26-30 says the same thing: "1. The per-automation setting, if set 1. The org-level default 1. Auto approval and read-only permissions (the built-in fallback)". That makes the two pages consistent with…; source: repo:content/docs/ai/concepts/neo/automations.md L24-30; gh search code --owner pulumi (HTTP 429); intuition: Possible ambiguity: if the org-level default always exists, the built-in fallback may never apply. Also, L118 says…
source: repo:content/docs/ai/concepts/neo/automations.md L24-30; gh search code --owner pulumi (HTTP 429)
pass1 · behavior · medium confidence
#140
🤷 Unverifiable
content/docs/ai/concepts/neo/permissions.md:120
Neo invokes integrated CLIs with `pulumi env run` as the acting user, so the integration only works for users who can open the backing ESC environment…
framing: Sibling docs say the same thing, but no independent product source was found.; evidence: The sibling page cli-integrations.md says the same thing ("Neo invokes the CLI with `pulumi env run`, as that user, so an integration works only for users who can open the backing ESC environment") and shows the `pulumi env run…; source: repo:content/docs/ai/integrations/cli-integrations.md L27-33, L75; gh search prs --owner pulumi (no results)
source: repo:content/docs/ai/integrations/cli-integrations.md L27-33, L75; gh search prs --owner pulumi (no results)
framing: Sibling docs say the same thing, but no independent product source was found.
pass1 · behavior · medium confidence
#153
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:39
Pulumi Neo can be turned off entirely, or kept on while disabling individual features.
evidence: The only source that says this is the page under review ("You can turn Neo off entirely, or keep it on while disabling individual features", followed by the master toggle and per-feature toggles). That can't count as independent…; source: repo:content/docs/ai/concepts/neo/settings/index.md (reviewed file, circular); gh search code --owner pulumi "Enable Neo for organization" (HTTP 429); intuition: Plausible UI description; a reviewer with Pulumi Cloud console access can check the Neo Settings > General tab toggles.
source: repo:content/docs/ai/concepts/neo/settings/index.md (reviewed file, circular); gh search code --owner pulumi "Enable Neo for organization" (HTTP 429)
pass1 · feature · low confidence
#154
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:43
In Pulumi Cloud Neo Settings, turning off the 'Enable Neo for organization' toggle disables Neo everywhere, including the Neo agent, natural-language…
evidence: The claim describes how the Pulumi Cloud Neo Settings master toggle behaves. That logic lives in the private Pulumi Cloud service, not in public pulumi/* source. GitHub code search returned HTTP 429 (rate-limited) on every attempt, and a…; source: gh search code --owner pulumi "Enable Neo for organization" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L43 (reviewed file, not evidence); intuition: The page puts code reviews under a separate "Code reviews" tab toggle. Someone with Pulumi Cloud access should…
source: gh search code --owner pulumi "Enable Neo for organization" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L43 (reviewed file, not evidence)
pass1 · behavior · low confidence
#155
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:45
To toggle Neo for an organization, navigate to Neo Settings from the Pulumi left navigation, select the 'General' tab, and toggle 'Enable Neo for…
evidence: The only place this navigation path (Neo Settings → "General" tab → "Enable Neo for organization" toggle) appears is the reviewed page itself, which can't serve as its own evidence. The Pulumi Cloud console code that would confirm it…; source: repo:content/docs/ai/concepts/neo/settings/index.md (reviewed file only); gh search code --owner pulumi "Enable Neo for organization" (HTTP 429)
source: repo:content/docs/ai/concepts/neo/settings/index.md (reviewed file only); gh search code --owner pulumi "Enable Neo for organization" (HTTP 429)
pass1 · behavior · low confidence
#156
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:51
Each Neo per-feature control (Enable Neo agent, Enable Neo CLI explanations, Enable natural-language resource search) is enabled by default and can be turned…
evidence: The only place I found this claim is the page under review, and that can't count as evidence for it. The page says per-feature controls are "enabled by default and can be turned off independently". These toggles live in the Pulumi Cloud…; source: repo:content/docs/ai/concepts/neo/settings/index.md (L49-55); gh search code --owner pulumi "natural-language resource search" (HTTP 429); intuition: Not a red flag: it fits the page's opening statement "Neo and all of its features are enabled by default", but only…
source: repo:content/docs/ai/concepts/neo/settings/index.md (L49-55); gh search code --owner pulumi "natural-language resource search" (HTTP 429)
pass1 · behavior · low confidence
#157
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:53
Neo Settings provides per-feature controls named 'Enable Neo agent', 'Enable Neo CLI explanations', and 'Enable natural-language resource search'.
evidence: The only place these three toggle labels appear is the page under review (L53-55), and that page can't verify itself. The labels come from the Pulumi Cloud UI, whose source is private. GitHub code search was rate-limited (HTTP 429) on…; source: gh search code --owner pulumi "Enable Neo CLI explanations" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L53-55 (reviewed file, not independent); intuition: These labels are from the closed-source Pulumi Cloud UI. Someone needs to check them against the live Neo Settings…
source: gh search code --owner pulumi "Enable Neo CLI explanations" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L53-55 (reviewed file, not independent)
pass1 · api-surface · low confidence
#159
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:62
If Neo was previously disabled, it needs to be re-enabled using the toggle steps described.
evidence: The page's own note says "If Neo was previously disabled, it will need to be enabled as outlined above." The page under review can't verify itself, and the Neo settings UI lives in Pulumi Cloud, which is closed source, so I couldn't…; source: repo:content/docs/ai/concepts/neo/settings/index.md (L62 note; reviewed file only); intuition: This is close to a tautology about the UI toggle, so the risk is low. The note is also vague: it doesn't say whether…
source: repo:content/docs/ai/concepts/neo/settings/index.md (L62 note; reviewed file only)
pass1 · behavior · low confidence
#162
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:71
Anthropic's Claude models can be accessed in Neo through Anthropic, Azure Foundry, or a custom Anthropic-compatible endpoint.
framing: Same-site docs agree (internally consistent), but they don't count as ground truth for product behavior.; evidence: The only support is Pulumi's own docs: pulumi/docs#21672 added this exact sentence along with a BYOK page that says "You can access these models through Anthropic, Azure Foundry, or a custom endpoint that supports the Anthropic Messages…; source: gh pr diff 21672 -R pulumi/docs
source: gh pr diff 21672 -R pulumi/docs
framing: Same-site docs agree (internally consistent), but they don't count as ground truth for product behavior.
pass1 · feature · medium confidence
#169
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:91
Organization administrators can set the default Neo task mode.
evidence: I couldn't confirm that only org admins can set the default task mode. The Pulumi Cloud/Neo settings code isn't public, and searching pulumi/* code turned up nothing. The page itself says "Organization administrators can set the default…; source: repo:content/docs/ai/concepts/neo/settings/index.md L85-105; gh search code --owner pulumi "neo task mode admin" (no results); intuition: Plausible, since lines 81 and 87 of the same page put Neo settings in admins' hands. Someone with access to the…
source: repo:content/docs/ai/concepts/neo/settings/index.md L85-105; gh search code --owner pulumi "neo task mode admin" (no results)
pass1 · behavior · low confidence
#171
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:99
To configure the default Neo task mode, navigate to Neo Settings in Pulumi Cloud, select the 'General' tab, locate the 'Task mode' section, select the…
evidence: I couldn't check this claim. The steps describe the Pulumi Cloud UI (Neo Settings → General tab → "Task mode" dropdown → Save), and that UI's source is in a private repo. My GitHub code search was rate-limited (HTTP 429), and the only…; source: repo:content/docs/ai/concepts/neo/settings/index.md L97-105 (reviewed file only); gh search code rate-limited; intuition: The page has a screenshot (task-mode.png) that a reviewer could check against the claimed "General" tab and dropdown.
source: repo:content/docs/ai/concepts/neo/settings/index.md L97-105 (reviewed file only); gh search code rate-limited
pass1 · behavior · low confidence
#173
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:118
Neo notification settings are user-level: each person configures their own preferences from their account settings, independent of any organization.
evidence: The only thing that says notifications are user-level is the page under review itself (L118, and steps at L126-128 sending users to "account settings"), and that file can't serve as its own evidence. Pulumi Cloud console code is not…; source: repo:content/docs/ai/concepts/neo/settings/index.md L118-128; gh search code --owner pulumi neoBrowserNotifications (HTTP 429); intuition: "Independent of any organization" sits uneasily next to the page's own note that the panel needs an org with Neo…
source: repo:content/docs/ai/concepts/neo/settings/index.md L118-128; gh search code --owner pulumi neoBrowserNotifications (HTTP 429)
pass1 · behavior · low confidence
#174
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:118
Neo notifications alert users when Neo needs attention on a task while the Pulumi Cloud tab is in the background.
evidence: The only place this behavior appears is the page under review (L118, L130: "Neo suppresses both notification types whenever the Pulumi Cloud tab has focus"), and that page can't verify itself. Neo notifications live in the private Pulumi…; source: gh search issues --owner pulumi "neo notifications" (no results); repo:content/docs/ai/concepts/neo/settings/index.md L118-L134; intuition: L118 says the alerts fire while the tab is "in the background", but L130 says they're suppressed only "whenever the…
source: gh search issues --owner pulumi "neo notifications" (no results); repo:content/docs/ai/concepts/neo/settings/index.md L118-L134
pass1 · behavior · low confidence
#175
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:118
Neo browser and audio notifications are both off by default.
evidence: The default state of the Neo notification toggles lives in the closed-source Pulumi Cloud console. Code searches across the pulumi org for "neo notification audio" and "audioNotifications" found nothing. The only statement of the default…; source: gh search code --owner pulumi "neo notification audio"; gh search code --owner pulumi "audioNotifications"; intuition: Off by default makes sense for browser notifications, since they need a permission prompt. Whether audio is also off…
source: gh search code --owner pulumi "neo notification audio"; gh search code --owner pulumi "audioNotifications"
pass1 · behavior · low confidence
#176
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:121
The 'Neo settings' panel in account settings only appears for users whose organization has Neo enabled.
evidence: The only place this condition shows up is the reviewed file's own note (L121: "The 'Neo settings' panel only appears for users whose organization has Neo enabled."), and that page can't serve as its own evidence. The Pulumi Cloud console…; source: repo:content/docs/ai/concepts/neo/settings/index.md L118-128; gh search prs --owner pulumi "Neo notifications account settings" (no results); intuition: Possible edge cases: notifications are a user-level setting that doesn't depend on any one org, so it's unclear what…
source: repo:content/docs/ai/concepts/neo/settings/index.md L118-128; gh search prs --owner pulumi "Neo notifications account settings" (no results)
pass1 · behavior · low confidence
#177
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:126
To configure Neo notifications, navigate to account settings in Pulumi Cloud, locate the 'Neo settings' panel, and turn browser and audio notifications on or…
evidence: The doc's own steps (L124-128) say to "Navigate to your account settings", "Locate the 'Neo settings' panel", and "Turn browser notifications and audio notifications on or off independently". But that is the file under review, so it…; source: repo:content/docs/ai/concepts/neo/settings/index.md L116-128; gh search prs --owner pulumi "Neo notifications browser audio" (no results); intuition: This describes Pulumi Cloud UI behavior, which only the private pulumi-service code or a live UI check can confirm.…
source: repo:content/docs/ai/concepts/neo/settings/index.md L116-128; gh search prs --owner pulumi "Neo notifications browser audio" (no results)
pass1 · behavior · low confidence
#178
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:130
Neo notifications fire when Neo completes a response or requests approval before continuing, and Neo suppresses both browser and audio notifications whenever…
evidence: Pulumi Cloud console code (the Neo notification triggers and the tab-focus suppression) isn't in any public pulumi/* repo. The only text I found is the reviewed page itself (L130), which can't verify its own claim. My code search also…; source: repo:content/docs/ai/concepts/neo/settings/index.md (reviewed file, not evidence); gh search code --owner pulumi "neo notification focus" (HTTP 429)
source: repo:content/docs/ai/concepts/neo/settings/index.md (reviewed file, not evidence); gh search code --owner pulumi "neo notification focus" (HTTP 429)
pass1 · behavior · low confidence
#179
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:130
Neo suppresses both browser and audio notifications whenever the Pulumi Cloud tab has focus.
evidence: The Pulumi Cloud frontend code that controls when Neo notifications fire isn't public. Code and PR searches across the pulumi org for the Neo notification and tab-focus logic returned nothing. The claim fits the rest of the page (L118…; source: gh search code --owner pulumi "neo notification document.hasFocus"; gh search prs --owner pulumi "neo audio notifications"
source: gh search code --owner pulumi "neo notification document.hasFocus"; gh search prs --owner pulumi "neo audio notifications"
pass1 · behavior · low confidence
#180
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:134
Neo browser notifications are native browser notifications that appear in the operating system's notification area, including when the Pulumi Cloud tab is in…
evidence: This behavior lives in the Pulumi Cloud console frontend, and that code isn't in any public pulumi/* repo. I couldn't run the code search (GitHub returned HTTP 429, rate-limited, twice), and a PR search for "neo browser notifications"…; source: gh search code --owner pulumi "Enable notifications in your browser settings" (HTTP 429); gh search prs --owner pulumi "neo browser notifications" (no results); intuition: "Clicking brings the browser to the foreground and opens the relevant task" depends on how the code handles the click…
source: gh search code --owner pulumi "Enable notifications in your browser settings" (HTTP 429); gh search prs --owner pulumi "neo browser notifications" (no results)
pass1 · behavior · low confidence
#181
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:134
Clicking a Neo browser notification brings the browser to the foreground and opens the relevant task.
evidence: I couldn't check this. The click behavior lives in the Pulumi Cloud frontend, which is private (pulumi-service). GitHub code search also returned HTTP 429 (rate-limited), so no product source came back. The only place the claim appears…; source: gh search code --owner pulumi "Notification onclick neo task" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L134; intuition: A click handler that focuses the window and opens the task is the usual pattern, but whether it navigates to the…
source: gh search code --owner pulumi "Notification onclick neo task" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L134
pass1 · behavior · low confidence
#182
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:136
Enabling Neo browser notifications prompts the browser for notification permission; if declined or previously blocked, the toggle reverts to off and an…
evidence: This claim describes how the Pulumi Cloud console UI behaves (the permission prompt, the toggle reverting, the message text). That UI code is in a private service repo, so public sources can't check it. The code search for the exact…; source: gh search code --owner pulumi "Enable notifications in your browser settings" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L136 (reviewed file, not independent)
source: gh search code --owner pulumi "Enable notifications in your browser settings" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md L136 (reviewed file, not independent)
pass1 · behavior · low confidence
#184
🤷 Unverifiable
content/docs/ai/concepts/neo/settings/index.md:142
When audio notifications are enabled, Neo plays a short two-note chime when a task needs the user's attention.
evidence: I couldn't find an independent source for the sound itself. The only place it appears is the page under review (L142: "plays a short two-note chime"). The Neo frontend code is in Pulumi Cloud's private repo, and every GitHub code search…; source: gh search code --owner pulumi "audioNotifications" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md; intuition: "Two-note chime" is a specific UI detail that only Pulumi Cloud's private frontend code can confirm. Ask the PR…
source: gh search code --owner pulumi "audioNotifications" (HTTP 429); repo:content/docs/ai/concepts/neo/settings/index.md
pass1 · behavior · low confidence
#189
🤷 Unverifiable
content/docs/ai/concepts/neo/slash-commands/index.md:31
To create a custom Neo slash command: navigate to Neo Settings in Pulumi Cloud, select the 'General' tab, scroll to the 'Slash commands' section, click 'Add…
evidence: The steps describe the Pulumi Cloud UI (Neo Settings > General > Slash commands > "Add custom slash command"), which isn't in public source. The only place they appear is the page under review, and that page can't serve as its own…; source: repo:content/docs/ai/concepts/neo/slash-commands/index.md; gh search code --owner pulumi "Add custom slash command" (HTTP 429); intuition: This is closed-source Cloud UI navigation, so a reviewer should check it against the live console or the screenshot…
source: repo:content/docs/ai/concepts/neo/slash-commands/index.md; gh search code --owner pulumi "Add custom slash command" (HTTP 429)
pass1 · behavior · low confidence
#191
🤷 Unverifiable
content/docs/ai/concepts/neo/slash-commands/index.md:41
Once a custom Neo slash command is saved, it is immediately available to all team members in the organization.
evidence: The only statement of this behavior is the reviewed page itself ("Once saved, the command is immediately available to all team members."), and that can't serve as its own evidence. Neo's slash-command feature is part of closed-source…; source: repo:content/docs/ai/concepts/neo/slash-commands/index.md (self only); gh search code --owner pulumi (HTTP 429); intuition: "Immediately" and "all team members" may hide caveats such as caching delays or Neo role permissions. Worth asking…
source: repo:content/docs/ai/concepts/neo/slash-commands/index.md (self only); gh search code --owner pulumi (HTTP 429)
pass1 · behavior · low confidence
#192
🤷 Unverifiable
content/docs/ai/concepts/neo/slash-commands/index.md:45
In a new or existing Neo task, after selecting a slash command, clicking the highlighted command name displays the actual prompt of that command.
evidence: This describes how the Pulumi Cloud Neo UI behaves, and that UI's source code isn't public. My code search hit a rate limit, and an issue search for Neo slash command prompt viewing found nothing. The only place this behavior is…; source: gh search issues --owner pulumi "neo slash command view prompt" (no results); repo:content/docs/ai/concepts/neo/slash-commands/index.md L45 (reviewed file, not evidence)
source: gh search issues --owner pulumi "neo slash command view prompt" (no results); repo:content/docs/ai/concepts/neo/slash-commands/index.md L45 (reviewed file, not evidence)
pass1 · behavior · low confidence
#195
🤷 Unverifiable
content/docs/ai/concepts/neo/tasks.md:19
Tasks are Neo's primary unit of work; each task is a conversation where the user describes what they want to accomplish and Neo handles the infrastructure…
evidence: I couldn't check this against an independent source. Neo is closed-source Pulumi Cloud, so there's no product code to read, and a code search hit GitHub's rate limit. The sibling page content/docs/ai/concepts/neo/_index.md agrees with…; source: repo:content/docs/ai/concepts/neo/_index.md L33-63; gh search code (rate-limited); intuition: This is close to a definition of what a task is, not a testable statement about behavior. It agrees with the sibling…
source: repo:content/docs/ai/concepts/neo/_index.md L33-63; gh search code (rate-limited)
pass1 · behavior · low confidence
#197
🤷 Unverifiable
content/docs/ai/concepts/neo/tasks.md:68
The page links to /docs/ai/concepts/neo/previews/ as the page with more information about Neo and previews; the target must exist.
evidence: I couldn't find the link target in the local checkout. Neither content/docs/ai/concepts/neo/previews.md nor previews/_index.md exists. Sibling pages that are linked the same way (pull-requests.md) are missing too, while tasks.md and…; source: read_file content/docs/ai/concepts/neo/previews.md (does not exist); read_file content/docs/ai/concepts/neo/previews/_index.md (does not exist); gh api repos/pulumi/docs/contents/content/docs/ai/concepts/neo (404); intuition: This could be a broken internal link. Neo pages seem to be mid-restructure (tasks.md exists, but the linked previews…
source: read_file content/docs/ai/concepts/neo/previews.md (does not exist); read_file content/docs/ai/concepts/neo/previews/_index.md (does not exist); gh api repos/pulumi/docs/contents/content/docs/ai/concepts/neo (404)
pass1 · url · low confidence
#202
🤷 Unverifiable
content/docs/ai/concepts/neo/usage-limits.md:75
- [Neo settings](/docs/ai/concepts/neo/settings/) — configure Neo for your organization
evidence: I couldn't find a target page for /docs/ai/concepts/neo/settings/. Neither content/docs/ai/concepts/neo/settings.md nor settings/_index.md exists in the repo, and neither does content/docs/ai/settings.md. A GitHub code search turned up…; source: repo:content/docs/ai/concepts/neo/ (settings.md and settings/_index.md not found); gh search code --owner pulumi path:content/docs/ai "/docs/ai/concepts/neo/settings/"; intuition: This may be a broken internal link: no page or alias for /docs/ai/concepts/neo/settings/ was found. Check that the PR…
source: repo:content/docs/ai/concepts/neo/ (settings.md and settings/_index.md not found); gh search code --owner pulumi path:content/docs/ai "/docs/ai/concepts/neo/settings/"
pass1 · url · low confidence
#216
🤷 Unverifiable
content/docs/ai/get-started/neo.md:30
Without a VCS integration, Neo can still provide code change suggestions, but the user must apply the changes and open PRs manually.
evidence: The only place this appears is the reviewed file itself (L30: "Neo can still provide code change suggestions without a VCS integration, but you'll need to apply the changes and open PRs manually"), and that can't serve as its own…; source: repo:content/docs/ai/get-started/neo.md L22-30 (self-reference only); gh search code returned HTTP 429
source: repo:content/docs/ai/get-started/neo.md L22-30 (self-reference only); gh search code returned HTTP 429
pass1 · behavior · low confidence
#219
🤷 Unverifiable
content/docs/ai/get-started/neo.md:40
In Neo's read-only mode, Neo can still read state, run previews, write and refactor code, and open pull requests, but cannot trigger deployments or other…
evidence: I couldn't check this against product source: GitHub code search was rate-limited (HTTP 429) and the issue search returned nothing. The canonical permissions page in this repo says the same thing: "Read-only removes the ability to…; source: repo:content/docs/ai/concepts/neo/permissions.md L79, L68; gh search code (HTTP 429); intuition: permissions.md L68 adds that read-only mode also "instructs Neo not to make modifications", which sits uneasily with…
source: repo:content/docs/ai/concepts/neo/permissions.md L79, L68; gh search code (HTTP 429)
pass1 · behavior · medium confidence
#220
🤷 Unverifiable
content/docs/ai/get-started/neo.md:40
Neo never gets more access than the user has; read-only mode only reduces permissions.
evidence: The sibling page content/docs/ai/concepts/neo/permissions.md backs this up: "No privilege escalation: Neo never gets more access than the user has, only the same or less." It also says read-only mode "removes the ability to trigger…; source: repo:content/docs/ai/concepts/neo/permissions.md L23, L45, L79; gh search code --owner pulumi "read-only permission-mode neo" (no results); intuition: "Never more access" only covers Pulumi Cloud permissions (RBAC). permissions.md L45 says Neo writes to version…
source: repo:content/docs/ai/concepts/neo/permissions.md L23, L45, L79; gh search code --owner pulumi "read-only permission-mode neo" (no results)
pass1 · behavior · medium confidence
#226
🤷 Unverifiable
content/docs/ai/get-started/neo.md:53
AI controls for an organization are located in Settings > Neo Settings > General, and disabling AI features hides Neo from navigation.
evidence: The sibling Neo Settings page backs up the location: "Navigate to Neo Settings from the Pulumi left navigation... Select the 'General' tab... Toggle 'Enable Neo for organization' on or off". That is only another docs page, though.…; source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md; gh search code --owner pulumi "Neo Settings"; intuition: The settings page says to reach Neo Settings "from the Pulumi left navigation". If disabling Neo hid that navigation…
source: gh api repos/pulumi/docs/contents/content/docs/ai/neo/settings/_index.md; gh search code --owner pulumi "Neo Settings"
pass1 · behavior · medium confidence
#229
🤷 Unverifiable
content/docs/ai/get-started/neo.md:65
In response to a prompt, Neo acknowledges the request, searches through the user's infrastructure, and presents findings in a clear format.
evidence: The tutorial says "Neo will: Acknowledge your request / Search through your infrastructure / Present findings in a clear format". Neo is a closed-source Pulumi Cloud agent, and its output comes from an LLM, so no public pulumi/* source…; source: repo:content/docs/ai/get-started/neo.md L65-68; intuition: Soft wording about what an LLM will do ("clear format"). It's low-risk, and checking it would mean running Neo, not…
source: repo:content/docs/ai/get-started/neo.md L65-68
pass1 · behavior · low confidence
#230
🤷 Unverifiable
content/docs/ai/get-started/neo.md:78
Depending on the scale of the issue, Neo may propose a plan or may immediately create a PR; Neo asks for confirmation before making changes and generates the…
evidence: No product source is public for Neo's behaviour, and I couldn't find the cited pull-requests page as a file in the repo. A sibling page, permissions.md L82-98, contradicts the claim that confirmation always happens: "Auto mode: Neo does…; source: repo:content/docs/ai/concepts/neo/permissions.md (L73-98); repo:content/docs/ai/get-started/neo.md L78-83; intuition: The claim says Neo always asks for confirmation before making changes. The permissions doc says that depends on…
source: repo:content/docs/ai/concepts/neo/permissions.md (L73-98); repo:content/docs/ai/get-started/neo.md L78-83
pass1 · url · medium confidence
#235
🤷 Unverifiable
content/docs/ai/get-started/neo.md:89
Neo cannot initialize new Pulumi projects; it can only work within existing projects that are already set up.
evidence: Neo runs in closed Pulumi Cloud, so there's no public product source to check this limitation against, and no other docs page confirms or denies it. Nearby text points the other way: L88 says "Neo creates repositories as your own…; source: repo:content/docs/ai/get-started/neo.md L88-89; repo:content/docs/ai/concepts/neo/permissions.md L124-133; intuition: This limitation may be out of date: if Neo can create repositories (L88, permissions.md), it can probably set up new…
source: repo:content/docs/ai/get-started/neo.md L88-89; repo:content/docs/ai/concepts/neo/permissions.md L124-133
pass1 · feature · low confidence
#240
🤷 Unverifiable
content/docs/ai/guides/set-up-mcp-server.md:31
Through the Pulumi MCP server, an agent can list your stacks, search your resources, check policy violations, look up resource schemas in the Pulumi…
framing: The source defines the MCP protocol in general, while the claim describes the tools a Pulumi product exposes. The cited page can't support the capability list.; evidence: The cited page (HTTP 200) is the generic "What is the Model Context Protocol (MCP)?" intro. It says nothing about the Pulumi MCP server's tools (listing stacks, searching resources, checking policy violations, looking up Registry…; source: https://modelcontextprotocol.io/
source: https://modelcontextprotocol.io/
framing: shifted — The source defines the MCP protocol in general, while the claim describes the tools a Pulumi product exposes. The cited page can't support the capability list.
pass2 · url · low confidence
#245
🤷 Unverifiable
content/docs/ai/guides/set-up-mcp-server.md:165
Each task the `neo-bridge` tool starts, and each message or approval it sends, runs Neo in Pulumi Cloud and counts against the organization's Neo usage as it…
framing: The source only says limits cover 'Neo usage billed by Pulumi across your organization'. The claim adds specific metering for each `neo-bridge` task, message…; evidence: The cited usage-limits page never mentions the MCP server or `neo-bridge`. It only says the org limit "covers Neo usage billed by Pulumi across your organization" and that requests through BYOK "do not count toward these limits". That…; source: repo:content/docs/ai/concepts/neo/usage-limits.md; repo:content/docs/ai/reference/mcp-server-tools.md; gh api repos/pulumi/mcp-server/contents/README.md (404); intuition: The claim says every MCP call counts, but the usage-limits page says BYOK requests don't count toward limits.…
source: repo:content/docs/ai/concepts/neo/usage-limits.md; repo:content/docs/ai/reference/mcp-server-tools.md; gh api repos/pulumi/mcp-server/contents/README.md (404)
framing: overclaim-broader — The source only says limits cover 'Neo usage billed by Pulumi across your organization'. The claim adds specific metering for each `neo-bridge` task, message and approval, 'as it would in the console', which the source doesn't address.
pass1 · url · low confidence
#246
🤷 Unverifiable
content/docs/ai/guides/set-up-mcp-server.md:167
In Claude Code, adding `mcp__pulumi__neo-bridge` to `permissions.deny` in `settings.json` blocks the Pulumi MCP `neo-bridge` tool.
evidence: (escalated from pass1) Claude Code docs confirm the mechanism: deny rules "prevent Claude Code from using the specified tool", and MCP tools use the form mcp__<server>__<tool> (e.g. "a deny on mcp__github__delete_repo blocks the…; source: https://code.claude.com/docs/en/permissions; https://www.datacamp.com/tutorial/claude-code-security; intuition: The rule only works if the user's MCP server key is literally "pulumi" (as set up earlier in the guide). Check the… (WebSearch dispatched but verification did not converge within the turn budget)
source: https://code.claude.com/docs/en/permissions; https://www.datacamp.com/tutorial/claude-code-security
pass3 · api-surface · medium confidence
#247
🤷 Unverifiable
content/docs/ai/guides/set-up-mcp-server.md:167
Restricting the access token's role isn't enough on its own to prevent Neo tasks from being started via the MCP server; denying `neo-bridge` in the agent's…
evidence: I couldn't find any product source showing whether an organization token's RBAC role is checked when Neo tasks are created. Code search for `neo-bridge` in pulumi/* only turned up docs pages that repeat the claim ("Don't rely on the…; source: gh search code --owner pulumi "neo-bridge" (only docs hits: content/docs/ai/mcp-server/index.md, content/blog/remote-mcp-server/index.md); intuition: Says roles in Pulumi Cloud's access control (RBAC) can't stop Neo tasks from starting. If that's true it's a notable…
source: gh search code --owner pulumi "neo-bridge" (only docs hits: content/docs/ai/mcp-server/index.md, content/blog/remote-mcp-server/index.md)
pass1 · behavior · low confidence
#267
🤷 Unverifiable
content/docs/ai/reference/mcp-server-tools.md:24
The Pulumi MCP server exposes a `get-stacks` tool that lists the stacks in your organization.
evidence: Code search only found `get-stacks` in pulumi/docs content (e.g. the mcp-server page says "| `get-stacks` | List the stacks in your organization. |" and the remote-mcp-server blog post). I couldn't find the source for the hosted MCP…; source: gh search code --owner pulumi "get-stacks"; gh api repos/pulumi/mcp-server/contents/ (404); intuition: Other docs pages and the blog list the same tool name and description. The hosted server's source looks closed…
source: gh search code --owner pulumi "get-stacks"; gh api repos/pulumi/mcp-server/contents/ (404)
pass1 · api-surface · low confidence
#270
🤷 Unverifiable
content/docs/ai/reference/mcp-server-tools.md:33
The Pulumi MCP server exposes a `neo-bridge` tool that starts a Neo task, sends it follow-up messages, and approves or rejects its requests, and returns a…
evidence: I couldn't find any public product source for the `neo-bridge` tool. A code search across the pulumi org only turned up docs pages, and `repos/pulumi/mcp-server` returns 404, so the remote MCP server code looks private. Two other Pulumi…; source: gh search code --owner pulumi neo-bridge; gh search code --owner pulumi neo-reset-conversation; gh api repos/pulumi/mcp-server/contents (404)
source: gh search code --owner pulumi neo-bridge; gh search code --owner pulumi neo-reset-conversation; gh api repos/pulumi/mcp-server/contents (404)
pass1 · api-surface · low confidence
#282
🤷 Unverifiable
content/docs/iac/comparisons/spacelift.md:93
Both platforms have moved into AI-assisted infrastructure from different starting points. Spacelift's [Intelligence](https://spacelift.io/platform/intelligence…
framing: The link resolves to the Spacelift Intelligence product page, but the fetched text has no passage to compare against the claimed description of what…; evidence: The cited URL is live (HTTP 200) and is the right page, titled "AI-assisted Deployment | Spacelift Intelligence". But the fetched text was cut off after the site navigation, so I couldn't find any passage saying Intelligence includes "an…; source: https://spacelift.io/platform/intelligence
source: https://spacelift.io/platform/intelligence
framing: The link resolves to the Spacelift Intelligence product page, but the fetched text has no passage to compare against the claimed description of what Intelligence includes.
pass2 · url · low confidence
#311
🤷 Unverifiable
content/what-is/mcp-for-infrastructure-as-code.md:65
The local server's tool names are prefixed to keep them unambiguous inside a host that may be connected to multiple servers at once…
framing: The cited docs page (which now points to the tools reference) names `neo-bridge` and unprefixed `list-resources`/`get-resource`/etc.; the claim names…; evidence: I couldn't confirm the prefixed tool names, because the pulumi/mcp-server source wasn't reachable (contents API returned 404, code search found nothing). The only place `neo-task-launcher` or `pulumi-cli-stack-output` appears in the…; source: repo:content/docs/ai/reference/mcp-server-tools.md L20-58; repo:content/docs/ai/guides/set-up-mcp-server.md L156-167; gh search code --owner pulumi neo-task-launcher; intuition: The tool list looks like an older @pulumi/mcp-server version (`pulumi-cli-*`, `neo-task-launcher`). The current docs…
source: repo:content/docs/ai/reference/mcp-server-tools.md L20-58; repo:content/docs/ai/guides/set-up-mcp-server.md L156-167; gh search code --owner pulumi neo-task-launcher
framing: shifted — The cited docs page (which now points to the tools reference) names `neo-bridge` and unprefixed `list-resources`/`get-resource`/etc.; the claim names `neo-task-launcher`, `pulumi-registry-*`, and `pulumi-cli-*` tools.
pass1 · url · medium confidence
#312
🤷 Unverifiable
content/what-is/mcp-for-infrastructure-as-code.md:78
Download and pull counts come from the [npm registry](https://www.npmjs.com/package/@pulumi/mcp-server) and [Docker Hub](https://hub.docker.com/r/mcp/pulumi)…
framing: Couldn't check framing: the 403 response had an empty body, so there was no passage to compare against.; evidence: The cited npm URL returned HTTP 403 Forbidden with an empty body, so I couldn't confirm the package page or its download counts. npm commonly blocks automated fetches with a 403 even when the page exists, so this looks like bot blocking…; source: https://www.npmjs.com/package/@pulumi/mcp-server; intuition: The rule says a non-2xx status means contradicted, but I didn't apply it here: a 403 from npmjs.com is usually…
source: https://www.npmjs.com/package/@pulumi/mcp-server
framing: Couldn't check framing: the 403 response had an empty body, so there was no passage to compare against.
pass2 · url · low confidence
#24
❌ Contradicted
content/docs/ai/concepts/_index.md:24
The Neo sub-pages (tasks, permissions, automations, neo-in-the-cli, neo-in-your-editor, pull-requests, code-reviews, previews, instructions, slash-commands…
evidence: Most of the linked sub-pages exist in the repo under content/docs/ai/concepts/neo/: automations.md, tasks.md, neo-in-the-cli.md, neo-in-your-editor.md, code-reviews.md, model-providers.md and usage-limits.md. Three did not resolve at the…; source: read_file content/docs/ai/concepts/neo/{automations,tasks,neo-in-the-cli,neo-in-your-editor,code-reviews,model-providers,usage-limits}.md (exist); read_file content/docs/ai/concepts/neo/{pull-requests.md,previews.md,previews/_index.md,slash-commands.md,slash-commands/_index.md} (not found); intuition: I didn't check permissions, instructions or settings (call budget). Before fixing, a reviewer should confirm whether…
source: read_file content/docs/ai/concepts/neo/{automations,tasks,neo-in-the-cli,neo-in-your-editor,code-reviews,model-providers,usage-limits}.md (exist); read_file content/docs/ai/concepts/neo/{pull-requests.md,previews.md,previews/_index.md,slash-commands.md,slash-commands/_index.md} (not found)
pass1 · url · medium confidence
#139
❌ Contradicted
content/docs/ai/concepts/neo/permissions.md:118
Org-level defaults for permission and approval mode set the starting point for new Neo tasks, and users can override them per task.
framing: Only approval mode has an org-level default for new tasks. Permission mode falls back to a built-in 'default' value. The automations docs mention an…; evidence: (escalated from pass1) The approval-mode half holds: the auto-generated REST schema says CreateAgentTaskRequest.approvalMode is an "Optional approval mode override for this task. If omitted, org default is used." The permission-mode half…; source: https://www.pulumi.com/docs/reference/cloud-rest-api/schema/createagenttaskrequest/ ; https://www.pulumi.com/docs/reference/cloud-rest-api/schema/organizationmetadata/; intuition: The claim pairs both modes under 'org-level defaults', but the org metadata schema only exposes an approval-mode…
source: https://www.pulumi.com/docs/reference/cloud-rest-api/schema/createagenttaskrequest/ ; https://www.pulumi.com/docs/reference/cloud-rest-api/schema/organizationmetadata/
framing: Only approval mode has an org-level default for new tasks. Permission mode falls back to a built-in 'default' value. The automations docs mention an org-level default, but only for scheduled automation runs.
pass3 · behavior · medium confidence
#118
⚔️ Mismatch
content/docs/ai/concepts/neo/permissions.md:39
API/MCP-created Neo tasks run as the Pulumi user whose token created the task, with that user's RBAC exactly as if started in the console; the MCP link…
framing: The MCP link should probably go to /docs/ai/guides/set-up-mcp-server/ (or the neo-bridge reference), not external-mcp-servers. Pulumi Cloud's code isn't…; evidence: The link target exists, but it points to the wrong page. external-mcp-servers.md covers Neo connecting out to other services' MCP servers. The sibling page set-up-mcp-server.md says it covers the reverse case ("connecting your own AI…; source: repo:content/docs/ai/integrations/external-mcp-servers.md; repo:content/docs/ai/guides/set-up-mcp-server.md L36, L109, L126, L167; intuition: "The Pulumi user whose token created the task" leaves out organization tokens, which aren't users. The MCP setup…
source: repo:content/docs/ai/integrations/external-mcp-servers.md; repo:content/docs/ai/guides/set-up-mcp-server.md L36, L109, L126, L167
framing: The MCP link should probably go to /docs/ai/guides/set-up-mcp-server/ (or the neo-bridge reference), not external-mcp-servers. Pulumi Cloud's code isn't public, so I couldn't check the runs-as-token-user behavior against product source.
pass1 · url · medium confidence
#121
⚔️ Mismatch
content/docs/ai/concepts/neo/permissions.md:45
Neo authenticates as the shared app installation for its VCS interactions regardless of which surface started the task.
framing: The page contradicts itself: L45 says the shared installation is used for every VCS interaction, while L124-133 lists repo creation, GHES individual auth…; evidence: L45 says Neo uses the shared app installation for all its VCS interactions no matter which surface started the task. The same page's VCS table (L124-133) lists exceptions: repo creation "runs as your connected individual account", GitHub…; source: repo:content/docs/ai/concepts/neo/permissions.md L45 vs L124-L133; intuition: "Regardless of surface" may be right about surfaces, but the blanket "its VCS interactions" ignores the per-provider…
source: repo:content/docs/ai/concepts/neo/permissions.md L45 vs L124-L133
framing: The page contradicts itself: L45 says the shared installation is used for every VCS interaction, while L124-133 lists repo creation, GHES individual auth, and Custom VCS as exceptions.
pass1 · behavior · medium confidence
#11
🌀 Framing drift
content/docs/ai/_index.md:25
Pulumi agent accounts remove signup friction entirely.
framing: overclaim: the linked page says the agent gets an account "without requiring a human user to sign up first" (signup is postponed), but the claim says agent…; evidence: The feature is real: pulumi/pulumi changelog 3.262.0 mentions "agent account claim". But the linked agent-accounts page says signup is deferred, not removed: "The human claims the account later to take permanent ownership." Write access…; source: repo:content/docs/administration/concepts/agent-accounts.md; gh search code --owner pulumi "agent account claim" (pulumi/pulumi changelog/3.262.0.md); intuition: "Entirely" is absolute marketing wording, but the same docs describe a required claim step, a 3-day write window and…
source: repo:content/docs/administration/concepts/agent-accounts.md; gh search code --owner pulumi "agent account claim" (pulumi/pulumi changelog/3.262.0.md)
framing: overclaim-broader — overclaim: the linked page says the agent gets an account "without requiring a human user to sign up first" (signup is postponed), but the claim says agent accounts "remove signup friction entirely"
pass1 · feature · medium confidence
#60
🌀 Framing drift
content/docs/ai/concepts/neo/_index.md:88
Neo's Plan Mode makes Neo agree on a plan with the user before acting, task modes control which steps need user approval, and read-only mode removes Neo's…
framing: overclaim — claim broadens 'removes the ability to trigger writes in Pulumi Cloud' (code edits, PRs and ESC access still allowed) to 'removes its ability to…; evidence: The Plan Mode and task-mode parts check out against tasks.md: Neo "Waits for your explicit approval before any execution begins", and "Task modes control what approvals Neo requires during execution". The read-only part goes further than…; source: repo:content/docs/ai/concepts/neo/tasks.md L33-62; repo:content/docs/ai/get-started/neo.md L38-42
source: repo:content/docs/ai/concepts/neo/tasks.md L33-62; repo:content/docs/ai/get-started/neo.md L38-42
framing: overclaim-broader — overclaim — claim broadens 'removes the ability to trigger writes in Pulumi Cloud' (code edits, PRs and ESC access still allowed) to 'removes its ability to change anything at all'
pass1 · url · high confidence
#61
🌀 Framing drift
content/docs/ai/concepts/neo/_index.md:91
Neo's read-only mode removes its ability to change anything at all.
framing: overclaim: the claim turns "removes the ability to trigger writes in Pulumi Cloud" into "removes its ability to change anything at all", but the source says…; evidence: The cited section says read-only mode only blocks Pulumi Cloud writes, and lists things Neo can still do: "Read-only mode takes your existing permissions and removes the ability to trigger writes in Pulumi Cloud: Neo can still read…; source: repo:content/docs/ai/get-started/neo.md#L38-L42
source: repo:content/docs/ai/get-started/neo.md#L38-L42
framing: overclaim-broader — overclaim: the claim turns "removes the ability to trigger writes in Pulumi Cloud" into "removes its ability to change anything at all", but the source says Neo can still write code, open PRs, and open ESC environments.
pass1 · url · high confidence
#167
🌀 Framing drift
content/docs/ai/concepts/neo/settings/index.md:83
The page /docs/ai/integrations/ exists and lists available integrations, setup instructions, and credential storage details.
framing: The link target is valid, but the line describes it as having 'the full list of available integrations, setup instructions, and credential storage details'.…; evidence: The /docs/ai/integrations/ page exists (content/docs/ai/integrations/_index.md). It is now a short overview that links out to MCP, CLI, GitHub and Slack integrations, and it does not hold the full list, setup steps, or credential storage…; source: repo:content/docs/ai/integrations/_index.md
source: repo:content/docs/ai/integrations/_index.md
framing: overclaim-broader — The link target is valid, but the line describes it as having 'the full list of available integrations, setup instructions, and credential storage details'. That material now lives at /docs/ai/integrations/external-mcp-servers/, so the…
pass1 · url · medium confidence
#307
🌀 Framing drift
content/releases/changelog/2026-07-14-neo-usage-limits.md:15
Neo usage limits are available now for all organizations, and are configurable by organization admins and billing managers. Read the [announcement blog…
framing: overclaim: the changelog widens "organizations on a paid plan" to "all organizations". The cited blog and docs leave out trial organizations and Individual…; evidence: Both links resolve: the blog exists at content/blog/neo-usage-limits/, and the docs page lists /docs/ai/concepts/neo/usage-limits/. Both pages confirm that Admins and Billing Managers can set limits. But the cited blog says "Usage limits…; source: repo:content/blog/neo-usage-limits/index.md L51; repo:content/docs/ai/concepts/neo/usage-limits.md L21-23, L69-71
source: repo:content/blog/neo-usage-limits/index.md L51; repo:content/docs/ai/concepts/neo/usage-limits.md L21-23, L69-71
framing: overclaim-broader — overclaim: the changelog widens "organizations on a paid plan" to "all organizations". The cited blog and docs leave out trial organizations and Individual accounts.
pass1 · url · high confidence
#330
🚩 Flagged
content/docs/ai/neo/settings/_index.md:1
frontmatter URL `?` collides with `?`
frontmatter: url-collision
source: frontmatter-validate.py pre-step
preflight · frontmatter-url-collision · high confidence
#331
🚩 Flagged
content/docs/ai/concepts/neo/instructions/index.md:57
Neo reads `AGENTS.md` files when it enters a repository, but it needs to clone the repository first.
readthrough: prerequisite-inversion
source: readthrough pre-step
preflight · readthrough-prerequisite-inversion · high confidence
#332
🚩 Flagged
content/docs/ai/concepts/neo/instructions/index.md:95
Use `AGENTS.md` to capture conventions that aren't enforced by linters or formatters: coding standards, naming conventions, how to run tests
readthrough: self-redundancy
source: readthrough pre-step
preflight · readthrough-self-redundancy · high confidence
#333
🚩 Flagged
content/docs/ai/concepts/neo/settings/index.md:49
If you'd rather keep Neo on but disable specific capabilities, use the per-feature controls.
readthrough: missing-step
source: readthrough pre-step
preflight · readthrough-missing-step · high confidence
No claims match the current filter.
Findings
| ID | Bucket | File:lines | Status | Disposition |
|---|---|---|---|---|
| F2 | 🚨 Outstanding | content/docs/ai/concepts/neo/permissions.md | resolved | fixed |
The permissions table links "MCP" to the page about external MCP servers that Neo calls, not to the Pulumi MCP server that creates tasks. — ✅ fixed in 5dd6e0e: MCP link now points to /docs/ai/guides/set-up-mcp-server/ | ||||
| F3 | 🚨 Outstanding | content/docs/ai/concepts/neo/permissions.md | resolved | fixed |
The page says Neo always uses the shared app installation for VCS writes "no matter which surface", which the page's own VCS section (L124–129) contradicts. — ✅ fixed in 5dd6e0e: sentence now names repo creation and GHES individual auth as exceptions | ||||
| F4 | 🚨 Outstanding | content/docs/ai/concepts/neo/permissions.md | resolved | fixed |
The page says permission mode has an org-level default, which the control inventory on the same page (L108) contradicts. — ✅ fixed in 5dd6e0e: sentence removed; control inventory states the approval-mode org default | ||||
| F6 | ⚠️ Reviewer check | content/docs/ai/concepts/neo/instructions/index.md | resolved | fixed |
The "Bootstrapping repository instructions" subsection talks about `AGENTS.md` before the "Repository instructions" section introduces it (L80). Decide whether that order works or should be reversed. — ✅ fixed in 5dd6e0e: bootstrapping subsection now sits under Repository instructions | ||||
| F7 | ⚠️ Reviewer check | content/docs/ai/concepts/neo/instructions/index.md | resolved | fixed |
L95 repeats the bullet list at L88–93 (coding standards, naming conventions, tests). Decide whether the duplicate sentence should go. — ✅ fixed in 5dd6e0e: duplicate sentence removed | ||||
| F8 | ⚠️ Reviewer check | content/docs/ai/concepts/neo/settings/index.md | resolved | fixed |
Per-feature controls (L51–55) don't give their own navigation steps; only the General-tab steps at L45–47 imply where they are. Decide whether readers can find the toggles. — ✅ fixed in a0f9ecc: page says per-feature controls are on the General tab, below the master switch | ||||
| F62 | ⚠️ Reviewer check | content/docs/ai/_index.md | resolved | fixed |
*"Pulumi agent accounts remove signup friction entirely."* — "entirely" overstates the linked page, which says an agent can get an account before a human signs up (signup is postponed, not removed). Ask for "let an agent start before a human signs up" or drop "entirely". — ✅ fixed in 5dd6e0e: now says agent accounts let an agent start before anyone signs up | ||||
| F64 | ⚠️ Reviewer check | content/docs/ai/concepts/neo/_index.md | resolved | fixed |
*"Neo's Plan Mode makes Neo agree on a plan with the user before acting, task modes control which steps need user approval, and read-only mode removes Neo's…"* — verdict: framing-drift; framing: overclaim — claim broadens 'removes the ability to trigger writes in Pulumi Cloud' (code edits, PRs and ESC access still allowed) to 'removes its ability to… — the permissions page says read-only blocks only Pulumi Cloud writes; Neo can still edit code, open PRs, and use ESC credentials. Ask for "removes its ability to make changes in Pulumi Cloud" before approving. — ✅ fixed in 5dd6e0e: read-only now stops Neo from making changes in Pulumi Cloud | ||||
| F65 | ⚠️ Reviewer check | content/docs/ai/concepts/neo/_index.md | resolved | fixed |
*"Neo's read-only mode removes its ability to change anything at all."* — verdict: framing-drift; framing: overclaim: the claim turns "removes the ability to trigger writes in Pulumi Cloud" into "removes its ability to change anything at all", but the source says… — same sentence as F64; one rewrite fixes both. — ✅ fixed in 5dd6e0e: same rewrite as F64 | ||||
| F69 | ⚠️ Reviewer check | content/docs/ai/concepts/neo/settings/index.md | resolved | fixed |
*"The page /docs/ai/integrations/ exists and lists available integrations, setup instructions, and credential storage details."* — verdict: framing-drift; framing: The link target is valid, but the line describes it as having 'the full list of available integrations, setup instructions, and credential storage details'.… — open `/docs/ai/integrations/` and confirm it covers credential storage; if not, ask the author to drop that phrase. — ✅ fixed in 5dd6e0e: credential storage now links to external-mcp-servers#credential-storage | ||||
| F9 | 💡 Preexisting | content/docs/ai/concepts/neo/_index.md:71-73 | open | — |
this claim came over with the rename from `content/docs/ai/neo/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F10 | 💡 Preexisting | content/docs/ai/concepts/neo/automations.md:26 | open | — |
this claim came over with the rename from `content/docs/ai/neo/automations/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F11 | 💡 Preexisting | content/docs/ai/concepts/neo/automations.md:40 | open | — |
this claim came over with the rename from `content/docs/ai/neo/automations/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F12 | 💡 Preexisting | content/docs/ai/concepts/neo/automations.md:40 | open | — |
this claim came over with the rename from `content/docs/ai/neo/automations/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F13 | 💡 Preexisting | content/docs/ai/concepts/neo/code-reviews.md:50 | open | — |
this claim came over with the rename from `content/docs/ai/neo/code-reviews/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F14 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:14 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F15 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:22-28 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F16 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:40 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F17 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:44-47 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F18 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:59-68 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F19 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:68 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F20 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:72-78 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F21 | 💡 Preexisting | content/docs/ai/concepts/neo/instructions/index.md:123 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F22 | 💡 Preexisting | content/docs/ai/concepts/neo/neo-in-the-cli.md:31 | open | — |
this claim came over with the rename from `content/docs/ai/neo/pulumi-cli/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F23 | 💡 Preexisting | content/docs/ai/concepts/neo/neo-in-the-cli.md:35 | open | — |
this claim came over with the rename from `content/docs/ai/neo/pulumi-cli/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F24 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:43 | open | — |
this claim came over with the rename from `content/docs/ai/neo/permissions/_index.md`; this PR changes the page's location and links, not the claim. The link on the same row is covered by F2. | ||||
| F25 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:69 | open | — |
this claim came over with the rename from `content/docs/ai/neo/permissions/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F26 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:69 | open | — |
this claim came over with the rename from `content/docs/ai/neo/permissions/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F27 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:69 | open | — |
this claim came over with the rename from `content/docs/ai/neo/permissions/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F28 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:120 | open | — |
this claim came over with the rename from `content/docs/ai/neo/permissions/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F29 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:39 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F30 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:43 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F31 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:45-47 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F32 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:51 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F33 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:53-55 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F34 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:62 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F35 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:71 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F36 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:91 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F37 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:99-103 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F38 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:118 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F39 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:118 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F40 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:118 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F41 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:121 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F42 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:126-128 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F43 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:130 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F44 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:130 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F45 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:134 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F46 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:134 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F47 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:136 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F48 | 💡 Preexisting | content/docs/ai/concepts/neo/settings/index.md:142 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F49 | 💡 Preexisting | content/docs/ai/concepts/neo/slash-commands/index.md:31-37 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F50 | 💡 Preexisting | content/docs/ai/concepts/neo/slash-commands/index.md:41 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F51 | 💡 Preexisting | content/docs/ai/concepts/neo/slash-commands/index.md:45 | open | — |
this text moved over from the deleted `content/docs/ai/neo/settings/_index.md` when the page was split; the PR moves the claim but doesn't change it. | ||||
| F54 | 💡 Preexisting | content/docs/ai/get-started/neo.md:78-83 | open | — |
this claim came over with the rename from `content/docs/ai/neo/get-started/_index.md`; this PR changes the page's location and links, not the claim. | ||||
| F55 | 💡 Preexisting | content/docs/ai/guides/set-up-mcp-server.md:31 | open | — |
this claim came over with the rename from `content/docs/ai/mcp-server/index.md`; this PR changes the page's location and links, not the claim. | ||||
| F56 | 💡 Preexisting | content/docs/ai/guides/set-up-mcp-server.md:165 | open | — |
this claim came over with the rename from `content/docs/ai/mcp-server/index.md`; this PR changes the page's location and links, not the claim. | ||||
| F57 | 💡 Preexisting | content/docs/ai/reference/mcp-server-tools.md:24 | open | — |
this tools list moved here from `content/docs/ai/mcp-server/index.md` (which lost about the same number of lines); the PR moves the claim but doesn't change it. | ||||
| F58 | 💡 Preexisting | content/docs/ai/reference/mcp-server-tools.md:33-34 | open | — |
this tools list moved here from `content/docs/ai/mcp-server/index.md` (which lost about the same number of lines); the PR moves the claim but doesn't change it. | ||||
| F59 | 💡 Preexisting | content/docs/iac/comparisons/spacelift.md:93 | open | — |
this PR only updates a link in this file; the comparison claim was already there. | ||||
| F60 | 💡 Preexisting | content/what-is/mcp-for-infrastructure-as-code.md:65 | open | — |
this PR only updates links in this file; the tool-naming claim was already there. | ||||
| F61 | 💡 Preexisting | content/what-is/mcp-for-infrastructure-as-code.md:78 | open | — |
this PR only updates links in this file; the download-count sourcing was already there. | ||||
| F74 | 💡 Preexisting | content/releases/changelog/2026-07-14-neo-usage-limits.md:15 | open | — |
the "all organizations" wording was already in this changelog entry; this PR only changes its link (+1/-1). | ||||
| F75 | 💡 Preexisting | content/docs/ai/concepts/neo/_index.md:35-36 | open | — |
Unverifiable claim on a line this PR doesn't change: When a task calls for changing infrastructure, Neo changes the IaC code rather than making changes in a console. | ||||
| F76 | 💡 Preexisting | content/docs/ai/concepts/neo/_index.md:46-47 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo's pull request reviews never block the merge. | ||||
| F77 | 💡 Preexisting | content/docs/ai/concepts/neo/code-reviews.md:22 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo code reviews are currently in public preview and will be generally available on July 1, 2026. | ||||
| F78 | 💡 Preexisting | content/docs/ai/concepts/neo/code-reviews.md:29 | open | — |
Unverifiable claim on a line this PR doesn't change: By default, Neo reviews every pull request automatically, skipping draft pull requests and pull requests opened by bots. | ||||
| F79 | 💡 Preexisting | content/docs/ai/concepts/neo/code-reviews.md:33 | open | — |
Unverifiable claim on a line this PR doesn't change: Mentioning `@pulumi-neo` in a pull request description, a review comment (top-level or inline), or an issue causes Neo to reply in the same thread. | ||||
| F80 | 💡 Preexisting | content/docs/ai/concepts/neo/code-reviews.md:35 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo matches your GitHub identity to your Pulumi user; if you signed in to Pulumi with GitHub, that link already exists. | ||||
| F81 | 💡 Preexisting | content/docs/ai/concepts/neo/code-reviews.md:54 | open | — |
Unverifiable claim on a line this PR doesn't change: When a Pulumi GitHub App installation is not linked to an organization, the Pulumi preview comment on the pull request includes a note with a link to finish… | ||||
| F82 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:22 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo operates within the acting user's RBAC entitlements and cannot perform actions that user couldn't perform. | ||||
| F83 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:23 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo never gets more access than the acting user has (no privilege escalation). | ||||
| F84 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:58 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo has no direct management of policy packs. | ||||
| F85 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:68 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo's read-only permission mode blocks writes in Pulumi Cloud and instructs Neo not to make modifications, but does not technically prevent Neo from opening… | ||||
| F86 | 💡 Preexisting | content/docs/ai/concepts/neo/permissions.md:116 | open | — |
Unverifiable claim on a line this PR doesn't change: For scheduled Neo automations, settings resolve in order: the per-automation setting, then the org-level default, then the built-in fallback of auto approval… | ||||
| F87 | 💡 Preexisting | content/docs/ai/concepts/neo/tasks.md:19 | open | — |
Unverifiable claim on a line this PR doesn't change: Tasks are Neo's primary unit of work; each task is a conversation where the user describes what they want to accomplish and Neo handles the infrastructure… | ||||
| F88 | 💡 Preexisting | content/docs/ai/get-started/neo.md:30 | open | — |
Unverifiable claim on a line this PR doesn't change: Without a VCS integration, Neo can still provide code change suggestions, but the user must apply the changes and open PRs manually. | ||||
| F89 | 💡 Preexisting | content/docs/ai/get-started/neo.md:40 | open | — |
Unverifiable claim on a line this PR doesn't change: In Neo's read-only mode, Neo can still read state, run previews, write and refactor code, and open pull requests, but cannot trigger deployments or other… | ||||
| F90 | 💡 Preexisting | content/docs/ai/get-started/neo.md:40 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo never gets more access than the user has; read-only mode only reduces permissions. | ||||
| F91 | 💡 Preexisting | content/docs/ai/get-started/neo.md:53 | open | — |
Unverifiable claim on a line this PR doesn't change: AI controls for an organization are located in Settings > Neo Settings > General, and disabling AI features hides Neo from navigation. | ||||
| F92 | 💡 Preexisting | content/docs/ai/get-started/neo.md:65-68 | open | — |
Unverifiable claim on a line this PR doesn't change: In response to a prompt, Neo acknowledges the request, searches through the user's infrastructure, and presents findings in a clear format. | ||||
| F93 | 💡 Preexisting | content/docs/ai/get-started/neo.md:89 | open | — |
Unverifiable claim on a line this PR doesn't change: Neo cannot initialize new Pulumi projects; it can only work within existing projects that are already set up. | ||||
| F94 | 💡 Preexisting | content/docs/ai/guides/set-up-mcp-server.md:167 | open | — |
Unverifiable claim on a line this PR doesn't change: In Claude Code, adding `mcp__pulumi__neo-bridge` to `permissions.deny` in `settings.json` blocks the Pulumi MCP `neo-bridge` tool. | ||||
| F95 | 💡 Preexisting | content/docs/ai/guides/set-up-mcp-server.md:167 | open | — |
Unverifiable claim on a line this PR doesn't change: Restricting the access token's role isn't enough on its own to prevent Neo tasks from being started via the MCP server; denying `neo-bridge` in the agent's… | ||||
Editorial stances
Superlative, ranking, or comparative language the diff adds. No verdict — a page's own framing isn't fact-checkable — listed so a reviewer can confirm each is a stance the docs should take.
- content/docs/ai/_index.md L27 Neo is suited for long-running, governed infrastructure tasks, while coding agents are suited for interactive development. positioning · found by llm-atomic
- content/docs/ai/concepts/_index.md L35 - [Settings](/docs/ai/concepts/neo/settings/): Access controls, the default task mode, and notifications. positioning · found by regex
- content/docs/ai/concepts/neo/permissions.md L109 | Approval (task) mode | Review-`manual` / Balanced / Auto | User per task; org admin sets the default | Task UI; `--approval-mode` in the CLI; org default… positioning · found by regex
- content/docs/ai/concepts/neo/settings/index.md L102 1. Select the default mode from the dropdown positioning · found by regex
- content/docs/ai/concepts/neo/settings/index.md L109 Starting with the most restrictive Neo task mode is best for most organizations. positioning · found by llm-atomic
- content/docs/ai/concepts/neo/settings/index.md L109 Starting with the most restrictive Neo task mode (Review mode) is best for most organizations. positioning · found by regex, llm-atomic, llm-holistic
- content/docs/ai/concepts/neo/settings/index.md L5 meta_desc: Configure Neo access controls, model providers, integrations, the default task mode, and notification preferences. positioning · found by regex
- content/docs/ai/concepts/neo/settings/index.md L91 Organization administrators can set the default task mode. The available modes determine how much autonomy Neo has during execution: positioning · found by regex
- content/docs/iac/concepts/converters.md L16 For most conversions, using an LLM is the recommended first option. [Pulumi Neo](/docs/ai/), part of Pulumi Cloud, can convert your infrastructure code using… positioning · found by regex
Investigation log
- cross-sibling-reads
- 0 of 12 siblings
- external-claim-verification
- 226 of 329 claims verified (74 unverifiable, 4 contradicted, 5 framing-drift) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 302 Pass 1, 6 Pass 2 (verified 3, contradicted 0, unverifiable 3), 21 Pass 3 (verified 19, contradicted 1, unverifiable 1).
- cited-claim-spot-checks
- 6 of 6 cited claims fetched and compared
- frontmatter-sweep
- ran on body + meta_desc
- temporal-trigger-sweep
- ran (recency words present in diff; spot-check in-review)
- code-execution
- not run (no `static/programs/` change)
- code-examples-checks
- ran (3 specialists: structural, existence, body-code-coverage); 0 findings
- editorial-balance-pass
- not run (not under content/blog/)
Triaged
{ "file": "content/docs/ai/concepts/_index.md", "from_bucket": "outstanding", "id": "F1", "kind": "spurious", "note": "`pull-requests/`, `previews/`, and `slash-commands/` are leaf bundles (`index.md`), which the verifier did not look for; the Hugo build is green and all added internal links resolve." }{ "file": "content/docs/ai/neo/settings/_index.md", "from_bucket": "outstanding", "id": "F5", "kind": "spurious", "note": "the colliding file `content/docs/ai/neo/settings/_index.md` is deleted by this PR and its content is split into `concepts/neo/{settings,instructions,slash-commands}/`, so the collision is a PR-internal move, not a live clash." }{ "file": "content/docs/ai/concepts/neo/tasks.md", "from_bucket": "author-answer", "id": "F52", "kind": "spurious", "note": "this is a link claim. The target `content/docs/ai/concepts/neo/previews/index.md` exists in this PR, the Hugo build is green, and the added internal links resolve." }{ "file": "content/docs/ai/concepts/neo/usage-limits.md", "from_bucket": "author-answer", "id": "F53", "kind": "spurious", "note": "this is a link claim. The target `content/docs/ai/concepts/neo/settings/index.md` exists in this PR, the Hugo build is green, and the added internal links resolve." }{ "file": "content/docs/ai/concepts/cli-for-agents.md", "from_bucket": "reviewer-check", "id": "F63", "kind": "spurious", "note": "verified against the CLI-for-agents sources; nothing left that affects readers." }{ "file": "content/docs/ai/concepts/neo/code-reviews.md", "from_bucket": "reviewer-check", "id": "F66", "kind": "spurious", "note": "inline line comments are how GitHub PR reviews deliver code-level feedback; no reader impact." }{ "file": "content/docs/ai/concepts/neo/code-reviews.md", "from_bucket": "reviewer-check", "id": "F67", "kind": "spurious", "note": "verified; the remaining doubt is about how strong the source is, not reader impact." }{ "file": "content/docs/ai/concepts/neo/settings/index.md", "from_bucket": "reviewer-check", "id": "F68", "kind": "spurious", "note": "the page goes on to cover all three levels (org settings, repository `AGENTS.md`, and user notifications)." }{ "file": "content/docs/ai/concepts/neo/settings/index.md", "from_bucket": "reviewer-check", "id": "F70", "kind": "spurious", "note": "this matches the approval-mode gates on the permissions page word for word." }{ "file": "content/docs/ai/get-started/neo.md", "from_bucket": "reviewer-check", "id": "F71", "kind": "spurious", "note": "matches the VCS integration docs; the only doubt is how independent the source is, and that doesn't affect readers." }{ "file": "content/docs/ai/get-started/neo.md", "from_bucket": "reviewer-check", "id": "F72", "kind": "spurious", "note": "the claim matches the permissions page section linked in the same paragraph (L68 of `permissions.md`)." }{ "file": "content/docs/ai/get-started/neo.md", "from_bucket": "reviewer-check", "id": "F73", "kind": "spurious", "note": "verified; the remaining doubt is about UI labels only, and the text came over unchanged from the old get-started page." }
History
- 2026-10-22T18:06:37Z
6467df3
initial review (pending publication)
- 2026-10-22T20:31:02Z
a0f9eccbc8
Author pushed fixes in 5dd6e0e and a0f9ecc; F2–F4 and reviewer checks F6–F8, F62, F64, F65, F69 verified resolved