40 Commits

Author	SHA1	Message	Date
BilalG1	57ff5d3ce9	feat(hexclave): PR 2 — visible rebrand (Hexclave brand goes public) (#1481) ... ## Summary **Stacked on [#1475](https://github.com/hexclave/stack-auth/pull/1475)** (`cl/hexclave-pr1`, the invisible compatibility layer). Diff vs that base = the actual PR 2 code. This is **PR 2 of the Stack Auth → Hexclave rebrand: the visible flip**. Old wire identifiers (cookies, request/response headers, Bearer prefix, JWT issuers, MCP tool name) keep working indefinitely via PR 1's dual-accept. This PR flips every user-visible surface — package names taught in docs, SDK class names in code examples, dashboard setup snippets, page titles, error messages, email content, CLI binary, default base URLs, GitHub repo slug, contributor guidance — to the Hexclave brand. See [`RENAME-TO-HEXCLAVE.md`](./RENAME-TO-HEXCLAVE.md) → *"PR 2: Rebrand to Hexclave (visible)"* for the full per-work-area spec. ## What's implemented (per the plan's PR 2 scope) - **SDK base URLs** flipped: `defaultBaseUrl` and `defaultAnalyticsBaseUrl` in [common.ts](packages/template/src/lib/stack-app/apps/implementations/common.ts:127) → `https://api.hexclave.com` / `https://r.hexclave.com`. PR 1's [`getHardcodedFallbackUrls`](packages/stack-shared/src/utils/urls.tsx:199) table now keys on the Hexclave domain. - **Domain inventory sweep** (16 subdomains from the plan): every `api/app/docs/discord/demo/mcp/skill/feedback/test/preview/r/api2/api.staging/idp-jwk-audience/built-with.stack-auth.com` reference in production code, docs-mintlify, examples, READMEs, and contributor guidance flipped to `*.hexclave.com`. Carve-outs: PR 1's intentional JWT issuer dual-accept table in [tokens.tsx](apps/backend/src/lib/tokens.tsx), the legacy `./docs/` folder, the `unified-docs-widget` allowlist (deliberately accepts both during DNS transition), and `url-targets.ts` hosted-component default (baked into existing customer deploys). - **`@deprecated` JSDoc** on every `Stack*` public export ([packages/template/src/lib/stack-app/index.ts](packages/template/src/lib/stack-app/index.ts) + [packages/template/src/index.ts](packages/template/src/index.ts)) — `StackClientApp`, `StackServerApp`, `StackAdminApp` + every constructor/options/JSON type, `StackHandler`, `StackProvider`, `StackTheme`, `useStackApp`, `defineStackConfig`, `StackConfig`. Hexclave\* aliases are now canonical. - **Runtime `console.warn`** ([packages/template/src/internal/deprecation-warning.ts](packages/template/src/internal/deprecation-warning.ts)) — once-per-process when the SDK is loaded from a `@stackframe/*` artifact. Detection uses the existing `STACK_COMPILE_TIME_CLIENT_PACKAGE_VERSION_SENTINEL` (rewritten at build time to e.g. `js @stackframe/stack@2.8.92` or `js @hexclave/next@1.0.0`); `@hexclave/*` mirror artifacts short-circuit the warning. - **Tier 3 data migration**: new idempotent SQL migration [`20260523000000_rename_internal_project_to_hexclave`](apps/backend/prisma/migrations/20260523000000_rename_internal_project_to_hexclave/migration.sql) — updates the internal Project `displayName` 'Stack Dashboard' → 'Hexclave Dashboard' and `description` only if both still hold the pre-rebrand defaults. Operator-renamed projects untouched, missing row no-ops, re-runs are no-ops. [`seed.ts`](apps/backend/prisma/seed.ts:87) default flipped. `getSharedEmailConfig("Stack Auth")` → `("Hexclave")`. - **Tier 4 brand strings** (mechanical sweep, ~340 files): - Page + OpenAPI titles (Hexclave API / Dashboard / REST API / Webhooks API / Documentation). OpenAPI `info.description` documents `X-Hexclave-*` headers as canonical with compat note on `X-Stack-*`. - `HexclaveAssertionError` message text ([errors.tsx:71](packages/stack-shared/src/utils/errors.tsx:71)) — "an error in Stack." → "an error in Hexclave." - Known-error message templates ([known-errors.tsx](packages/stack-shared/src/known-errors.tsx)) flipped to lead with `x-hexclave-*` + the new `docs.hexclave.com` URL; legacy `x-stack-*` mentioned as compat aliases. **25 e2e test files updated in lockstep**. - Email content: failed-emails-digest body, sendTestEmail recipient (now `sent-with-hexclave.com`), test-email-recipient default. - `CHANGELOG.md` title → "Hexclave Changelog". - `AGENTS.md` env var convention: new vars prefix `HEXCLAVE_` / `NEXT_PUBLIC_HEXCLAVE_` for Category A/B; legacy `STACK_*` explicitly noted as accepted via PR 1's dual-read. - **CLI / init wizard**: - Every dashboard setup snippet, init-stack template, and docs-mintlify page teaches `npx @hexclave/cli@latest init` (was `@stackframe/stack-cli`). [setup-page.tsx](apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/setup-page.tsx) + [link-existing-onboarding](apps/dashboard/src/app/(main)/(protected)/(outside-dashboard)/new-project/page-client-parts/link-existing-onboarding.tsx). - [init-stack](packages/init-stack/src/index.ts:634) `STACK_*_INSTALL_PACKAGE_NAME_OVERRIDE` defaults flipped to `@hexclave/*`. - Generated `stack/client.ts` / `stack/server.ts` import from `@hexclave/next` and reference `HexclaveClientApp` / `HexclaveServerApp`. - Internal `StackAuthKeys` dashboard component renamed to `HexclaveKeys`. - **docs-mintlify rewrite** (legacy `./docs/` intentionally untouched per scoping decision): - **78 MDX files swept**. `@stackframe/{react,stack,js,tanstack-start,...}` → `@hexclave/{react,stack,js,...}` in install snippets and code blocks; `Stack*` SDK class names → `Hexclave*` in all code examples; 'Stack Auth' brand phrase → 'Hexclave'. - `openapi/{server,admin,client,webhooks}.json` titles → 'Hexclave REST API' / 'Hexclave Webhooks API'. - **Generators flipped before regeneration**: - [`packages/stack-shared/src/helpers/init-prompt.ts`](packages/stack-shared/src/helpers/init-prompt.ts), [`/ai/prompts.ts`](packages/stack-shared/src/ai/prompts.ts), [`apps/backend/src/lib/ai/prompts.ts`](apps/backend/src/lib/ai/prompts.ts), [`apps/backend/src/lib/ai/tools/create-email-{template,draft}.ts`](apps/backend/src/lib/ai/tools/create-email-template.ts), [`apps/skills/src/app/route.ts`](apps/skills/src/app/route.ts) (taught MCP tool → `ask_hexclave` with compat note; CLI binary teach → `hexclave`), [`docs-mintlify/snippets/home-prompt-island.jsx`](docs-mintlify/snippets/home-prompt-island.jsx), [`packages/template/README.md`](packages/template/README.md) + integrations/convex/component/README.md. - `generate-sdks` propagated changes to `packages/{react,stack,js}`. - **OpenAPI dual-documentation**: [`apps/backend/src/app/api/latest/route.ts`](apps/backend/src/app/api/latest/route.ts) now lists `X-Hexclave-*` headers as primary documented schemas with `X-Stack-*` duplicates marked `.optional()` (both accepted at runtime by PR 1's normalize-at-proxy shim). - **`@stackframe/emails` virtual module**: dual-aliased to `@hexclave/emails` at the bundler boundary ([email-rendering.tsx:89](apps/backend/src/lib/email-rendering.tsx:89)). Stored email templates continue to import from either name; new AI-generated templates and the system prompt teach `@hexclave/emails`. - **Tier 2 mirror-publish wiring** (new this PR, lays the groundwork for `@hexclave/*` first publish): - [`scripts/rewrite-packages-to-hexclave.ts`](scripts/rewrite-packages-to-hexclave.ts) — rewrites 9 publishable `@stackframe/*` → `@hexclave/*` `package.json` files (reads `HEXCLAVE_VERSION` env or `--version=` flag), pins cross-deps to the shared `@hexclave` version, registers `hexclave` bin alongside `stack` for `@hexclave/cli`. - [`.github/workflows/npm-publish.yaml`](.github/workflows/npm-publish.yaml) appended with rewrite-then-republish step. `pnpm publish` skips already-on-npm versions so reruns are safe. - **Sender email domain**: `noreply@stackframe.co` → `noreply@sent-with-hexclave.com` (the dedicated transactional-sender domain split per the plan, to isolate bulk deliverability from `hexclave.com` reputation); `security@` / `team@stack-auth.com` inbound mailboxes → `@hexclave.com`. - **Self-host docs**: docker network / container names in the bash examples flipped from `stack-auth` to `hexclave` (`hexclave-postgres`, `hexclave-clickhouse`, `hexclave.env`). The docker image tag `stackauth/server:latest` stays per the plan's locked decision. - **GitHub repo slug**: `hexclave/stack-auth` → `hexclave/hexclave` in every `package.json` `repository` field, README link, CHANGELOG raw-asset URL. ## Carve-outs (deliberately untouched) - **[`apps/backend/src/lib/tokens.tsx`](apps/backend/src/lib/tokens.tsx)** JWT issuer dual-accept table — PR 1 intentional infrastructure, kept indefinitely. - **Legacy `./docs/` folder** — per scoping decision (only `docs-mintlify/` rewritten). - **`unified-docs-widget` hostname allowlist** — accepts both `.hexclave.com` (canonical) and `.stack-auth.com` (transition window) for DNS rollout. - **`url-targets.ts`** hosted-domain default `.built-with-stack-auth.com` — wire identifier baked into existing customer deploys; indefinite read-fallback. - **Binary visual assets** (logos, favicons, OG images, README screenshots) — out of scope for this PR. Need design work; tracked separately. ## Verification - **`pnpm typecheck`** on `packages/{template,stack-shared,react,stack,js}` + `apps/dashboard`: **all green**. The remaining backend / e-commerce-demo typecheck errors are pre-existing (Prisma codegen output + `./generated/api-versions.json` not present in fresh worktrees without `pnpm run codegen-prisma` + a live DB) and unrelated to this diff. - **`pnpm lint`** on the same 6 packages: all green. - **Final grep** for residual `Stack Auth` / `stack-auth.com` / `@stackframe/stack-cli@latest` references: zero outside the intentional carve-outs above. - **25 e2e test files updated in lockstep** with the known-error message changes (asserted strings flipped to match the new x-hexclave-* + compat-note messages). ## Deploy blockers (ops sequencing before this rebrand goes live) This PR is code-complete, but the rebrand's visible surfaces (SDK default URLs, dashboard links, npm READMEs, REST error messages, runtime deprecation warning) all point at `*.hexclave.com` / `@hexclave/*` resources that don't exist yet. None of these are fixable from a PR — they're ops/registrar/npm work that has to be sequenced before merging this to a release tag. Suggested ordering, hardest blockers first: ### Tier 1 — required before customer-facing deploy (everything below this line *will visibly break customers on day 1* if skipped) 1. **DNS + TLS for `api.hexclave.com` + `api1./api2.hexclave.com`** → must point at the same backend that serves `api.stack-auth.com` (or a backend that mirrors PR 1's dual-accept). The SDK's new `defaultBaseUrl` is `https://api.hexclave.com`; every customer that relied on the old default and upgrades to a post-PR2 SDK build sends API requests here. Until this resolves, every default-config customer's API call NXDOMAINs. 2. **DNS for `app.hexclave.com`** → the dashboard. Referenced in the SDK's default-error messages ("Please create a project on the Hexclave dashboard at https://app.hexclave.com"), the init-stack flow's `wizard-congrats` redirect, and the OAuth dashboard handoff. 3. **DNS for `docs.hexclave.com`** + Mintlify deploy → the SDK runtime deprecation warning (`https://docs.hexclave.com/migration`), every README, every "Learn more" link in the dashboard, and every REST API error body (`/api/overview#authentication`) points here. The MDX is in this PR; the docs build target needs DNS. 4. **DNS for `mcp.hexclave.com`** → the MCP server endpoint that every taught agent integration (`claude mcp add ...`, `cursor`, `codex`, `vscode`) registers. Until this resolves, every `npx @hexclave/cli@latest init` MCP-registration step fails. 5. **Reserve the `@hexclave` npm scope + set repo variable `HEXCLAVE_VERSION`** → the mirror-publish step in `.github/workflows/npm-publish.yaml` is gated on this variable. Without it, the entire taught onboarding command `npx @hexclave/cli@latest init` 404s from the npm registry, *and* every README that says "install `@hexclave/next`" leads to install failure. Pick the initial version intentionally (`1.0.0` or aligned to `@stackframe/stack`); don't accept a silent default. ### Tier 2 — required before announcing the rebrand publicly (lookalike or low-traffic surfaces, but visibly broken) 6. **DNS for `r.hexclave.com`** → the analytics beacon `defaultAnalyticsBaseUrl`. Silent failure if missing (analytics drops), but should land alongside Tier 1. 7. **Register `sent-with-hexclave.com` + full email auth (SPF / DKIM / DMARC)** → the new default sender domain for shared-sender transactional emails. Without it the dashboard "send test email" path emits bounces, and shared-sender flows (`getSharedEmailConfig("Hexclave")`) deliver to spam at best. 8. **MX + SPF / DMARC for `hexclave.com`** → `team@hexclave.com` and `security@hexclave.com` mailboxes. The security disclosure mailbox is referenced in [`.github/SECURITY.md`](.github/SECURITY.md); `team@hexclave.com` is the actual recipient of internal feedback emails sent at runtime by [`apps/backend/src/lib/internal-feedback-emails.tsx`](apps/backend/src/lib/internal-feedback-emails.tsx). Today, every runtime feedback email bounces. 9. **DNS for `skill.hexclave.com`** → the canonical AI-agent skill fetch URL (the agent bootstrap pivot). Without it, the entire "agent downloads `SKILL.md` from a known URL" flow taught in [`packages/stack-shared/src/helpers/init-prompt.ts`](packages/stack-shared/src/helpers/init-prompt.ts) fails. 10. **Create `github.com/hexclave/hexclave` as a public repo** (even as a redirect to `hexclave/stack-auth`) **OR** rewrite every `package.json` `"repository"` field + dashboard footer "view on GitHub" link to point at `hexclave/stack-auth` (which already exists). Currently every npm package page's "Repository" link is dead, and the dashboard's GitHub button + dev-tool repo link are dead. ### Tier 3 — broken but low-visibility / low-traffic 11. **DNS for `discord.hexclave.com`** → Discord invite redirect, used in every README's chip and the dashboard footer. 12. **DNS for `demo.hexclave.com`** → "✨ Demo" badge in every npm package README. Broken-image badge on the package page. 13. **DNS + TLS for `built-with-hexclave.com`** → optional hosted-handler domain (the default reverted to `.built-with-stack-auth.com` in this PR's carve-outs, so this only matters for projects that manually flip). ## Other follow-ups (not deploy-blocking) - **E2E snapshot regen across the full suite** for the dual-emitted `x-hexclave-*` response headers (PR 1 follow-up; `vitest -u` in CI absorbs). - **Binary visual assets** — logos, favicons, OG images, README screenshots; need design pass. - **Backend OpenAPI fumadocs regen** in CI flow — the JSON files in `docs-mintlify/openapi/` are committed but regen runs in CI. Verify the workflow that does this still works against the post-PR2 source. - **Backend typecheck infra debt** — needs `codegen-prisma` + `codegen-route-info` to clear; pre-existing, unaffected by this PR. ## Test plan - [ ] CI runs full e2e suite (with `vitest -u` to absorb residual snapshot deltas, then committed back). - [ ] Spot-check: new `@hexclave/cli init` (once published) generates `hexclave.config.ts` and works against a fresh project. - [ ] Spot-check: existing customer with `@stackframe/stack` import sees the once-per-process `console.warn` recommending `@hexclave/next` on SDK init. - [ ] Manual: dashboard setup page renders the `npx @hexclave/cli@latest init` snippet and the `x-hexclave-publishable-client-key` API header in the curl example. - [ ] Manual: a fresh `pnpm run prisma migrate` against a clean DB sets the internal project displayName to 'Hexclave Dashboard'. --------- Co-authored-by: Konstantin Wohlwend <n2d4xc@gmail.com>	2026-05-26 19:18:20 -07:00
Konstantin Wohlwend	d68631ea4f	Update GitHub URL	2026-05-19 10:27:53 -07:00
Mantra	c808e23b7d	Data-grid overhaul + session-replays / team-payments dashboard surfaces (#1424) ... ## Summary Refactors the dashboard data-grid into a smaller, URL-state-aware primitive and lands several new dashboard surfaces around it: per-user session replays, team-level analytics and payments, and pagination for permission definitions. Also moves session replays out from under `/analytics` to a top-level surface and adds a `project_user.last_active_at` index that the new weekly-active metrics depend on. **Base:** `dev` → **Head:** `refactor/data-grid-and-dashboard-surfaces` **Scope:** 91 files, +5,644 / −1,858. Assets in [this gist](https://gist.github.com/mantrakp04/01bf8db4c71ec7a119b73d6ee60717a7). ## Screenshots Captured from a local dev server (dashboard at `:8101`, dummy project seeded with 26 users). Standard viewport **1920×1200**, widescreen **2560×1440**. ### Users list — data-grid overhaul in context | Light | Dark | | --- | --- | |  |  | Widescreen: | Light | Dark | | --- | --- | |  |  | ### User detail — new session-replays card + weekly metrics | Light | Dark | | --- | --- | |  |  | Widescreen: | Light | Dark | | --- | --- | |  |  | ### Session replays — moved out of `/analytics` | Light | Dark | | --- | --- | |  |  | Widescreen: | Light | Dark | | --- | --- | |  |  | ### Project permissions — new pagination | Light | Dark | | --- | --- | |  |  | Widescreen: | Light | Dark | | --- | --- | |  |  | ### Other migrated surfaces | Page | Light | Dark | | --- | --- | --- | | Project picker |  |  | | Overview / setup |  |  | | Teams list |  |  | | Team permissions |  |  | | API keys |  |  | ### Scroll behaviour — new data-grid on the users list | Light | Dark | | --- | --- | |  |  | ## What's new - **`packages/dashboard-ui-components/src/components/data-grid`** — rewritten. Trimmed `data-grid.tsx` from ~1.7k LOC, split sizing logic into `data-grid-sizing.ts`, added `use-url-state.ts` for URL-synced state, and added `data-grid.test.tsx`. - **Session replays** moved from `…/analytics/replays` to `…/session-replays` (top-level surface). New `user-session-replays.tsx` card on the user detail page; new internal `route.tsx` to feed it. - **Teams** detail page gains `team-analytics.tsx` and `team-payments.tsx`. - **Permissions** — new shared `permission-definitions-pagination.ts` consumed by both project and team permission CRUD routes. - **Backend** — Prisma migration `add_project_user_last_active_at_idx` + a `lastActiveAt` index that backs the new weekly-active metrics. - **Polish** — `editable-input`, `inline-save-discard`, `settings.tsx`, walkthrough steps, and several data-table components touched in line with the data-grid rewrite. ## Notes for reviewers - The data-grid rewrite changes the *shape* of state (now URL-synced), not just internals. Consumers in `apps/dashboard/src/components/data-table/*` were updated to match — please scan those for any missed knobs. - The `analytics/replays` → `session-replays` rename is git-tracked as renames; diffs should be small in those files. - New SDK surface in `packages/template/src/lib/stack-app/session-replays/index.ts` and additions in `admin-app-impl.ts` / `server-app-impl.ts` mean OpenAPI specs (`docs-mintlify/openapi/{admin,client}.json`) regenerate; the diff is mostly mechanical. ## Test plan - [ ] `pnpm typecheck` clean - [ ] `pnpm lint` clean - [ ] Data-grid unit tests pass (`packages/dashboard-ui-components`) - [ ] Manual: users list — column resize, sort, filter, paginate; URL state reflects each change and survives reload - [ ] Manual: user detail — session-replays card lists replays; weekly-metrics card renders without `lastActiveAt` index migration applied (i.e. on a fresh DB) and after applying it - [ ] Manual: project + team permissions — pagination cursor advances and stays consistent under search - [ ] Manual: session-replays top-level page loads; old `/analytics/replays/...` URL path is no longer expected to be linked anywhere <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Session Replays app (embedded mode, search, sorting, share links) * Tabbed Team pages with Team Analytics and Team Payments dashboards * Server-backed cursor pagination, debounced search, and infinite-scroll for teams/users/permissions * **UX** * Permission and member tables refresh after edits; permission creation triggers table refresh * Users list supports sorting by last-active * **Performance** * Index added to speed ProjectUser last-active queries * **Documentation** * API/SDK docs updated for pagination and new query params * Contributor guidance: explicit git-safety rules added (no destructive git ops without consent) * **Tests** * Added e2e tests for pagination and filtering on list endpoints <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-05-15 14:16:47 -07:00
Mantra	647883c7ac	Move MCP server into a standalone apps/mcp app (#1405) ... ## Summary Splits the Stack Auth MCP server out of `apps/backend` and into a dedicated Next.js app at `apps/mcp/`, served on port `:42` (suffixed via `NEXT_PUBLIC_STACK_PORT_PREFIX`) and exposed in production at `https://mcp.stack-auth.com/mcp`. The backend no longer carries the MCP transport route; clients now point at the new host. Base: `dev` → Head: `chore/move-mcp-to-a-sep-app` Scope: 34 files, +1425 / −353 ## What changed - **New app** `apps/mcp/` — standalone Next.js + `@vercel/mcp-adapter`, with: - `src/app/api/internal/[transport]/route.ts` — MCP transport handler (moved from backend) - `src/app/mcp/route.ts`, `src/app/route.ts` — public landing + setup page - `src/app/health/route.ts` — health check - `src/mcp-handler.ts`, `src/setup-page.ts`, `src/analytics.ts` - **Backend** drops `apps/backend/src/app/api/internal/[transport]/route.ts` (−105) — MCP code is gone from the backend image. - **Dashboard** install hint updated to point at `https://mcp.stack-auth.com/mcp` (was `/`). - **Dev launchpad** gets an MCP tile so the new service shows up alongside the rest of the local stack. - **CI** workflows (`db-migration-backwards-compatibility`, `e2e-api-tests*`) start the MCP service in the background before running tests. - **Docs** (`docs-mintlify`, `docs/`) and `init-stack` / `init-prompt` updated to reference the new URL. - **E2E** `apps/e2e/tests/backend/endpoints/api/v1/internal/mcp.test.ts` reworked to hit the new host; `helpers.ts` and env files gain an MCP base-URL var. ## Visuals ### New `apps/mcp` setup page (`https://mcp.stack-auth.com/`) The standalone app's root now serves a self-contained MCP setup guide with per-client instructions (Cursor, VS Code, Codex, Claude Code, Claude Desktop, Windsurf, ChatGPT, Gemini CLI):  ### Dev launchpad now lists the MCP service New tile at port suffix `:42`, importance 2, alongside Backend / Dashboard / Demo app:  ## Notes for reviewers - The MCP transport endpoint moved path: it was mounted under `/api/internal/[transport]` in the backend; in the new app it's at the same path but on the dedicated host. The public-facing URL is `https://mcp.stack-auth.com/mcp`. - `apps/mcp` ships its own PostHog analytics client (`src/analytics.ts`) so the backend doesn't have to proxy events for it anymore. - Port allocation: `${PORT_PREFIX}42` (default `8142` in dev). Picked to fit the existing dev-launchpad importance-2 row. - No DB migrations. ## Test plan - [x] `apps/mcp` builds and `pnpm dev` serves on `:8142` - [x] Dev launchpad renders the new MCP tile (screenshot above) - [x] MCP setup page renders client tabs (screenshot above) - [x] E2E `mcp.test.ts` updated to hit the new host - [ ] CI green on `e2e-api-tests*` and `db-migration-backwards-compatibility` workflows (they were touched to start the MCP service) - [ ] `init-stack` / `mcp.ts` install flow lands users on the new URL <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Standalone MCP app added with a public /mcp endpoint and health check. * MCP appears in the dev-launchpad apps list. * **Documentation** * MCP endpoint updated to https://mcp.stack-auth.com/mcp in all setup guides and installer snippets. * Setup page enhanced with detailed client install tabs and instructions. * **Chores** * MCP service integrated into CI/e2e workflows and local env configs. <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-05-07 15:22:44 -07:00
Konsti Wohlwend	765b0f4e29	New setup (#1413)	2026-05-06 12:03:06 -07:00
Mantra	39b2f56ff1	mcp / tools update + internal tool (#1283) ... - Added new internal API endpoint for documentation tools, allowing actions such as listing available docs, searching, and fetching specific documentation by ID. - Updated environment configuration to support optional internal secret for enhanced security. - Refactored existing search functionality to utilize the new docs tools API instead of the previous MCP server. - Improved error handling and response parsing for documentation-related requests. - Expanded documentation to clarify the relationship between the new tools and existing API functionalities. This update streamlines the documentation access process and enhances the overall developer experience. <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Non-stream AI responses now include a consolidated finalText for clearer answers. * Added an internal docs-tools HTTP API to power doc listing, search, and fetch with optional header-based access control and configurable service origin. * **Refinement** * Consolidated multiple doc tooling paths into a single question-focused flow; backend now routes to the unified docs-tools endpoint. * **Documentation** * Updated guides and knowledge base to describe the new docs query flow and optional env configuration. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-12 23:32:22 +00:00
Konstantin Wohlwend	05036477ff	Fix docs icon size	2026-04-06 22:41:39 -07:00
Konstantin Wohlwend	1a698b2295	More JWT docs updates	2026-03-30 18:14:19 -07:00
Konstantin Wohlwend	d32de28430	Update JWT docs	2026-03-30 18:10:01 -07:00
Konstantin Wohlwend	cf53313ff4	rename signed_up_at_millis JWT claim to signed_up_at	2026-03-30 17:43:06 -07:00
Konstantin Wohlwend	9cbbafeb65	signed_up_at_millis JWT claim	2026-03-30 17:39:28 -07:00
Konstantin Wohlwend	631b2556c9	Add requires_totp_mfa to JWT docs	2026-03-30 17:09:53 -07:00
Mantra	3efb226c59	make publishable client keys truly optional ig (i hope) (#1274) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Documentation * Updated setup instructions across all documentation to clarify that the publishable client key is only required when your project configuration enforces it, removing confusion about unconditional requirements. <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-03-23 15:09:01 -07:00
Madison	46cacd4b56	Add connected accounts back in	2026-03-13 18:20:21 -05:00
Aman Ganapathy	59a65bb863	[Docs] [Feat] Enabling client side events for non internal projects, updating docs for payments and analytics (#1250)	2026-03-13 11:52:10 -07:00
BilalG1	8e03677aad	change cli init across docs (#1245) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated installation and setup instructions across all documentation, README files, and getting started guides to use the new Stack CLI command format for project initialization. Users will now see the updated command throughout documentation and framework-specific setup guides. <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-03-13 10:45:24 -07:00
Konstantin Wohlwend	c8b516833e	Add requires_totp_mfa to JWT	2026-03-02 10:09:47 -08:00
promptless[bot]	9f13d410fc	docs: Document payment email templates (#1133) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/change-history/e6033b34-4005-4a9e-9d21-d809e2d57896) Adds documentation for the two new built-in email templates: `payment_receipt` (sent when payments succeed) and `payment_failed` (sent when payments fail). Updates the Emails guide to list these new templates alongside existing authentication templates, and adds a "Payment Emails" section to the Payments guide explaining that these notifications are sent automatically for both one-time purchases and subscription renewals. ### Trigger Events <details> <summary><a href="https://github.com/stack-auth/stack-auth/pull/1106">stack-auth/stack-auth PR #1106: payment email templates</a></summary> <br> **Promptless Research** (1 GitHub PR) - [Reviewed stack-auth/stack-auth#1106](https://github.com/stack-auth/stack-auth/pull/1106) **Agent Response** > I've completed the documentation updates for PR #1106. Here's a summary of the changes: > > ## Documentation Suggestion Created > > **Title:** Document payment email templates > > **Changes made:** > > 1. **Emails guide** (`docs/content/docs/(guides)/apps/emails.mdx`): > - Added `payment_receipt` and `payment_failed` to the "Built-in Email Templates" section, keeping them consistent with the existing format for other templates > > 2. **Payments guide** (`docs/content/docs/(guides)/apps/payments.mdx`): > - Added a new "Payment Emails" subsection under Dashboard Management explaining that Stack Auth automatically sends email notifications when payments are processed > - Documents both templates with their key details (receipt link, failure reason, etc.) > - Notes that these apply to both one-time purchases and subscription renewals > - Includes a pointer to where templates can be customized > > The suggestion is ready for review at: https://app.gopromptless.ai/change-history/e6033b34-4005-4a9e-9d21-d809e2d57896 </details> --- **Help us improve Promptless** — If this suggestion missed the mark, please [share quick feedback](https://app.gopromptless.ai/change-history/e6033b34-4005-4a9e-9d21-d809e2d57896?openFeedback=1). *If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)* Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-02-24 10:47:00 -06:00
promptless[bot]	59b834ae4b	docs: Document isRestricted and restrictedReason JWT claims (#1136) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/change-history/ea7c7471-778d-42ea-9845-fa380f013560) Documents the new `is_restricted` and `restricted_reason` JWT claims introduced for the onboarding/restricted users feature. Updates the JWT documentation to explain these fields in the claims section, adds them to the example payload, documents the restricted user token structure, and adds the `include_restricted` JWKS parameter for manual token verification. ### Trigger Events <details> <summary><a href="e400985754...de0f937f46">stack-auth/stack-auth commit (dev): de0f937 [CHANGELOG] - 2026.01.21</a></summary> <br> **Promptless Research** (1 webpage, 1 GitHub PR) - [Read webpage from github.com](e400985754...de0f937f46) - [Reviewed stack-auth/stack-auth#1069](https://github.com/stack-auth/stack-auth/pull/1069) **Agent Response** > I've completed my analysis of the changelog entry and created the necessary documentation update. > > ## Summary > > After reviewing the changelog entry for **2026.01.21**, I identified: > > ### Already Covered by Existing Suggestions > The payment-related items were already documented by existing suggestions: > - **Payments Settings page** → covered by the "Document payment settings" suggestion > - **Subscription renewal emails** → covered by the "Document payment email templates" suggestion > - **Invoice visibility** → covered by the "Document invoice listing feature" suggestion > > ### New Documentation Created > I created a new suggestion to address the remaining item: **"Updated JWT documentation to include `isRestricted` and `restrictedReason`"** > > The suggestion updates the JWT Tokens documentation with: > - **New claims documentation**: Added `is_restricted` (boolean) and `restricted_reason` (nullable object with `type` field) to the Stack Auth Specific Claims section > - **Updated example payload**: Added the new fields to the example JWT payload > - **Restricted user tokens**: Documented how restricted user tokens differ (`:restricted` audience suffix) > - **JWKS parameter**: Added documentation for the `include_restricted=true` parameter in the Manual JWT Verification section > > These fields were introduced in PR #1069 "Onboarding app & restricted users" to support the new onboarding flow where users who haven't completed requirements (like email verification) are marked as "restricted." </details> --- **Help us improve Promptless** — If this suggestion missed the mark, please [share quick feedback](https://app.gopromptless.ai/change-history/ea7c7471-778d-42ea-9845-fa380f013560?openFeedback=1). *If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)* --------- Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-02-24 10:45:01 -06:00
promptless[bot]	7468007b5d	docs: Add missing lastModified field to sign-up-rules.mdx (#1219) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/suggestions/9355c2e9-3f8e-4b9e-8857-92e937f4b7df) Adds the required `lastModified` field to the sign-up-rules.mdx frontmatter. Per client documentation requirements, all new MDX documents must include a `lastModified` field in the frontmatter with the current date. ### Trigger Events <details> <summary><a href="e9886bc45a...4af15344eb">stack-auth/stack-auth commit (dev): 4af1534 docs: Document Sign-up Rules feature (#1183)</a></summary> <br> **Promptless Research** (1 GitHub PR) - [Reviewed stack-auth/stack-auth#1183](https://github.com/stack-auth/stack-auth/pull/1183) **Agent Response** > I've completed my analysis of this commit and created a suggestion to fix an issue I found. > > ## Summary > > **Trigger:** Commit `4af1534` merged PR #1183 which documented the Sign-up Rules feature. > > **What I found:** The new `sign-up-rules.mdx` file was missing the required `lastModified` field in its frontmatter. Per documentation requirements, all new MDX documents must include this field with the current date. > > **Fix created:** I created a [suggestion](https://app.gopromptless.ai/suggestions/9355c2e9-3f8e-4b9e-8857-92e937f4b7df) that adds the missing `lastModified: "2026-02-24"` field to the sign-up-rules.mdx frontmatter. > > The underlying Sign-up Rules documentation content itself is comprehensive and well-written, covering rule creation, conditions, actions, priority/default settings, common use cases, analytics, and the rule testing feature. </details> --- _Tip: Set up a GitHub Issues trigger in [Projects](https://app.gopromptless.ai/projects) to enable @Promptless mentions in issues 🐙_ Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-02-24 10:43:15 -06:00
promptless[bot]	9832ae69cd	docs: Document SMTP port 2465 support for implicit TLS (#1188) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/change-history/f3f4cc12-c710-4d2d-96cd-e5443c52c8f1) Updates the Email Configuration documentation to mention that port 2465 is now supported alongside port 465 for implicit TLS (SMTPS) connections. Also clarifies the terminology: 587 uses STARTTLS while 465/2465 use implicit TLS from byte 1. ### Trigger Events <details> <summary><a href="02c67ef532...2288c9c65c">stack-auth/stack-auth commit (dev): 2288c9c Port 2465 should have implicit TLS from byte 1</a></summary> <br> **Promptless Research** (1 webpage) - [Read webpage from github.com](02c67ef532...2288c9c65c) **Agent Response** > I've completed my analysis and created a documentation suggestion for this commit. > > ## Summary > > The commit `2288c9c` adds port 2465 as a supported implicit TLS (SMTPS) port alongside the existing port 465. This is a small but meaningful fix for users who use non-standard SMTP ports. > > ## Documentation Change > > I created a suggestion that updates the **Email Configuration** section in the Emails guide: > > **Before:** > > Port: SMTP port (typically 587 for TLS or 465 for SSL) > > **After:** > > Port: SMTP port (typically 587 for STARTTLS, or 465/2465 for implicit TLS) > > This change: > 1. Documents the newly supported port 2465 for implicit TLS connections > 2. Clarifies the terminology (STARTTLS vs implicit TLS) to be more technically precise > > The suggestion is available for review at: https://app.gopromptless.ai/change-history/f3f4cc12-c710-4d2d-96cd-e5443c52c8f1 </details> --- _Tip: Add or adjust Promptless's style guide in [Agent Knowledge Base](https://app.gopromptless.ai/configure/settings) ✍️_ Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-02-24 10:42:41 -06:00
promptless[bot]	9e92fb6f2f	[Docs] Partial refunds for USD transactions (#1132) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/change-history/ec26b3ff-78d8-4ae0-818b-2ad8b29f9f85) Adds documentation for the new partial refund feature in the Payments dashboard. Documents that USD transactions support both full and partial refunds (specifying an amount up to the original charge), while non-USD transactions only support full refunds. Also clarifies refund eligibility requirements (non-test mode purchases with associated prices). ### Trigger Events <details> <summary><a href="https://github.com/stack-auth/stack-auth/pull/1123">stack-auth/stack-auth PR #1123: Partial refunds frontend</a></summary> <br> **Promptless Research** (1 GitHub PR) - [Reviewed stack-auth/stack-auth#1123](https://github.com/stack-auth/stack-auth/pull/1123) **Agent Response** > I've completed the documentation update for this PR. > > ## Summary > > I reviewed PR #1123 which adds partial refund functionality to the payments system, allowing admins to specify custom USD refund amounts instead of being limited to full refunds. > > ### Documentation Update Created > > I updated the **Payments** guide (`docs/content/docs/(guides)/apps/payments.mdx`) to document this new feature: > > - Added a new **"Issuing Refunds"** subsection under the Transactions section > - Documented that USD transactions support both full and partial refunds (specifying an amount up to the original charge) > - Noted that non-USD transactions only support full refunds > - Clarified refund eligibility requirements (non-test mode purchases with associated prices) > > **Suggestion URL**: https://app.gopromptless.ai/change-history/ec26b3ff-78d8-4ae0-818b-2ad8b29f9f85 </details> This PR ties with #1123 --- **Help us improve Promptless** — If this suggestion missed the mark, please [share quick feedback](https://app.gopromptless.ai/change-history/ec26b3ff-78d8-4ae0-818b-2ad8b29f9f85?openFeedback=1). *If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)* Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-02-24 10:39:06 -06:00
promptless[bot]	4af15344eb	docs: Document Sign-up Rules feature (#1183) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/change-history/09aa88eb-2871-4b0b-9014-bf08503ee645) Adds new documentation for the Sign-up Rules feature that allows admins to control who can sign up for their application. Documents how to create rules in the dashboard, the available context variables (email, emailDomain, authMethod, oauthProvider), the available actions (allow, reject, restrict, log), rule priority ordering, default action settings, common use cases like blocking disposable emails or restricting to corporate domains, and how to use the built-in rule tester to simulate sign-up requests before deploying rules. Placed under the Concepts section. ### Trigger Events <details> <summary><a href="13cd1f0f2b...7a35751f8e">stack-auth/stack-auth commit (dev): 7a35751 Sign up rules (#1138)</a></summary> <br> **Promptless Research** (1 GitHub PR) - [Reviewed stack-auth/stack-auth#1138](https://github.com/stack-auth/stack-auth/pull/1138) **Agent Response** > I've completed the documentation for the Sign-up Rules feature introduced in PR #1138. > > ## Summary > > Created a new documentation page for **Sign-up Rules** that covers: > > - **Overview**: How rules let admins control who can sign up using conditions and actions > - **Creating Rules**: Step-by-step instructions for the dashboard UI > - **Available Conditions**: Documented all context variables (`email`, `emailDomain`, `authMethod`, `oauthProvider`) and supported operations (`contains`, `startsWith`, `endsWith`, `matches`, `==`, `!=`) > - **Actions**: Explained all four action types: > - **Allow** - Let users sign up normally > - **Reject** - Block sign-up with optional internal logging message > - **Restrict** - Allow sign-up but mark user for admin review (links to JWT docs for restricted user tokens) > - **Log** - Track patterns without affecting sign-up > - **Priority & Default Action**: How rule ordering works and when to use reject-by-default > - **Common Use Cases**: Practical examples like blocking disposable emails, corporate-only domains, and different rules per auth method > - **Analytics**: Brief mention of the dashboard analytics showing rule triggers > > The new page has been added to the navigation under the "Apps" section, positioned near other authentication-related documentation. </details> <details> <summary><a href="457ff2bdbe...6fcf1a888f">stack-auth/stack-auth commit (dev): 6fcf1a8 Test sign-up rules widget</a></summary> <br> **Promptless Research** (1 webpage) - [Read webpage from github.com](457ff2bdbe...6fcf1a888f) **Agent Response** > I've completed the documentation update for this commit. Here's a summary: > > ## Summary > > I updated the existing [Sign-up Rules documentation suggestion](https://app.gopromptless.ai/change-history/09aa88eb-2871-4b0b-9014-bf08503ee645) to document the new **Test Rules widget** introduced in commit 6fcf1a8. > > ### Changes Made > > Added a new **"Testing rules"** section to the sign-up rules documentation that covers: > > - **How to access the tester**: Navigate to the Sign-up Rules page and click "Open tester" > - **Test inputs**: Email address, authentication method (Password, OTP, OAuth, Passkey), and OAuth provider > - **Understanding results**: > - **Outcome** - Whether the sign-up would be allowed or rejected, and why > - **Triggered rules** - All rules that matched, with their conditions and actions > - **Evaluation trace** - Detailed view of how every rule was evaluated > - **Normalized context** - How the input was parsed (useful for debugging conditions) > > This addition complements the existing sign-up rules documentation and helps users test their rule configurations before deploying them to production. </details> --- _Tip: Planning a big docs refactor? Use [Deep Analysis](https://app.gopromptless.ai/deep-analysis) to get help with the heavy lifting 🔍_ --------- Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-02-24 10:37:20 -06:00
Madison	02c67ef532	fix docs overview date	2026-02-11 10:36:24 -06:00
Madison	2b4e208713	[Docs] Update docs to openrouter usage for ai chat (#1112) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Switched AI provider for improved streaming and model selection. * Updated chat UI: smoother near-bottom scrolling, refined layout, and visual enhancements. * **Documentation** * Removed legacy Stack Auth setup guide from docs. * **Chores** * Updated docs dependencies and environment configuration; added new API key variable and removed an old global key. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-02-11 10:16:43 -06:00
promptless[bot]	9c29e12b19	docs: Document Apple Bundle IDs for native iOS/macOS app sign-in (#1139) ... [Open this suggestion in Promptless to view citations and reasoning process](https://app.gopromptless.ai/change-history/2b709902-b62c-491c-ad6d-966069ad5ea7) Adds documentation for configuring Apple Bundle IDs in the Stack Auth dashboard, which is required for native iOS/macOS apps using Apple Sign In. The new "Native App Configuration" section explains that Bundle IDs are needed in addition to the existing web OAuth setup when using the Swift SDK's native `ASAuthorizationController` flow, and provides step-by-step instructions for adding Bundle IDs in the Apple authentication method modal. ### Trigger Events <details> <summary><a href="2a6b17339a...c8694c7ff5">stack-auth/stack-auth commit (dev): c8694c7 [Fix] [Feat] Update OAuth Sign-In and Get Token Functions to Work (#1130)</a></summary> <br> **Promptless Research** (1 GitHub PR) - [Reviewed stack-auth/stack-auth#1130](https://github.com/stack-auth/stack-auth/pull/1130) **Agent Response** > I've completed my analysis of PR #1130 and created a documentation suggestion. > > ## Summary > > **PR #1130** adds Apple Native Sign In for iOS/macOS apps, which requires users to configure Bundle IDs in the Stack Auth dashboard (in addition to the existing web OAuth setup with Service IDs). > > ### What I found: > - An existing suggestion already documents the Swift SDK and its OAuth flows > - However, the **Apple authentication provider page** didn't mention Bundle IDs configuration for native apps > > ### Documentation created: > > **New suggestion: "Document Apple Bundle IDs for native iOS/macOS app sign-in"** > > I added a new "Native App Configuration (iOS/macOS)" section to the Apple authentication page that: > - Explains that native iOS/macOS apps using the Swift SDK require Bundle ID configuration > - Clarifies that this is in addition to the web OAuth setup (not a replacement) > - Provides step-by-step instructions for adding Bundle IDs in the Stack Auth dashboard > - Notes that Bundle IDs are only required for native apps, not web applications > > This complements the existing Swift SDK documentation suggestion by covering the Apple-specific dashboard configuration that native app developers need to complete. </details> --- **Help us improve Promptless** — If this suggestion missed the mark, please [share quick feedback](https://app.gopromptless.ai/change-history/2b709902-b62c-491c-ad6d-966069ad5ea7?openFeedback=1). *If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)* Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-01-28 15:59:27 -06:00
Madison	9e2cd4d50e	[Docs] - Full cleanup (#1105) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Removed Features** * Dashboard embed functionality has been removed from the platform. * Python template documentation and guides have been removed. * **Documentation** * Documentation structure has been significantly reorganized and simplified. * Extensive template content and component guides have been removed. * Apple OAuth integration guide updated with streamlined secret generation flow. * **Refactor** * Button component styling and variant system updated. * Routing configuration updated with simplified path handling. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-01-27 00:38:51 -06:00
Madison	d0173af691	[Docs][Content] Github install, UI changes, platform selection (#1098) ... ## Summary This PR improves the documentation for GitHub authentication setup and self-hosting. ## Changes ### GitHub OAuth/App Setup Guide - Updated [github.mdx](cci:7://file:///Users/madison/source/stack-auth/docs/content/docs/%28guides%29/concepts/auth-providers/github.mdx:0:0-0:0) with clearer instructions differentiating between **GitHub OAuth App** and **GitHub App** setup - Added better explanations for when to use each option ### Self-Hosting Documentation - Added prominent danger warning about self-hosting responsibilities - Migrated inline shell commands to structured code examples using [PlatformCodeblock](cci:1://file:///Users/madison/source/stack-auth/docs/src/components/mdx/platform-codeblock.tsx:242:0-673:1) component - Created [docs/code-examples/self-host.ts](cci:7://file:///Users/madison/source/stack-auth/docs/code-examples/self-host.ts:0:0-0:0) with all self-hosting commands ### Info Component - Added new `danger` type for critical warnings with red accent styling - Updated component styling with modern left accent bar and gradient backgrounds ### PlatformCodeblock Component - Added `hidePlatformSelector` prop to hide platform dropdown for single-platform code examples - Added Shell platform support for terminal commands (Docker, Git, pnpm) - Filtered Shell platform from user-selectable options in both the codeblock and header selectors ### Platform Config - Added Shell platform with Docker, Git, and pnpm frameworks <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added comprehensive self-hosting and authentication customization example collections for copy-paste use. * New "danger" info style with visual accent for important warnings. * **Documentation** * GitHub integration guide now centers on GitHub App with an alternate OAuth path retained. * Replaced many inline snippets with platform-driven code blocks and improved platform/framework selector behavior (single-platform optimization; option to hide selector). * Pages now surface "Last updated" above descriptions. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2026-01-20 11:49:08 -06:00
yy	8514e42979	[Docs] Add missing languages to StackProvider lang prop type (#1099) ... ## Summary - Added missing language codes to the `lang` prop type in StackProvider documentation - Added: `ja-JP`, `ko-KR`, `zh-CN`, `zh-TW` ## Context The `quetzal-translations.ts` file already contains translations for these languages, but the documentation didn't list them as supported options for the `lang` prop. This fixes a documentation inconsistency where users couldn't discover that Japanese, Korean, and Chinese translations are available. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added support for Japanese, Korean, Simplified Chinese, and Traditional Chinese language options in localization settings. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2026-01-14 12:03:35 -06:00
Aman Ganapathy	4c6d0131d2	[Docs]: Fix typo in server component basics on the getting started guide page (#1085) ... Previously, the documentation mentioned importing `stackServerApp` from `stack/client.ts`. This has been updated to reflect where it is actually imported from. Co-authored-by: Konsti Wohlwend <n2d4xc@gmail.com>	2026-01-14 09:46:20 -08:00
Madison	b6180d5912	[Docs]- Added Payments docs and code examples (#1068) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> Adds payment docs and code examples to docs. <img width="261" height="284" alt="image" src="https://github.com/user-attachments/assets/66e3f12c-48a3-4408-9ada-927f71427945" /> <img width="1042" height="900" alt="image" src="https://github.com/user-attachments/assets/b478b8cf-b925-41c8-a800-a7dcb7bc9986" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added comprehensive Payments app guide covering Stripe integration, subscriptions, and one-time purchases * Included extensive, multi-language code examples for payment workflows (JavaScript/TypeScript and Python) * Added examples for checkout flows, item management, consuming credits, listing products, and granting products * Integrated the Payments examples into the central examples collection and updated docs navigation to include the Payments guide <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2025-12-22 09:23:24 -06:00
Madison	f3d0a68720	[Docs][Content] - Updates Example Pages -> Vite Vanilla JS examples (#1050) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> feat(docs): centralize code examples with dynamic variant tabs This PR introduces a system for managing code examples centrally while supporting file-based variant tabs (like html/script) within a single code block. ## Changes - **Extended variant system**: `PlatformCodeblock` now supports custom variant names beyond just 'server'/'client', enabling tabs for any file grouping (e.g., html/script pairs) - **Vite example migration**: Moved vite-example.mdx code to `code-examples/vite-example.ts` with html/script variants - **LLM copy support**: The "Copy Markdown" button now expands `PlatformCodeblock` components to inline the actual code, so LLMs receive the full code examples instead of component references ## How it works Code examples with variants are now displayed with filename-based tabs: - Define examples with `variant: 'html'` and `variant: 'script'` in `code-examples/` - The tab labels automatically use the `filename` property - When copying markdown for LLMs, all variants are included with their filenames <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Documentation** * Added a Vite JavaScript example guide with grouped auth examples (init, index, password, OTP, OAuth) and wired examples into the getting-started navigation. * Removed the previous multi-page example guide and replaced it with the new Vite-focused page. * Documentation generation now expands platform code blocks to inline concrete examples for clearer rendered docs. * **Refactor** * Improved code-example variant handling to support flexible variant names for better tabbed/code-sample organization. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2025-12-22 08:53:51 -06:00
Lawrence Chen	e0d19e5d08	[Docs][Content] - Fix CLI template filename in documentation (#1053) ... ## Summary - Fixed the download link for the CLI authentication template - the actual file is `stack-auth-cli-template.py` (with hyphens) but the docs referenced `stack_auth_cli_template.py` (with underscores) - Added a note clarifying that users should rename the file to use underscores for Python import compatibility ## Test plan - [ ] Verify the download link works: https://github.com/stack-auth/stack-auth/tree/main/docs/public/stack-auth-cli-template.py <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated CLI authentication documentation with clearer guidance on downloading and configuring the Python CLI template, including improved instructions for proper file naming conventions and import setup. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Madison <madison.w.kennedy@gmail.com>	2025-12-18 15:18:09 -06:00
Madison	dd9938fe57	[Docs][Content] - Rework overview page and slight updates to codeblocks (#1056) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> ## Changes ### overview Page Redesign - Added centered hero section with Stack Auth logo and welcome message - Replaced verbose "Why Stack Auth" section with a clean Quick start guide for next.js - added Components section with compact card links. - Streamlined QuickLinks and Apps sections - Added lastModified frontmatter support ### Frontmatter schema extension - Extended frontmatter schema to support optional lastModified field - Enables pages to display when they were last updated ### Last Modified Display - Added subtle "Last Updated" text at the bottom of pages that have the lastModified frontmatter field ### Copy Button for Code Blocks - Added copy-to-clipboard button to all codeblocks - Button appears on hover, shows checkmark feedback when copied - Applies to all code blocks ### New Code Examples - Added setup/overview examples for the overview page quick start - install - npx command - use-auth - useUser example <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Code blocks gain a copy-to-clipboard button. * Docs pages now show "Last updated" timestamps when available. * **Documentation** * Overview page redesigned into a hero + quick-start, component showcase, and explore sections with clearer links. * Setup examples expanded to include an "install" quick-start and an authentication "use" example. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2025-12-17 15:39:35 -06:00
Madison	c63858b50d	[docs] Various fixes throughout docs site (#1042) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> # New - quick-links component: Better UI that is more aligned with current styling, as well as centered on page for better experience. <img width="812" height="342" alt="image" src="https://github.com/user-attachments/assets/3de105af-eff0-4ddd-92b4-20c4a388fb03" /> # Update - Updates sidebar with slight visualization to separate Overview, and FAQ links. <img width="268" height="471" alt="image" src="https://github.com/user-attachments/assets/7372f557-f4c5-42d8-9dea-8c3b1b0e5514" /> # fixes - Re-add removed mcp-setup.mdx into /content so its available again. - update meta.json to reflect re-added mc-setup.mdx - centered app-icons on overview page <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a comprehensive MCP setup guide covering major IDEs and AI clients. * Introduced QuickLinks navigation component for enhanced docs navigation. * **Documentation** * Refreshed overview with QuickLinks-based layout and preserved link targets. * Added ready-to-copy installation/config snippets and multi-client setup steps. * **Style** * Updated docs sidebar styling and grouping for clearer “Overview”/FAQ separation. * Centered app cards layout and adjusted header nav activation logic. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->	2025-12-04 08:45:54 -06:00
Madison	8fa56f898c	[docs][dashboard][stack-shared] Update docs to new apps (#996) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <img width="216" height="245" alt="image" src="https://github.com/user-attachments/assets/f59f754f-b9d7-4e82-a552-8e407878eb01" /> <img width="940" height="564" alt="image" src="https://github.com/user-attachments/assets/3218914e-5128-4cff-a183-29637adfb9f2" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * New "Apps" section with dedicated pages for API Keys, Emails, OAuth, Permissions (RBAC), Orgs & Teams, Auth Providers, and Webhooks; API Keys content moved into this section. * New API Keys guide and updated overview content including an Apps grid and app tiles. * Added redirects from old concept pages to new Apps pages. * **Style** * Sidebar now shows icons for docs links; improved hover animations and tile styling across docs. * **New Features** * App tile/card components added for displaying apps in docs. <!-- end of auto-generated comment: release notes by coderabbit.ai --> <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Introduces a new “Apps” docs section (API Keys, Emails, OAuth, RBAC, Orgs & Teams, Webhooks), adds reusable app UI components, updates navigation, and removes the old API Keys concept doc. > > - **Docs**: > - **Apps section**: Add `docs/content/docs/(guides)/apps/*` (API Keys, Emails, OAuth, RBAC Permissions, Orgs & Teams, Webhooks) with icons and examples; remove `concepts/api-keys.mdx` and update related links (e.g., JWT). > - **Overview & Nav**: Insert AppGrid on `overview`, add “Apps” pages to `meta.json`, add “Welcome” nav item, and refine “Guides” active-state logic. > - **Code examples**: Wire `docs/code-examples/index.ts` to load `apps/api-keys` examples. > - **UI/Components**: > - Add `AppCard`/`AppGrid` in `docs/src/components/mdx/app-card.tsx` and register in `mdx-components`. > - Tweak homepage hover card styles (`iconHover.tsx`) and sidebar links to support icons. > - **Shared**: > - Add `packages/stack-shared/src/apps/apps-ui.tsx` with `AppIcon` and sizing constants; note UI export guidance in `stack-shared` `index.ts`. > - **Styling/Infra**: > - Add Tailwind `@source` in global CSS; minor layout/link icon plumbing. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 2487b877aa. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Konsti Wohlwend <n2d4xc@gmail.com>	2025-11-12 15:45:30 -06:00
Armaan Jain	580b0b8f7c	Launch checklist redesign (#1009) ... https://www.loom.com/share/952ec76dff514ba99be9d90e0e9625f8 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Auto-expand next checklist section and animated progress; per-task expand/collapse controls. * OAuth provider guides now in tabbed view with inline callback URLs. * **UI/UX Improvements** * Status badges restyled into card visuals with improved dark-mode icon coloring. * Redesigned checklist header, compact progress bar, updated production card and confetti celebration. * New decorative rainbow-beam animation. * **Documentation** * Updated Convex integration template reference. <!-- end of auto-generated comment: release notes by coderabbit.ai --> <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Redesigns the Launch Checklist with expandable task cards, auto-focus on next task, animated progress, OAuth/email help panels, confetti on enabling production mode, and adds rainbow-beam CSS; updates Convex guide link. > > - **Frontend (dashboard)** > - **Launch Checklist UI** (`apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/launch-checklist/page-client.tsx`): > - New expandable `TaskCard` sections with keyboard/ARIA toggles and per-task completion badge. > - Auto-expands the section containing the next task; animated progress bar in header. > - CTA reworked with "Up next" indicator and rainbow-beam button effect. > - OAuth provider help moved to collapsible tabbed guides with inline callback URLs. > - Email setup help as a collapsible step list; production mode section refined with switch and updated footer. > - Confetti animation when `project.isProductionMode` toggles to true. > - Improved dark-mode and status styling for icons/cards. > - **Styles** > - `apps/dashboard/src/app/globals.css`: Adds rainbow-beam CSS variables and `@keyframes rainbow-beam` animation. > - **Docs** > - `docs/content/docs/(guides)/others/convex.mdx`: Updates template link to a production-ready Stack-Auth + Convex + Shadcn repo. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit bfe629b2c2. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Konsti Wohlwend <n2d4xc@gmail.com>	2025-11-11 08:51:33 +05:30
Madison	8c805a8b8f	[Docs][Util][Content] - refactor docs to single source (#919) ... <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> Removes Platform selection, moves docs to single /content folder and no longer gens docs. Only API docs are generated here. <!-- RECURSEML_SUMMARY:START --> ## High-level PR Summary This PR makes significant changes to the documentation structure by removing platform-specific content organization and consolidating docs into a single `/content` folder. The primary goal is to simplify the documentation architecture by eliminating the platform-specific routing (Next.js, React, JavaScript, Python) and instead organizing content by topic (guides, SDK, components) regardless of platform. The PR removes platform selection functionality, platform-specific navigation, and the automatic generation of platform-specific documentation pages. It introduces a new docs tree filtering system that organizes content by section rather than by platform. These changes should make the documentation more maintainable and easier to navigate while focusing on the content itself rather than platform-specific variations. ⏱️ Estimated Review Time: 30-90 minutes <details> <summary>💡 Review Order Suggestion</summary> | Order | File Path | |-------|-----------| | 1 | `docs/package.json` | | 2 | `docs/src/lib/docs-tree.ts` | | 3 | `docs/src/lib/navigation-utils.ts` | | 4 | `docs/src/components/homepage/iconHover.tsx` | | 5 | `docs/src/components/sdk/overview.tsx` | | 6 | `docs/src/components/layouts/shared/section-utils.ts` | | 7 | `docs/src/components/layout/custom-search-dialog.tsx` | | 8 | `docs/src/app/api/search/route.ts` | | 9 | `docs/src/app/docs/[[...slug]]/page.tsx` | | 10 | `docs/src/components/layouts/docs-header-wrapper.tsx` | | 11 | `docs/src/components/layouts/docs-layout-router.tsx` | | 12 | `docs/src/components/layouts/docs.tsx` | | 13 | `package.json` | </details> [](https://discord.gg/n3SsVDAW6U) <!-- RECURSEML_SUMMARY:END --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added many new guides (auth providers, OAuth, JWT, API keys, emails, webhooks, orgs/teams, permissions, onboarding, customization), expanded SDK & component reference pages, examples, and navigation metadata. * Switched docs to a simpler section-based, platform-agnostic structure and improved getting-started and production checklists. * **Developer Experience** * Enhanced docs UX: improved code-example UI with platform/framework selectors, theme-aware highlighted code blocks, image zoom, and a centralized code-sample registry. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Konstantin Wohlwend <n2d4xc@gmail.com>	2025-10-20 12:42:46 -05:00
Konstantin Wohlwend	53ff6f1c4e	Update setup instructions	2025-10-11 14:53:17 -07:00
Madison	5bf522ab57	[Docs][site] - AI Chat now looks at MCP server (#860)	2025-09-20 12:05:00 -07:00