@mastra/mcp-docs-server 1.1.35-alpha.21 → 1.1.35-alpha.26

package/.docs/reference/browser/stagehand-browser.md

@@ -61,18 +61,29 @@ Use stagehand_extract to get data from pages.`,
 
 **screencast** (`ScreencastOptions`): Configuration for streaming browser frames to Studio.
 
+**excludeTools** (`StagehandToolName[]`): Tool names to exclude from the browser toolset. Use this to disable specific tools for models that do not support certain capabilities, such as vision.
+
 ## Tools
 
-`StagehandBrowser` provides 6 AI-powered tools for browser automation:
+`StagehandBrowser` provides 7 AI-powered tools for browser automation:
+
+| Tool                   | Description                                                                           |
+| ---------------------- | ------------------------------------------------------------------------------------- |
+| `stagehand_act`        | Perform actions using natural language instructions                                   |
+| `stagehand_extract`    | Extract structured data from pages                                                    |
+| `stagehand_observe`    | Discover actionable elements on a page                                                |
+| `stagehand_navigate`   | Navigate to a URL                                                                     |
+| `stagehand_tabs`       | Manage browser tabs                                                                   |
+| `stagehand_screenshot` | Capture a screenshot as PNG (viewport by default; set `fullPage: true` for full page) |
+| `stagehand_close`      | Close the browser                                                                     |
 
-| Tool                 | Description                                         |
-| -------------------- | --------------------------------------------------- |
-| `stagehand_act`      | Perform actions using natural language instructions |
-| `stagehand_extract`  | Extract structured data from pages                  |
-| `stagehand_observe`  | Discover actionable elements on a page              |
-| `stagehand_navigate` | Navigate to a URL                                   |
-| `stagehand_tabs`     | Manage browser tabs                                 |
-| `stagehand_close`    | Close the browser                                   |
+To exclude specific tools, pass `excludeTools` in the constructor:
+
+```typescript
+const browser = new StagehandBrowser({
+  excludeTools: ['stagehand_screenshot'],
+})
+```
 
 ## Tool reference
 
@@ -224,6 +235,21 @@ Manage browser tabs.
 { "action": "close", "index": 1 }
 ```
 
+### `stagehand_screenshot`
+
+Capture a screenshot of the current page as PNG (viewport by default; set `fullPage: true` for full-page capture). Returns image content that vision-capable models can interpret directly. Use `stagehand_observe` or `stagehand_extract` when you only need text or structured data.
+
+```text
+// Viewport only (default)
+
+// Full scrollable page
+{ "fullPage": true }
+```
+
+| Parameter  | Type      | Description                                                                              |
+| ---------- | --------- | ---------------------------------------------------------------------------------------- |
+| `fullPage` | `boolean` | Capture the full scrollable page instead of just the viewport (optional, default: false) |
+
 ### `stagehand_close`
 
 Close the browser and clean up resources.

package/.docs/reference/client-js/agents.md

@@ -151,6 +151,95 @@ for await (const part of uiMessageStream) {
 }
 ```
 
+### `sendSignal()`
+
+Send a signal to an active agent run or memory thread. Use this with `subscribeToThread()` so the client can render the stream that wakes from, or receives, the signal.
+
+```typescript
+const agent = mastraClient.getAgent('support-agent')
+
+const result = await agent.sendSignal({
+  signal: {
+    type: 'user-message',
+    contents: 'Also consider the customer note I just added.',
+  },
+  resourceId: 'user-123',
+  threadId: 'thread-abc',
+})
+
+console.log(result.runId)
+```
+
+Use `ifActive.behavior` and `ifIdle.behavior` to control whether Mastra delivers, persists, discards, or wakes from a signal:
+
+```typescript
+await agent.sendSignal({
+  signal: { type: 'user-message', contents: 'Store this for later.' },
+  resourceId: 'user-123',
+  threadId: 'thread-abc',
+  ifIdle: {
+    behavior: 'persist',
+  },
+})
+```
+
+Pass `ifIdle.streamOptions` when the idle wake-up stream needs options such as model settings, tools, or runtime context:
+
+```typescript
+await agent.sendSignal({
+  signal: { type: 'user-message', contents: 'Start from this signal.' },
+  resourceId: 'user-123',
+  threadId: 'thread-abc',
+  ifIdle: {
+    behavior: 'wake',
+    streamOptions: {
+      maxSteps: 3,
+    },
+  },
+})
+```
+
+Returns `{ accepted: true, runId: string }`.
+
+**signal** (`{ type: 'user-message'; contents: MessageListInput } | { type: string; contents: string }`): \`user-message\` signals are treated as user input. Other signal types are converted to contextual XML before the next model call.
+
+**runId** (`string`): Run ID to target directly.
+
+**resourceId** (`string`): Resource ID for the memory thread. Use with \`threadId\` for thread-targeted signals.
+
+**threadId** (`string`): Thread ID to target. Use with \`resourceId\` for thread-targeted signals.
+
+**ifActive.behavior** (`'deliver' | 'persist' | 'discard'`): Controls what happens when the target thread is active. Defaults to \`deliver\`.
+
+**ifIdle.behavior** (`'wake' | 'persist' | 'discard'`): Controls what happens when the target thread is idle. Defaults to \`wake\`.
+
+**ifIdle.streamOptions** (`Omit<AgentExecutionOptions, 'messages'>`): Options for the stream that starts when \`ifIdle.behavior\` is \`wake\`.
+
+### `subscribeToThread()`
+
+Subscribe to raw stream chunks for a memory thread. Use this to render output from a thread that may be started or continued by `sendSignal()`.
+
+```typescript
+const agent = mastraClient.getAgent('support-agent')
+
+const subscription = await agent.subscribeToThread({
+  resourceId: 'user-123',
+  threadId: 'thread-abc',
+})
+
+await subscription.processDataStream({
+  onChunk: async chunk => {
+    console.log(chunk)
+  },
+})
+```
+
+`subscribeToThread()` returns the underlying `Response` plus a `processDataStream()` helper. The helper reads the subscription stream until the connection closes or the request is aborted.
+
+**resourceId** (`string`): Resource ID for the memory thread.
+
+**threadId** (`string`): Thread ID to subscribe to.
+
 ### `streamUntilIdle()`
 
 Stream a response and keep the stream open until every [background task](https://mastra.ai/docs/agents/background-tasks) dispatched during the run completes. The server re-enters the agentic loop on each task completion so the LLM can react to results in the same call. Requires background tasks to be [enabled on the Mastra instance](https://mastra.ai/reference/configuration) and a memory thread; otherwise the call falls through to a plain `stream()`.

package/.docs/reference/index.md

@@ -199,6 +199,7 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [registerApiRoute()](https://mastra.ai/reference/server/register-api-route)
 - [Server Routes](https://mastra.ai/reference/server/routes)
 - [Overview](https://mastra.ai/reference/storage/overview)
+- [Aurora DSQL Storage](https://mastra.ai/reference/storage/dsql)
 - [ClickHouse Storage](https://mastra.ai/reference/storage/clickhouse)
 - [Cloudflare D1 Storage](https://mastra.ai/reference/storage/cloudflare-d1)
 - [Cloudflare KV Storage](https://mastra.ai/reference/storage/cloudflare)
@@ -223,6 +224,7 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [.stream()](https://mastra.ai/reference/streaming/workflows/stream)
 - [.timeTravelStream()](https://mastra.ai/reference/streaming/workflows/timeTravelStream)
 - [Overview](https://mastra.ai/reference/templates/overview)
+- [Bright Data Tools](https://mastra.ai/reference/tools/brightdata)
 - [createDocumentChunkerTool()](https://mastra.ai/reference/tools/document-chunker-tool)
 - [createGraphRAGTool()](https://mastra.ai/reference/tools/graph-rag-tool)
 - [createTool()](https://mastra.ai/reference/tools/create-tool)
@@ -257,6 +259,7 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [Events](https://mastra.ai/reference/voice/voice.events)
 - [Google](https://mastra.ai/reference/voice/google)
 - [Google Gemini Live](https://mastra.ai/reference/voice/google-gemini-live)
+- [Inworld](https://mastra.ai/reference/voice/inworld)
 - [Mastra Voice](https://mastra.ai/reference/voice/mastra-voice)
 - [Murf](https://mastra.ai/reference/voice/murf)
 - [OpenAI](https://mastra.ai/reference/voice/openai)

package/.docs/reference/processors/prefill-error-handler.md

@@ -2,7 +2,7 @@
 
 The `PrefillErrorHandler` is an **error processor** that handles assistant-response prefill errors. This error occurs when a conversation ends with an assistant message and the model rejects the request because it interprets it as prefilling the assistant response.
 
-When the error is detected, the processor appends a hidden `<system-reminder>continue</system-reminder>` user message to the conversation and signals a retry. The reminder is persisted with `metadata.systemReminder = { type: 'anthropic-prefill-processor-retry' }`, which keeps it available for retry reconstruction and raw history while standard UI-facing message conversions hide it.
+When the error is detected, the processor sends a hidden `system-reminder` signal with `continue` as its contents and signals a retry. The reminder is persisted as signal metadata, which keeps it available for retry reconstruction and raw history while standard UI-facing message conversions hide it.
 
 Add this processor to `errorProcessors` when you want Mastra to recover from assistant prefill rejections (for example Anthropic's "assistant message prefill" and Qwen/llama.cpp's "assistant response prefill is incompatible with `enable_thinking`" errors).
 
@@ -10,7 +10,7 @@ Add this processor to `errorProcessors` when you want Mastra to recover from ass
 
 1. The LLM API call fails with a known assistant-prefill rejection message
 2. `PrefillErrorHandler` checks that this is the first retry attempt
-3. It appends a hidden `<system-reminder>continue</system-reminder>` user message to the `messageList`
+3. It sends a hidden `system-reminder` signal with `continue` as its contents
 4. It returns `{ retry: true }` to signal the LLM call should be retried with the modified messages
 
 The processor now reacts to the API rejection itself instead of re-checking whether the conversation currently ends with an assistant message. This makes it resilient to cases where the provider rejects the request for prefill semantics even if the trailing message shape has already been transformed upstream.
@@ -62,7 +62,7 @@ The `PrefillErrorHandler` takes no constructor parameters.
 
 **name** (`'Prefill Error Handler'`): Processor display name.
 
-**processAPIError** (`(args: ProcessAPIErrorArgs) => ProcessAPIErrorResult | void`): Handles known assistant-prefill errors by appending a hidden system reminder continue message and signaling retry. Only triggers on the first retry attempt.
+**processAPIError** (`(args: ProcessAPIErrorArgs) => ProcessAPIErrorResult | void`): Handles known assistant-prefill errors by sending a hidden system reminder signal and signaling retry. Only triggers on the first retry attempt.
 
 ## Related
 

package/.docs/reference/storage/dsql.md

@@ -0,0 +1,428 @@
+# Aurora DSQL Storage
+
+The Aurora DSQL storage implementation provides storage using Amazon Aurora DSQL with IAM authentication.
+
+Aurora DSQL does not support PostgreSQL extensions (`CREATE EXTENSION`), including `pgvector`. For vector storage, use a separate vector store such as `@mastra/s3vectors`.
+
+## Installation
+
+```bash
+npm install @mastra/dsql@beta
+```
+
+## Prerequisites
+
+- Amazon Aurora DSQL cluster
+- AWS credentials with access to the DSQL cluster (IAM authentication)
+
+## Usage
+
+```typescript
+import { DSQLStore } from '@mastra/dsql'
+
+const storage = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+  // region is auto-detected from host, or specify explicitly:
+  // region: 'us-east-1',
+  // user: 'admin', // default
+  // database: 'postgres', // default
+})
+
+// Initialize the store (creates tables if needed)
+await storage.init()
+```
+
+## Parameters
+
+**id** (`string`): Unique identifier for this store instance
+
+**host** (`string`): DSQL cluster endpoint (e.g., abc123.dsql.us-east-1.on.aws)
+
+**pool** (`pg.Pool`): Pre-configured pg.Pool instance. Use this for direct control over the connection pool. Cannot be used with host configuration.
+
+**user** (`string`): Database user. Aurora DSQL's admin role is 'admin'.
+
+**database** (`string`): Database name. Aurora DSQL exposes a single database named 'postgres' per cluster.
+
+**region** (`string`): AWS region. Extracted from host if not provided.
+
+**schemaName** (`string`): PostgreSQL schema name where Mastra tables and indexes are created.
+
+**customCredentialsProvider** (`AwsCredentialIdentityProvider`): Custom AWS credentials provider for IAM authentication.
+
+**max** (`number`): Maximum connections in the pool.
+
+**min** (`number`): Minimum connections in the pool.
+
+**idleTimeoutMillis** (`number`): Close idle connections after this many milliseconds.
+
+**maxLifetimeSeconds** (`number`): Maximum connection lifetime in seconds. Must be less than 3600 due to Aurora DSQL's 60-minute connection limit.
+
+**connectionTimeoutMillis** (`number`): Connection acquisition timeout in milliseconds.
+
+**allowExitOnIdle** (`boolean`): Allow the process to exit when all connections are idle.
+
+## Constructor Examples
+
+You can instantiate `DSQLStore` in the following ways:
+
+```typescript
+import { DSQLStore } from '@mastra/dsql'
+
+// Basic configuration (region auto-detected from host)
+const store1 = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+})
+
+// With explicit region and schema
+const store2 = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+  region: 'us-east-1',
+  schemaName: 'my_app',
+})
+
+// With custom credentials provider
+import { fromNodeProviderChain } from '@aws-sdk/credential-providers'
+
+const store3 = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+  customCredentialsProvider: fromNodeProviderChain(),
+})
+
+// With connection pool settings
+const store4 = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+  max: 20,
+  min: 2,
+  idleTimeoutMillis: 300000,
+  maxLifetimeSeconds: 3000,
+  connectionTimeoutMillis: 10000,
+})
+
+// Using a pre-configured pg.Pool
+import { Pool } from 'pg'
+import { AuroraDSQLClient } from '@aws/aurora-dsql-node-postgres-connector'
+
+const pool = new Pool({
+  host: 'abc123.dsql.us-east-1.on.aws',
+  Client: AuroraDSQLClient,
+  region: 'us-east-1',
+})
+
+const store5 = new DSQLStore({
+  id: 'my-dsql-store',
+  pool,
+})
+```
+
+## Additional Notes
+
+### Schema Management
+
+The storage implementation handles schema creation and updates automatically. It creates the following tables:
+
+- `mastra_workflow_snapshot`: Stores workflow state and execution data
+- `mastra_threads`: Stores conversation threads
+- `mastra_messages`: Stores individual messages
+- `mastra_ai_spans`: Stores span data for observability
+- `mastra_scorers`: Stores scoring and evaluation data
+- `mastra_resources`: Stores resource working memory data
+- `mastra_agents`: Stores agent data
+
+### Initialization
+
+When you pass storage to the Mastra class, `init()` is called automatically before any storage operation:
+
+```typescript
+import { Mastra } from '@mastra/core'
+import { DSQLStore } from '@mastra/dsql'
+
+const storage = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+})
+
+const mastra = new Mastra({
+  storage, // init() is called automatically
+})
+```
+
+If you're using storage directly without Mastra, you must call `init()` explicitly to create the tables:
+
+```typescript
+import { DSQLStore } from '@mastra/dsql'
+
+const storage = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+})
+
+// Required when using storage directly
+await storage.init()
+
+// Access domain-specific stores via getStore()
+const memoryStore = await storage.getStore('memory')
+const thread = await memoryStore?.getThreadById({ threadId: '...' })
+```
+
+> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+
+### Direct Database and Pool Access
+
+`DSQLStore` exposes both the underlying database client and the pg.Pool instance as public fields:
+
+```typescript
+storage.db // Database client for executing queries
+storage.pool // Underlying pg.Pool instance
+```
+
+This enables direct queries and custom transaction management. When using these fields:
+
+- You are responsible for proper connection and transaction handling.
+- Closing the store (`storage.close()`) will destroy the connection pool if it was created by the store.
+- Direct access bypasses any additional logic or validation provided by DSQLStore methods.
+
+This approach is intended for advanced scenarios where low-level access is required.
+
+### Aurora DSQL Specifics
+
+#### IAM-only authentication
+
+Connections are authenticated with IAM. There are no database passwords. `@mastra/dsql` uses `@aws/aurora-dsql-node-postgres-connector` to generate short-lived auth tokens. You can provide a custom credentials provider via `customCredentialsProvider`.
+
+#### Single database, schema-based isolation
+
+Each cluster exposes a single database named `postgres`. Logical separation is done via schemas. The `schemaName` option controls where Mastra tables are created.
+
+#### No PostgreSQL extensions
+
+`CREATE EXTENSION` is not supported. This includes `pgvector`, `PostGIS`, and others. For vector storage, use a separate store such as `@mastra/s3vectors` alongside `DSQLStore`.
+
+#### JSON stored as text
+
+JSON/JSONB are available as query types but not as column types. `@mastra/dsql` stores structured fields (metadata, content, etc.) in `TEXT` columns and casts to JSON at query time.
+
+#### Schema and DDL constraints
+
+Some PostgreSQL features are not available:
+
+- Foreign key constraints
+- `TRUNCATE`
+- Synchronous `CREATE INDEX`
+
+Indexes are created asynchronously using `CREATE INDEX ASYNC`. The store's `init()` and index helper APIs respect these constraints.
+
+#### Transactions and optimistic concurrency
+
+Aurora DSQL uses optimistic concurrency control (OCC) and may return retriable OCC errors under contention. There are limits on transaction duration and size. Large bulk operations should be split into smaller batches at the application level.
+
+#### Connection lifetime
+
+Individual connections are limited to about 60 minutes. The default `maxLifetimeSeconds: 3300` ensures connections are recycled before hitting this limit.
+
+## Usage Example
+
+### Adding memory to an agent
+
+To add Aurora DSQL memory to an agent use the `Memory` class and create a new `storage` key using `DSQLStore`. The `host` should point to your Aurora DSQL cluster endpoint.
+
+```typescript
+import { Memory } from '@mastra/memory'
+import { Agent } from '@mastra/core/agent'
+import { DSQLStore } from '@mastra/dsql'
+
+export const dsqlAgent = new Agent({
+  id: 'dsql-agent',
+  name: 'DSQL Agent',
+  instructions:
+    'You are an AI agent with the ability to automatically recall memories from previous interactions.',
+  model: 'openai/gpt-5.1',
+  memory: new Memory({
+    storage: new DSQLStore({
+      id: 'dsql-agent-storage',
+      host: process.env.DSQL_HOST!,
+    }),
+    options: {
+      generateTitle: true, // Explicitly enable automatic title generation
+    },
+  }),
+})
+```
+
+### Using the agent
+
+Use `memoryOptions` to scope recall for this request. Set `lastMessages: 5` to limit recency-based recall, and use `semanticRecall` to fetch the `topK: 3` most relevant messages, including `messageRange: 2` neighboring messages for context around each match.
+
+```typescript
+import 'dotenv/config'
+
+import { mastra } from './mastra'
+
+const threadId = '123'
+const resourceId = 'user-456'
+
+const agent = mastra.getAgent('dsql-agent')
+
+const message = await agent.stream('My name is Mastra', {
+  memory: {
+    thread: threadId,
+    resource: resourceId,
+  },
+})
+
+await message.textStream.pipeTo(new WritableStream())
+
+const stream = await agent.stream("What's my name?", {
+  memory: {
+    thread: threadId,
+    resource: resourceId,
+  },
+  memoryOptions: {
+    lastMessages: 5,
+    semanticRecall: {
+      topK: 3,
+      messageRange: 2,
+    },
+  },
+})
+
+for await (const chunk of stream.textStream) {
+  process.stdout.write(chunk)
+}
+```
+
+## Index Management
+
+Aurora DSQL storage provides index management capabilities to optimize query performance.
+
+### Automatic Performance Indexes
+
+Aurora DSQL storage automatically creates composite indexes during initialization for common query patterns:
+
+- `mastra_threads_resourceid_createdat_idx`: (resourceId, createdAt)
+- `mastra_messages_thread_id_createdat_idx`: (thread\_id, createdAt)
+- `mastra_ai_spans_traceid_startedat_idx`: (traceId, startedAt)
+- `mastra_ai_spans_parentspanid_startedat_idx`: (parentSpanId, startedAt)
+- `mastra_ai_spans_name_idx`: (name)
+- `mastra_ai_spans_spantype_startedat_idx`: (spanType, startedAt)
+- `mastra_scores_trace_id_span_id_created_at_idx`: (traceId, spanId, createdAt)
+
+Aurora DSQL creates these indexes asynchronously using `CREATE INDEX ASYNC`. Because index creation is asynchronous, new indexes may not be immediately available after `init()`. The store will continue to function without them, but queries may be slower until index creation completes.
+
+### Creating Custom Indexes
+
+Create additional indexes to optimize specific query patterns:
+
+```typescript
+await storage.createIndex({
+  name: 'idx_threads_resource',
+  table: 'mastra_threads',
+  columns: ['resourceId'],
+})
+
+await storage.createIndex({
+  name: 'idx_messages_composite',
+  table: 'mastra_messages',
+  columns: ['thread_id', 'createdAt'],
+})
+```
+
+Aurora DSQL does not allow `ASC`/`DESC` in `CREATE INDEX ASYNC`. If you include them, they will be automatically stripped.
+
+### Index Options
+
+**name** (`string`): Unique name for the index
+
+**table** (`string`): Table name (e.g., 'mastra\_threads')
+
+**columns** (`string[]`): Array of column names. ASC/DESC modifiers are automatically stripped for Aurora DSQL compatibility.
+
+**unique** (`boolean`): Create a unique index.
+
+**concurrent** (`boolean`): Ignored in Aurora DSQL. Indexes are always created asynchronously.
+
+**where** (`string`): Partial index condition.
+
+**method** (`string`): Ignored in Aurora DSQL. Only btree indexes are supported.
+
+**opclass** (`string`): Ignored in Aurora DSQL.
+
+**storage** (`Record<string, any>`): Ignored in Aurora DSQL.
+
+**tablespace** (`string`): Ignored in Aurora DSQL. Tablespaces are not supported.
+
+### Managing Indexes
+
+List and monitor existing indexes:
+
+```typescript
+// List all indexes
+const allIndexes = await storage.listIndexes()
+console.log(allIndexes)
+// [
+//   {
+//     name: 'mastra_threads_pkey',
+//     table: 'mastra_threads',
+//     columns: ['id'],
+//     unique: true,
+//     size: '16 KB',
+//     definition: 'CREATE UNIQUE INDEX...'
+//   },
+//   ...
+// ]
+
+// List indexes for a specific table
+const threadIndexes = await storage.listIndexes('mastra_threads')
+
+// Get detailed statistics for an index
+const stats = await storage.describeIndex('idx_threads_resource')
+console.log(stats)
+// {
+//   name: 'idx_threads_resource',
+//   table: 'mastra_threads',
+//   columns: ['resourceId'],
+//   unique: false,
+//   size: '128 KB',
+//   definition: 'CREATE INDEX idx_threads_resource...',
+//   method: 'btree',
+//   scans: 1542,
+//   tuples_read: 45230,
+//   tuples_fetched: 12050
+// }
+
+// Drop an index
+await storage.dropIndex('idx_threads_status')
+```
+
+### Schema-Specific Indexes
+
+When using custom schemas, indexes are created with schema prefixes:
+
+```typescript
+const storage = new DSQLStore({
+  id: 'my-dsql-store',
+  host: 'abc123.dsql.us-east-1.on.aws',
+  schemaName: 'custom_schema',
+})
+
+// Creates index as: custom_schema_idx_threads_status
+await storage.createIndex({
+  name: 'idx_threads_status',
+  table: 'mastra_threads',
+  columns: ['status'],
+})
+```
+
+## Related Resources
+
+- [Aurora DSQL Documentation](https://docs.aws.amazon.com/aurora-dsql/)
+- [SQL Reference](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-aurora-dsql-sql.html)
+- [Supported SQL Features](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-supported-sql-features.html)
+- [Unsupported PostgreSQL Features](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-unsupported-features.html)
+- [Supported Data Types](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-supported-data-types.html)
+- [Asynchronous Indexes](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-create-index-async.html)