Changelog

Version history of the MyClaude platform. Every release, what changed, and what to expect next.

This changelog covers the MyClaude platform as a whole: the web application at myclaude.sh, the API, and the CLI. Each entry lists what shipped, what to be aware of, and any breaking changes. Most recent release first.

---

v1.0.0 — 2026-03-25

Initial public launch.

MyClaude is the first marketplace purpose-built for the Claude Code ecosystem. This release ships the complete marketplace infrastructure: discovery, purchase, publishing, and developer tooling.

Marketplace

• 9 product categories: Skills, Squads, Agents, Workflows, Design Systems, Prompts, CLAUDE.md, Applications, and Systems — see Product Types for definitions
• Server-rendered product pages (/p/[slug]) and creator profiles (/u/[username]) with full OpenGraph and structured data metadata for search engine and AI agent discoverability
• Explore page (/explore) with category filtering, search, and sorting — server-rendered for SEO
• Product detail pages with markdown descriptions, user reviews, version history, download controls, and like/share actions
• Creator profiles with published product listings, download stats, and bio
• Landing page with hero section, category browser, and featured products
• Dark terminal aesthetic with warm terracotta palette and phosphor category colors
• Custom design system: Minor Third typography scale, 4px spacing grid, glow-only shadows, 5-level surface hierarchy

Payments

• Stripe Connect Express integration — creators connect their own Stripe accounts and receive payouts directly from Stripe
• 92/8 revenue split — creators receive 92% of each sale, MyClaude retains 8% via Stripe application fee
• Secure purchase flow: Stripe Checkout sessions created server-side with auth verification, orders created exclusively by Stripe webhook handler
• Free and paid product support — free products skip the checkout flow entirely
• No card data touches MyClaude servers — all payment processing handled by Stripe (PCI DSS Level 1)

CLI (@myclaude-cli/cli)

• 12 commands covering the full product lifecycle:

• CONDUIT publishing pipeline: validate vault.yaml schema, scan for secrets and malicious patterns, upload product files to storage, create or update listing
• Product scaffolding with myclaude init generates SKILL.md (or category-appropriate content file) and vault.yaml manifest

Security

• Firebase Auth with email/password and Google OAuth providers
• Dual Firebase SDK architecture — Admin SDK for server operations, Client SDK for browser operations, with strict import boundaries preventing cross-contamination
• Firestore security rules enforce data ownership at the database layer, independent of application logic
• Signed URLs for paid product downloads with 5-minute expiry — fileUrl field is stripped from all client-facing API responses
• Firebase Storage rules set to allow read: if false for product files — access only via server-generated signed URLs
• Webhook-only order creation — no client-side code path can create an order, preventing purchase forgery
• Rate limiting on all mutation API routes (60 req/min general, 10 req/min checkout, 20 req/min downloads)
• Server-side input sanitization with DOMPurify before rendering user-generated content
• Automated content scanning on every publish via CONDUIT pipeline: secrets detection, malicious pattern analysis, policy enforcement, manifest validation
• 167 end-to-end and integration security tests covering auth flows, payment integrity, file access controls, and injection prevention

Documentation

• PRISM documentation system: 46+ pages across 3 surfaces
  • Human surface: structured guides with Diataxis framework (tutorials, how-tos, explanations, references)
  • Agent surface: agent_summary frontmatter field on every page for AI agent consumption
  • GEO surface: geo_quotable frontmatter field, structured data (schema_type), and keyword optimization for generative search engines
• 7 sections: Getting Started, Buyers, Creators, CLI, API, Security, Legal
• Built with Fumadocs on Next.js — MDX content with custom components

Infrastructure

• Next.js 16 App Router deployed on Vercel with edge network distribution
• Cloud Firestore for all application data (products, users, orders, reviews)
• Cloudflare R2 for product file storage — S3-compatible with zero egress fees
• Firebase Storage for user-uploaded assets (avatars, screenshots)
• SSR for all SEO-critical pages (/explore, /p/[slug], /u/[username]); client-side rendering for authenticated dashboard pages
• TypeScript strict mode across the entire codebase
• Tailwind CSS v4 with custom design tokens and utility classes

Known limitations at launch

• Search is client-side filtering only — full-text search with a dedicated search engine is planned for v1.1
• No email notifications for purchases, product updates, or review activity yet
• Admin moderation tools are internal-only — no public-facing admin dashboard
• Single language (English) — i18n infrastructure and translation dictionaries exist but only English strings are shipped
• No product collections or curated lists — all discovery is via search and category browse
• No creator analytics beyond basic download counts

---

Upcoming

Features under active development or planned for near-term releases. Dates are targets, not commitments.

v1.1 — Search and notifications

Targeted for Q2 2026. Focus: discoverability and communication.

• Full-text product search powered by a dedicated search engine (Algolia or Typesense under evaluation)
• Email notifications for purchase confirmation, product update alerts, new review notifications, and weekly creator digest
• Verified creator badges — manual verification initially, automated pipeline later
• Improved explore page with trending products, "new this week" section, and recommendation signals

v1.2 — Admin and moderation

Targeted for Q3 2026. Focus: marketplace governance at scale.

• Public admin dashboard for content moderation with queue management and audit trail
• Automated content re-scanning on a recurring schedule to catch newly identified patterns
• Creator analytics dashboard with revenue charts, download trends, and geographic distribution
• Bulk product management tools for creators with large catalogs

v1.3 — Internationalization

Targeted for Q3 2026. Focus: global accessibility.

• Full i18n for the web UI (English, Portuguese, Spanish) using the existing translation dictionary infrastructure
• Localized product metadata support — creators can provide descriptions in multiple languages
• Currency display localization based on user region
• Right-to-left layout support evaluation

Future

These features are planned but not yet scheduled:

• MCS certification pipeline — MyClaude Certified Standard automated testing and badge issuance for products that pass quality, security, and usability thresholds
• Product collections — curated lists and themed bundles (e.g., "Essential Security Skills", "Starter Pack for New Teams")
• Creator teams — organization accounts with shared product ownership, revenue splitting, and role-based access
• API rate limit dashboard — creators can monitor their API usage and adjust rate limits on their published products
• Dedicated status page — status.myclaude.sh with real-time monitoring, historical uptime, and incident timeline
• Webhook integrations — notify external systems when products are purchased, updated, or reviewed

---

Versioning policy

MyClaude follows semantic versioning for platform releases:

Major versions indicate breaking changes to the API or CLI. Minor versions add features without breaking existing integrations. Patch versions fix bugs.

Breaking changes, when they happen, will be announced at least 2 weeks in advance through the changelog and the MyClaude status channels.

Related pages

• System Status — current platform health
• Architecture — how the system is built
• CLI Commands — full CLI reference