From 5de55725c6bffa7cb2e3e9d2127c64082408fe44 Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Wed, 11 Nov 2026 22:07:03 +0700 Subject: [PATCH] docs(connections): system trust, Local only secrets, lost session state --- connections/connection-form.mdx | 2 +- connections/index.mdx | 2 ++ connections/ssl.mdx | 6 ++++-- databases/cockroachdb.mdx | 2 +- databases/kingbasees.mdx | 2 +- databases/postgresql.mdx | 2 +- features/ai-assistant.mdx | 2 ++ features/icloud-sync.mdx | 2 ++ features/import-export.mdx | 2 +- features/sql-editor.mdx | 4 +++- security/privacy.mdx | 2 +- 11 files changed, 19 insertions(+), 9 deletions(-) diff --git a/connections/connection-form.mdx b/connections/connection-form.mdx index f711771e..feaacf68 100644 --- a/connections/connection-form.mdx +++ b/connections/connection-form.mdx @@ -85,7 +85,7 @@ Encryption sits below the transport. [SSL/TLS](/connections/ssl) covers the mode | **AI Policy** | Per-connection override for the in-app AI agents. **Never** also refuses external clients. Shown while **Enable AI Features** is on | | **External Clients** | **Blocked**, **Read Only** (the default), or **Read & Write** for MCP clients such as Raycast, Cursor, and Claude Desktop, and for [AppleScript](/developers/applescript) and [Shortcuts](/integrations/shortcuts). A token's own scope cannot raise it. See the [integration security model](/developers#security-model) | | **AI Rules** | Guidance the AI reads on every chat turn for this connection: table conventions, columns to avoid, join hints. Shown while **Enable AI Features** is on. See [AI Assistant](/features/ai-assistant) | -| **Local only** | Keeps this connection off iCloud Sync. Shown while **Sync this Mac with iCloud** is on. See [iCloud Sync](/features/icloud-sync) | +| **Local only** | Keeps this connection and its passwords off iCloud. Saving an existing synced connection as Local only removes its passwords from iCloud Keychain, so your other devices ask for them again. Shown while **Sync this Mac with iCloud** is on. See [iCloud Sync](/features/icloud-sync#keeping-a-connection-off-icloud) | The connect timeout is one deadline for the whole network attempt, not a new timeout for each step. It includes the selected SSH tunnel or proxy, TCP, TLS and database authentication. Local SQLite and diff --git a/connections/index.mdx b/connections/index.mdx index f19d5e90..177b93b9 100644 --- a/connections/index.mdx +++ b/connections/index.mdx @@ -112,6 +112,8 @@ The first try comes 2 seconds after the drop, then 4 and 8, doubling to 2 minute Waking the Mac from sleep checks the tunnel of every open connection, and each one that died reconnects alongside the others rather than in turn. +A new session starts empty. When the old one held an open transaction, or something your statements set up there, such as a temporary table, a `SET` value, a user variable, a prepared statement, a cursor, a session lock or a `LISTEN`, the next thing you run on that database is refused once with a message naming what is gone, so a statement written for a temporary table cannot reach the real table it hid. Set it up again, then run your statements. The message names the kinds only, never your statements or their values. Startup commands run again on every reconnect, so they never count, and neither does a routine you call. A **Reconnect** you choose yourself reports only a lost transaction. The refusal goes to whatever runs first on that database, a grid save, Explain or an assistant statement included. + The connections strip, the welcome window and the connection switcher mark a reconnecting connection with a spinner and a lost one with a crossed-out bolt. [Connection state](/features/workspace-rail#connection-state) lists every mark. Hover one to read the cause. On the strip's right-click menu and in the **Database** menu, the connection command follows the state: **Connect**, **Reconnect**, **Stop Connecting** or **Stop Reconnecting**. The welcome window's right-click menu offers **Reconnect** for a lost connection and **Connect** for the rest. **Disconnect** stays on all three menus while a connection reconnects or is lost, and ends it without waiting for the next try. diff --git a/connections/ssl.mdx b/connections/ssl.mdx index 9b746038..f6f6bbb8 100644 --- a/connections/ssl.mdx +++ b/connections/ssl.mdx @@ -3,7 +3,7 @@ title: SSL/TLS description: Configure encrypted database connections, per-driver defaults, and certificate verification --- -Managed databases require TLS, every one of them, from RDS and Cloud SQL to Supabase, Neon, Atlas, and ClickHouse Cloud. Use **Verify Identity** when your provider hands you a CA certificate, or when the driver checks the system trust store on its own: ClickHouse, Trino, Presto, and SQL Server. Otherwise set **Required (skip verify)**. +Managed databases require TLS, every one of them, from RDS and Cloud SQL to Supabase, Neon, Atlas, and ClickHouse Cloud. Use **Verify Identity** when your provider hands you a CA certificate, or when the server's certificate chains to a root this Mac trusts: PostgreSQL and the engines built on it, ClickHouse, Trino, Presto, and SQL Server check the system trust store when no CA certificate is chosen. Otherwise set **Required (skip verify)**. ## Modes @@ -26,13 +26,15 @@ The certificate rows appear only once **SSL Mode** is anything but Disabled. Eac | Field | When it appears | What it takes | |---|---|---| -| **Certificate**, under **CA Certificate** | Verify CA and Verify Identity only | The PEM or DER certificate the server's certificate chains to, for example `/path/to/ca-cert.pem`. Saving without it is blocked, except under Verify Identity on ClickHouse, Kafka, Presto, Qdrant, SAP HANA and Trino, which check the system trust store when it is empty | +| **Certificate**, under **CA Certificate** | Verify CA and Verify Identity only | The PEM or DER certificate the server's certificate chains to, for example `/path/to/ca-cert.pem`. Saving without it is blocked, except under Verify Identity on ClickHouse, CockroachDB, Kafka, KingbaseES, PostgreSQL, Presto, Qdrant, Redshift, SAP HANA and Trino, which check the system trust store when it is empty | | **Client Certificate** | Any mode but Disabled | Your certificate, for a server that enforces mutual TLS. Optional otherwise | | **Client Key** | Any mode but Disabled | The matching private key. Required once a client certificate is set | | **Key Passphrase** | Once **Client Key** has a path, on drivers that support it (Cassandra, ScyllaDB and MongoDB) | The passphrase of an encrypted key. Stored in the Keychain | SQL Server shows no certificate fields at all and verifies against the system trust store. See [SQL Server](/databases/mssql#limitations). Under Verify Identity, SAP HANA and Kafka verify against the system trust store when **Certificate** is left empty. See [SAP HANA](/databases/sap-hana#ssl%2Ftls). +PostgreSQL, Redshift, CockroachDB and KingbaseES under Verify Identity with **Certificate** empty check the server against the roots this Mac trusts, as **Keychain Access** shows them, your own and your organization's trust settings included. A `~/.postgresql/root.crt` file, which libpq reads by default, is used instead when it exists. Backups and restores with `pg_dump` and `pg_restore` check the same way. Verify CA still needs the server's CA certificate: libpq refuses it against the system roots, since anyone can get a public certificate for a host they control. A provider with its own CA, such as Amazon RDS or Supabase, still needs its CA bundle in **Certificate**. + ## Per-driver defaults A new connection starts on the mode that matches the driver's own default, and so does a connection URL that names no mode. The driver's own guidance prints under the picker where there is any. diff --git a/databases/cockroachdb.mdx b/databases/cockroachdb.mdx index 6e648091..af66c9ff 100644 --- a/databases/cockroachdb.mdx +++ b/databases/cockroachdb.mdx @@ -37,7 +37,7 @@ A Cloud connection string carries a cluster routing parameter that the form has --cluster=my-cluster-1234 ``` -Set SSL Mode to **Verify Identity** for Cloud. **Connection Options** goes straight to libpq, so it takes any other libpq option a self-hosted cluster needs. +Set SSL Mode to **Verify Identity** for Cloud. With no CA certificate chosen, the server is checked against the roots this Mac trusts. **Connection Options** goes straight to libpq, so it takes any other libpq option a self-hosted cluster needs. ## What is different diff --git a/databases/kingbasees.mdx b/databases/kingbasees.mdx index 52a8b057..4ffcd043 100644 --- a/databases/kingbasees.mdx +++ b/databases/kingbasees.mdx @@ -71,7 +71,7 @@ Copy tables between KingbaseES in PostgreSQL mode and PostgreSQL, or generate a ## SSL/TLS -The default **Preferred** mode falls back to plain text when the server refuses TLS. Select **Verify CA** to validate the server certificate. See [SSL/TLS](/connections/ssl) for the certificate settings. +The default **Preferred** mode falls back to plain text when the server refuses TLS. Select **Verify Identity** to validate the server certificate and its hostname against the roots this Mac trusts, or a CA certificate you choose. See [SSL/TLS](/connections/ssl#certificate-fields) for the certificate settings. ## Limitations diff --git a/databases/postgresql.mdx b/databases/postgresql.mdx index f449608a..f658425a 100644 --- a/databases/postgresql.mdx +++ b/databases/postgresql.mdx @@ -189,7 +189,7 @@ Sessions run in `UTF8` whatever encoding the database was created with, and the ## SSL/TLS -New connections default to **Preferred** (libpq `sslmode=prefer`): TLS first, plain text if the server refuses it. Pick **Verify CA** to validate the server certificate. See [SSL/TLS](/connections/ssl). +New connections default to **Preferred** (libpq `sslmode=prefer`): TLS first, plain text if the server refuses it. Pick **Verify Identity** to validate the server certificate and its hostname; with no CA certificate chosen it checks the roots this Mac trusts. **Verify CA** checks only the chain and needs the server's CA certificate. See [SSL/TLS](/connections/ssl#certificate-fields). ## Limitations diff --git a/features/ai-assistant.mdx b/features/ai-assistant.mdx index 32dca725..a771ceae 100644 --- a/features/ai-assistant.mdx +++ b/features/ai-assistant.mdx @@ -108,6 +108,8 @@ Every provider can call tools. Claude Agent reaches them through the MCP server, A reply pauses after 25 tool calls, keeps everything it has done, and offers **Continue** for a fresh budget or **Adjust Limit** to change the number, 5 to 200, under **Agent** in **Settings > AI**. Every call is another request with the schema attached, so a higher limit costs tokens. +A reply the provider cut off at the model's output token limit, or because the conversation filled its context window, ends with a note saying so. A tool call cut off with it never runs: its card shows it denied, and the model gets an error asking for the call again with complete arguments. + ### Attach context with `@` Type `@` in the composer to open a picker at the caret: **Schema**, a specific **Table**, **Current Query**, **Query Results**, or a **Saved Query** ([favorites](/features/favorites)). Return or Tab inserts, Escape dismisses. The `@` button in the footer offers the same list minus saved queries; its **Tables** menu shows the first 100 tables, and typing `@` in the composer finds any other. A saved query chip resolves at send time, so the AI sees its current SQL. diff --git a/features/icloud-sync.mdx b/features/icloud-sync.mdx index 898e225c..b7edd6e1 100644 --- a/features/icloud-sync.mdx +++ b/features/icloud-sync.mdx @@ -47,6 +47,8 @@ Connections that use environment variables also need [approval on each Mac](/fea A localhost or throwaway database is rarely worth a round trip. Mark it **Local only** under **iCloud Sync** on the connection form's **Options** tab, or right-click it and choose **Exclude from iCloud Sync**. It shows a struck-through cloud icon in the connection list, and the flag survives duplicating and exporting. +Marking a synced connection Local only moves its passwords, passphrases and other secrets to this Mac and removes them from iCloud Keychain. Your other Macs, iPhone and iPad keep the connection but ask for its passwords again. The form says so before you save, and the menu item asks first. A secret this Mac cannot read or save keeps its iCloud Keychain copy. Passwords of a shared SSH or credential profile belong to the profile and stay where it syncs. A connection that was already Local only keeps any older iCloud Keychain copies until you turn Local only off and on again. + What belongs to the connection stays on this Mac with it: its table and database favorites, the saved queries and folders scoped to it, and its column widths, order, and hidden columns. Edits and removals you make to them wait here while the connection is Local only, and the first sync after you turn it off sends them. Deleting a Local only connection removes those items from this Mac and from nowhere else. ## Checking that it worked diff --git a/features/import-export.mdx b/features/import-export.mdx index 37a19e81..964795f8 100644 --- a/features/import-export.mdx +++ b/features/import-export.mdx @@ -354,7 +354,7 @@ A server that rejects the statement stops the import with that error, so clear t ### Import JSON -The sheet accepts an array of objects `[{…}, {…}]`, newline-delimited JSON streamed a line at a time, and TablePro's own export shape `{ "table": [ {…} ] }`, so an export round-trips. Then choose a destination: +The sheet accepts an array of objects `[{…}, {…}]`, newline-delimited JSON streamed a line at a time, a single object as one row, and TablePro's own export shape `{ "table": [ {…} ] }`, so an export round-trips. A `.json` file is read one value at a time whatever its size, in UTF-8, UTF-16 or UTF-32, with or without a byte order mark. Then choose a destination: - **Existing table**: map each JSON field to a column, as [Map fields to columns](#map-fields-to-columns) describes. A column with no field mapped to it keeps its default or NULL. The list holds tables and partitioned tables, and the server routes each row to the right partition. - **New table**: the name field opens on a name derived from the file, already selected, so one keystroke replaces it. Review the inferred columns underneath. Name, type, primary key, nullable flag, and default are all editable before the table is created. diff --git a/features/sql-editor.mdx b/features/sql-editor.mdx index 7517ff30..0b899998 100644 --- a/features/sql-editor.mdx +++ b/features/sql-editor.mdx @@ -35,7 +35,9 @@ Instead of hardcoding a value, write `:name` and fill it in when the query runs. To run the whole tab, press `Cmd+Shift+Enter`, choose **Run All Statements** from the **Run** button's menu, or use **Query > Execute All Statements**. Nothing needs to be selected first. Select text and `Cmd+Enter` runs the selection instead. -A batch runs top to bottom and stops at the first statement that fails. The error names its place in the run: "Statement 3/5 failed: …". Each statement gets its own result, and each is recorded separately in [query history](/features/query-history). +A batch runs top to bottom and stops at the first statement that fails. The error names its place in the run: "Statement 3/5 failed: …". Each statement is recorded separately in [query history](/features/query-history). + +Each statement that returns rows gets its own result. Statements that return none, such as `INSERT`, `UPDATE` or `CREATE TABLE`, share one result once there are two or more: it is named after how many there were, adds up their rows affected and time, and shows their server output in order. It sits where the last of them ran, so the result of the last statement is the one on screen. A run keeps the last 100 results that return rows. When it leaves older ones out, each result it keeps says how many there were in all. A SQL Server script runs a batch at a time instead, cut at its `GO` lines, so a `DECLARE`d variable reaches every statement after it. See [Scripts and batches](/databases/mssql#scripts-and-batches). diff --git a/security/privacy.mdx b/security/privacy.mdx index 27bde166..3574769f 100644 --- a/security/privacy.mdx +++ b/security/privacy.mdx @@ -118,7 +118,7 @@ Passwords are not one of those record types. The **Passwords** toggle nested und That flag is set on every keychain item the app writes, not only connection passwords: AI provider keys and an older license key go through the same helper. Current account tokens never sync. MCP tokens and Google sign-in refresh tokens do not; their stores always write device-only items. -With password sync off, secrets are written `kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly`, which keeps them on that one Mac. Query history, the activity log, the execution log, tab state, MCP settings, and the sync settings themselves are never synced. Individual connections can be marked **Local only**. Full detail in [iCloud Sync](/features/icloud-sync). +With password sync off, secrets are written `kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly`, which keeps them on that one Mac. Query history, the activity log, the execution log, tab state, MCP settings, and the sync settings themselves are never synced. Individual connections can be marked **Local only**, which also moves their secrets out of iCloud Keychain onto that one Mac. Full detail in [iCloud Sync](/features/icloud-sync#keeping-a-connection-off-icloud). ## The MCP server