Skip to content

feat(agents): stop publishing the orchestrator prompts - #536

Merged
edwinyjlim merged 3 commits into
dag/m0-match-every-rowfrom
dag/m1-delete-prompts
Nov 17, 2026
Merged

edwinyjlim merged 3 commits into
dag/m0-match-every-rowfrom
dag/m1-delete-prompts

Conversation

@edwinyjlim

Copy link
Copy Markdown
Member

What this does

context-mill publishes skills only. The wizard bundles its orchestrator prompts, so a release carries none.

After this change a release has:

  • no agent-menu.json
  • no agents-<flow>-<type>.md

and everything else it has today.

What goes with them:

  • context/agents/, 49 prompt files across six flows, and its README
  • scripts/lib/agent-generator.js, and the prompt build in scripts/build.js and scripts/dev-server.js
  • the dev server's /agent-menu.json and /agents-… routes
  • the prompt copy in scripts/mirror-dist.js, and the prompt menu check in scripts/verify-mirror.js
  • the prompt upload step in build-release.yml
  • scripts/visual-dags.js and its visual-dags package script, which drew its graphs from context/agents/
  • the tests that read prompt files: agent-generator-flow, integration-observability-flow, error-tracking-env-loading, and one case of error-tracking-link-releases

The old-wizard compatibility test keeps checking skill resolution. It reads the names it checks from its snapshot, which no longer lists prompt files.

.github/CODEOWNERS is not changed. Its four /context/agents/… lines now match no path.

Verification

  • npm test: 419 tests pass.
  • The build passes, and scripts/mirror-dist.js runs on its output.
  • A build of this branch was compared with a build of the branch below it, both from a clean checkout. 50 files are gone, agents/agent-menu.json and the 49 agents/agents-*.md. No other published file differs.

Rollout

Stacked on the match change.

A wizard that fetches its prompts from the latest release cannot plan a run once this ships. Merge it only when all of these hold:

  • cloud runs a wizard release that bundles its prompts and reads no feature flag for them
  • older wizard versions have drained from the run data
  • wizard-agent-dag and wizard-agent-dag-skills are both still on
  • the marketplace and MCP server owners have agreed

🤖 Generated with Claude Code

The wizard bundles its orchestrator prompts, so context-mill publishes
skills only. A release carries no `agent-menu.json` and no
`agents-<flow>-<type>.md`, the dev server serves no prompt routes, and the
mirror copies and verifies the skill menu alone.

`context/agents/`, its generator and the graph script are gone, with the
tests that read prompt files. The old-wizard compatibility test reads the
names it checks from its snapshot.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@edwinyjlim
edwinyjlim added this pull request to stack #539 November 17, 2026 01:10
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/go-sdk
  • /wizard-ci mcp-analytics/python-sdk
  • /wizard-ci mcp-analytics/ruby-sdk
  • /wizard-ci mcp-analytics/rust-sdk
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

@johncwaters johncwaters left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE WITH NITS

See inline comments.

Automated review by Glimmervoid. Not written by a human

@@ -1,188 +0,0 @@
/**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[boundary] MEDIUM

#474 (spend audit flow) is still open and merges cleanly with this, but its new spend-audit-flow.test.js imports buildAgents from ../agent-generator.js and reads agents/agent-menu.json. Once both land, npm test on main fails, and its 11 prompts under context/agents/spend-audit/ never ship. That flow probably wants to move into the wizard's bundled prompts before either merges.

Automated review. Not written by a human

@gewenyu99 gewenyu99 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale ownership in .github/CODEOWNERS: these lines point at context/agents/ folders this PR deletes. Suggested fix:

-/context/agents/error-tracking/                         @PostHog/team-error-tracking
-/context/agents/metrics/                                @PostHog/team-apm
-/context/agents/integration-v2/                         @PostHog/team-growth
-/context/agents/replay-vision/                          @PostHog/team-replay

@edwinyjlim
edwinyjlim marked this pull request as ready for review November 17, 2026 17:08
@edwinyjlim
edwinyjlim requested review from a team as code owners November 17, 2026 17:08
@edwinyjlim
edwinyjlim requested review from JamesPatrickGill, TueHaulund, ablaszkiewicz, fasyy612, hpouillot and ksvat and removed request for a team November 17, 2026 17:08
@edwinyjlim
edwinyjlim merged commit 33b6cf2 into main Nov 17, 2026
17 checks passed
Silthus added a commit that referenced this pull request Nov 17, 2026
main stopped publishing the agent prompts (#536), which removed context/agents
from the dev server's watch list. Keep context/shared there, drop context/agents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants