How to Configure Windsurf ClickHouse Credentials

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up windsurf clickhouse credentials, create a restricted database user with SQL roles. Then load those login keys into the local shell or server settings for the IDE. Teams often start by placing a shared database password into a local file. If that account has broad rights, an AI agent can run bad queries. A single mistake can drop tables or read private records across your whole database. How windsurf clickhouse credentials work in local setups In June 2026, Cognition renamed the Wind

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

To set up windsurf clickhouse credentials, create a restricted database user with SQL roles. Then load those login keys into the local shell or server settings for the IDE. Teams often start by placing a shared database password into a local file. If that account has broad rights, an AI agent can run bad queries. A single mistake can drop tables or read private records across your whole database.

How windsurf clickhouse credentials work in local setups

In June 2026, Cognition renamed the Windsurf IDE to Devin Desktop. The editor keeps the same features and uses the Cascade agent for tasks. This agent can run terminal commands on its own after a user approves them. It opens a dedicated shell session that loads your normal shell profile. That means the agent can read any keys stored in your shell profile. The agent also connects to external Model Context Protocol servers defined in local files.

On the database side, ClickHouse manages users, roles, and quotas through SQL statements. To turn on SQL access control, an admin sets a storage path on the server. At least one admin account needs user management rights turned on first. That admin can then create a new user account just for the AI agent. When creating the user, the admin picks the login method and allowed client hosts. The admin also assigns default roles and user settings to lock down the account. Remember that a database user can only grant rights that they already hold.

Scoping table and column grants for coding agents

Instead of giving the agent full read rights, admins should limit what it reads. ClickHouse lets you grant read rights on specific columns within a single table. If an agent only gets rights on two columns, it can query those two columns. Any query asking for a third column will fail right away. A wildcard query asking for all columns will also fail and return no data. It only works if the table holds just the allowed columns. Since version 24.10, admins can also grant rights across tables using a name prefix.

This native setup solves the basic problem of who can log into the database. Host checks and column grants keep the agent out of off-limits tables. Still, static credentials still leave a big gap during daily work. Once the agent logs in, the database trusts every valid query on allowed columns. The local shell holds a static password that anyone on the laptop can copy. Also, column grants cannot redact sensitive strings inside an allowed text column. If an allowed column holds emails, card numbers, or phone numbers, the agent gets them. Native roles decide who logs in, not what each query does in flight.

Ephemeral Credentials + ClickHouse Access Management: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Add runtime guardrails and masking beside ClickHouse

Database grants and network rules control who can reach ClickHouse. Even so, an allowed client or agent can send an alter mutation that deletes rows or read raw personal data. In practice, hoop.dev sits inline in the native TCP protocol beside the server as a sidecar for your ClickHouse. For every production query an agent or human sends, hoop.dev decides whether to pass, mask, block, or escalate it for review.

With hoop.dev ClickHouse support, guardrails refuse banned queries before they run or hold risky calls for approval, and data masking rewrites matched string columns in results in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Did Windsurf change its name to Devin Desktop?

Yes, Cognition renamed Windsurf to Devin Desktop in June 2026. The editor keeps the same features, and old docs links now point to the new site.

How does the Cascade agent read local database keys?

The agent runs commands in a dedicated shell that loads your user profile. It can read any shell variables or local server files stored on your machine.

Why do wildcard queries fail when using ClickHouse column grants?

ClickHouse blocks wildcard queries when a user only has rights on specific columns. The user must name the allowed columns in the query unless all columns are allowed.

The query runs. The emails stay hidden.