Build with your agent

You should not need to learn Chasing Mastery infrastructure before you can test a good practice idea. Choose the coding agent you already use, describe the member experience in ordinary language, and let the Chasing Mastery Author workflow handle the brief, standalone project, pinned tools, preview, proof, and review handoff.

All three routes use the same Agent Skills, version-3 package brief, public SDK, Workbench, Connector Lab, and immutable release format. The invocation syntax changes; the authored project does not. You can start in one provider and continue in another without migration or regenerated source.

Current channel: Developer Preview 0.3.0. Local package and connector authoring is real and credential-free. Optional Club tools currently use the clearly labeled staging OAuth/MCP resource. The OpenAI universal-directory listing is prepared but cannot be published until production MCP deployment and external review are complete.

Certified hosts

The exact public archive—not a source checkout—has completed both the complete Experience Suite/Workbench journey and the Station connector/Connector Lab journey on:

• Linux x86-64;
• Apple Silicon macOS;
• native Windows 11 x86-64.

Read the release-bound certification record or follow certification.report from the latest release JSON. Windows uses native PowerShell and does not require WSL. Package authoring stays fully unprivileged. The first Windows connector run may request one clearly bounded, Station-owned UAC preparation for its AppContainer sandbox; the coding agent itself must remain an ordinary user. Intel macOS is not a certified authoring host in this release.

Choose your provider

Only the installation step is provider-specific. Pick the agent you already use; every tab creates the same durable project and uses the same public SDK, Workbench, proof, and release format.

shasum -a 256 chasing-mastery-author-openai-preview-0.3.0.zip

Get-FileHash .\chasing-mastery-author-openai-preview-0.3.0.zip -Algorithm SHA256

unzip chasing-mastery-author-openai-preview-0.3.0.zip
codex plugin marketplace add ./chasing-mastery-developers
codex plugin add chasing-mastery-author@chasing-mastery-developers

Use $build-chasing-mastery-package to build a practice experience for the goal
below. Interview me only for choices that materially affect the member
experience, then open the real result in Workbench.

[Describe the pursuit, one Attempt, the result, and the ideal player experience.]

What the agent should do next

The first interaction should feel like product design, not environment setup:

1. recognize whether the idea needs a package, a connector, or both;
2. ask one compact batch of only the unanswered product questions;
3. restate the member promise, Attempt, result, progression, player, creator presentation, correction policy, and edge cases;
4. write the provider-neutral authoring brief;
5. bootstrap the standalone project without sudo, a global CM CLI, or a platform checkout;
6. implement against public SDKs and open the real artifact in Workbench or Connector Lab;
7. iterate visibly until you approve the experience;
8. produce immutable review bytes only after conformance passes and you say it is ready.

The bootstrap uses exact Node 24.18.0. If the host has a different version, it downloads the platform's checksum-pinned portable runtime into the author cache; it never replaces or globally upgrades the developer's Node installation. On Windows, connector projects also obtain exact project-local Rust 1.95.0 and the reviewed native Connector Lab/AppContainer launcher without installing a global language toolchain.

Continue with the complete authoring workflow to see the project that remains after the conversation ends.

Sign-in is intentionally late

Designing, running, and packing an experience is local. No Chasing Mastery account is required. Sign-in begins only if you explicitly ask the agent to search your Club, submit exact private package bytes, or set up a Pursuit and Sprint. That action must open first-party OAuth consent with only the necessary club.read, club.manage, or packages.submit scopes.

Never paste a password, cookie, access token, publisher key, Station credential, or billing secret into the conversation. The plugin does not need one.

Updates and rollback

• Codex preview: download the new semantic-version bundle, verify its release record, add or refresh that marketplace, and reinstall the plugin. Start a new thread.
• Claude: run claude plugin marketplace update chasing-mastery-developers, then reinstall when the marketplace advertises a new plugin version.
• Rollback: use a retained versioned archive and release record. Never overwrite old bytes under the same semantic version.

The latest release record is the machine-readable source of version, payload, archive, provider, support, and MCP channel truth.