powersync-ja · joshuabrink · Mar 4, 2026 · Mar 4, 2026 · Mar 4, 2026 · Mar 4, 2026
diff --git a/client-sdks/advanced/raw-tables.mdx b/client-sdks/advanced/raw-tables.mdx
diff --git a/client-sdks/reference/capacitor.mdx b/client-sdks/reference/capacitor.mdx
@@ -1,7 +1,7 @@
 ---
 title: "Capacitor SDK (alpha)"
 description: "Full SDK guide for using PowerSync in Capacitor clients"
-sidebarTitle: "Capacitor"
+sidebarTitle: "SDK Reference"
 ---
 
 import SdkFeatures from '/snippets/sdk-features.mdx';

diff --git a/client-sdks/reference/javascript-web.mdx b/client-sdks/reference/javascript-web.mdx
@@ -1,7 +1,7 @@
 ---
 title: "JavaScript Web SDK"
 description: "Full SDK guide for using PowerSync in JavaScript Web clients"
-sidebarTitle: "JavaScript Web"
+sidebarTitle: "SDK Reference"
 ---
 
 import SdkFeatures from '/snippets/sdk-features.mdx';

diff --git a/client-sdks/reference/node.mdx b/client-sdks/reference/node.mdx
@@ -1,7 +1,7 @@
 ---
 title: "Node.js client SDK (Beta)"
 description: "SDK reference for using PowerSync in Node.js clients."
-sidebarTitle: "Node.js"
+sidebarTitle: "SDK Reference"
 ---
 
 import SdkFeatures from '/snippets/sdk-features.mdx';
@@ -12,7 +12,7 @@
 import LocalOnly from '/snippets/local-only-escape.mdx';

 <Note>
  This page describes the PowerSync _client_ SDK for Node.js.
  If you're interested in using PowerSync for your Node.js backend, no special package is required.
  Instead, follow our guides on [app backend setup](/configuration/app-backend/setup).
 </Note>
@@ -299,9 +299,9 @@
 ```

 <Note>
 If you're using a custom compilation toolchain, for instance because you're compiling from TypeScript
 or are applying a bundler to your project, loading workers may require additional configuration on that
 toolchain.
 </Note>

 ### `node:sqlite`

diff --git a/configuration/auth/development-tokens.mdx b/configuration/auth/development-tokens.mdx
@@ -30,8 +30,7 @@
   </Tab>
 
   <Tab title="Self-Hosted">
-    For self-hosted setups, you can generate development tokens using the [powersync-service test-client](https://github.com/powersync-ja/powersync-service/tree/main/test-client):
-
+    Follow the steps below. Steps 1 and 2 configure signing keys and your PowerSync Service config; in Step 3 you can use the PowerSync CLI (recommended) or the [test-client](https://github.com/powersync-ja/powersync-service/tree/main/test-client) to generate the token.
 
     <DevTokenSelfHostedSteps />
   </Tab>
@@ -47,7 +46,7 @@

 1. Open the [Sync Diagnostics Client](https://diagnostics-app.powersync.com)
 2. Enter the generated development token at **PowerSync Token**.
 3. Enter your PowerSync Service endpoint URL at **PowerSync Endpoint** unless already prepopulated.
 4. Click **Proceed**.
 4. Wait for the syncing to complete and inspect the synced data in SQLite.


diff --git a/configuration/source-db/setup.mdx b/configuration/source-db/setup.mdx
@@ -436,7 +436,7 @@
 | Database         | Edition                                     | Version | Min Service Tier                                                                      |
 | ---------------- | ------------------------------------------- | ------- | ------------------------------------------------------------------------------------- |
 | SQL Server 2022+ | Standard, Enterprise, Developer, Evaluation | 16.0+   | N/A                                                                                   |
 | Azure SQL\*      | Database, Managed instance                  | N/A     | Any service tier on vCore purchasing model. S3 tier and up on DTU purchasing model. See: [Azure SQL Database compute requirements](https://learn.microsoft.com/en-us/azure/azure-sql/database/change-data-capture-overview?view=azuresql#azure-sql-database-compute-requirements) |

 \* Azure SQL Database is always running on the latest version of the SQL Server DB Engine

@@ -469,7 +469,7 @@

 - Read/Write permissions on the `_powersync_checkpoints` table
 - Read permissions on the replicated tables
 - `cdc_reader` role (grants access to CDC changetables and functions)
 - `SELECT` permission on the CDC schema (grants access to CDC metadata tables)
 - `VIEW DATABASE PERFORMANCE STATE` (SQL Server and Azure SQL)
 - `VIEW SERVER PERFORMANCE STATE` (SQL Server only)
@@ -615,7 +615,7 @@
 
 2. **Polling Interval**: The frequency at which PowerSync polls the CDC change tables for changes. The default value is once every 1000ms. This can be changed by setting the `pollingIntervalMs` parameter in the PowerSync configuration.
 
-<Warning>Configuration parameters for SQL Server like `pollingIntervalMs` and `pollingBatchSize` (see below) can currently only be [set when self-hosting](/intro/setup-guide#self-hosted-2) PowerSync. We are working on exposing these settings for SQL Server source database connections in the PowerSync Dashboard for PowerSync Cloud instances.</Warning>
+<Warning>Configuration parameters for SQL Server like `pollingIntervalMs` and `pollingBatchSize` (see below) can currently only be set when self-hosting PowerSync (e.g. via your config file or the [PowerSync CLI](/tools/cli)). We are working on exposing these settings in the PowerSync Dashboard for PowerSync Cloud instances.</Warning>
 
 ### Memory Management
 

diff --git a/intro/powersync-overview.mdx b/intro/powersync-overview.mdx
@@ -18,7 +18,10 @@
   <Card title="Understand PowerSync" icon="lightbulb" href="/intro/powersync-philosophy" horizontal>
     Learn about PowerSync's philosophy, key concepts and architecture.
   </Card>
-  <Card title="MongoDB Atlas Device Sync Migration" icon="leaf" href="/migration-guides/atlas-device-sync" horizontal>
+  <Card title="Agent Skills" icon="sparkles" href="/tools/ai-tools#powersync-agent-skills" horizontal>
+    Use the official PowerSync Agent Skills to get started with PowerSync quickly using AI-powered coding tools.
+  </Card>
+   <Card title="MongoDB Atlas Device Sync Migration" icon="leaf" href="/migration-guides/atlas-device-sync" horizontal>
     Step-by-step guide to migrate from Atlas Device Sync to PowerSync.
   </Card>
 </CardGroup>
@@ -44,7 +47,7 @@
 <ClientSdks />

 <Note>
  Looking for an SDK that's not listed above? Upvote it or submit it on [our roadmap](https://roadmap.powersync.com/).
 </Note>



diff --git a/intro/self-hosting.mdx b/intro/self-hosting.mdx
@@ -9,7 +9,6 @@ The [PowerSync Service](https://github.com/powersync-ja/powersync-service) can b
 
 <Note>
   * Note that the [PowerSync Dashboard](https://dashboard.powersync.com/) is currently not available when self-hosting PowerSync.
-  * The PowerSync Open Edition is currently considered a beta release as it still requires more detailed documentation and guides. From a stability perspective, the Open Edition is production-ready. It uses the same codebase as our Cloud version. See [Feature Status](/resources/feature-status) for how we define beta releases.
   * Please reach out on our [Discord](https://discord.gg/powersync) if you have any questions not yet covered in these docs.
 </Note>
 
@@ -27,9 +26,9 @@ The quickest way to get a feel for the system is to run our example project on y
 
 <Card title="GitHub - powersync-ja/self-host-demo" icon="github" href="https://github.com/powersync-ja/self-host-demo" horizontal />
 
-## Local Development With Docker Compose
+## Local Development
 
-If you plan to self-host for development purposes only, see [Local Development](/tools/local-development) for how to easily do this using Docker Compose.
+To run PowerSync locally, see [Local Development](/tools/local-development). The easiest path is the [PowerSync CLI](/tools/cli), which sets up a Docker Compose stack for you.
 
 
 ## Full Installation