DataZen SQL CDC for VS Code

Write, check, preview and publish DataZen SQL CDC pipelines (.sqlcdc files) from Visual Studio Code, against your DataZen cloud or self-hosted agent.

Features

SQL CDC language support

• Syntax highlighting, comment toggling, bracket matching and auto-closing for .sqlcdc files.
• IntelliSense:
  • At the start of a statement, every SQL CDC operation, inserted as a snippet of its required syntax.
  • The next keyword as you type (for example PUSH INTO → DB, HTTP, DRIVE, MESSAGE, …).
  • Inside a statement, the options of that operation with their descriptions.
  • @ lists the parameters declared with DECLARE / SET.
  • [ lists the connections defined on your agent, filtered by type (FROM DB [ shows database connections, FROM HTTP [ HTTP connections, and so on).
  • CALL AGENT [connection] ' lists the LLM models that AI connection offers (the model is optional). Press Ctrl+Space after CALL AGENT [connection] to pick one without typing the quote.
• Hover help on operations, options and parameters, with syntax, examples and a documentation link.
• DataZen: Insert Example… inserts a ready-made example of any operation.

Checks as you type

Scripts are checked with the same rules the agent applies when a job is saved, and problems appear in the Problems panel:

• unknown operations and syntax errors, underlined at the offending token;
• pipeline rules (for example DECLARE must come before the first SELECT/LOAD, only one CAPTURE);
• warnings for connections that do not exist on the agent or have the wrong type.

Some checks (such as license limits and operation-specific settings) are done by the agent itself and are reported when you preview or publish.

Preview

Run a script on your agent and see the results without saving a job, just like SQL CDC Studio:

• Preview Script (Ctrl+Enter): runs the whole script, or the selected text.
• Preview to Cursor (Ctrl+Shift+Enter): runs the script from the top down to the cursor.

Log messages stream to the DataZen SQL CDC output channel and the rows of the last statement are shown in a results panel. Cancelling the progress notification stops the run.

Publish and open jobs

• DataZen: Publish to Agent creates a job the first time (you choose its name, schedule, tags, timeout and whether it is active) and updates it afterwards.
• Before updating an existing job, a side-by-side diff shows what will change. DataZen: Compare with Agent Job shows the same diff at any time.
• DataZen: Open Job from Agent opens the jobs you have open in SQL CDC Studio, or any other job on the agent.
• The status bar shows which job the current file publishes to, with options to link it to another job, unlink it, or publish it as a new job.

Agent connections

• DataZen: Connect to DataZen Agent (cloud or self-hosted), Edit, Remove, Switch and Test DataZen Agent Connection.
• You can save several agents and switch between them from the status bar.

Getting started

1. Run DataZen: Connect to DataZen Agent from the Command Palette (Ctrl+Shift+P):
   • Cloud agent: enter your agent URL, agent id and service token.
   • Self-hosted agent: enter the URL the agent listens on (for example http://localhost:9559), then choose how you sign in: a Service token, Windows Authentication (your signed-in Windows account, no token needed; Windows only), or No authentication.
   • If your service token was issued with a signing certificate, add the certificate (PFX) when asked. Otherwise answer No.
2. Run DataZen: Test DataZen Agent Connection.
3. Open or create a .sqlcdc file and press Ctrl+Enter to preview it.

Service tokens are created in the DataZen portal. The token needs permission to read connections (for connection IntelliSense), read and write jobs (to open and publish), and run SQL (to preview).

Security

• The service token and certificate password are kept in VS Code's secure storage (your operating system's credential store), never in settings files or logs.
• Windows Authentication uses your current Windows sign-in through the operating system (Negotiate / NTLM); no password is asked for or stored. Credentials are only offered to the agent URL you saved, never to a server it redirects to.
• Agent connections are stored per user, not in the workspace, so an opened project cannot redirect your credentials to another server.
• HTTPS is required for cloud agents. Plain HTTP is allowed only for localhost, or for a self-hosted agent after a warning.
• Preview and publish are disabled in untrusted workspaces.

Settings

Known limitations

• Links between files and jobs are stored per workspace and are not shared between machines.
• Certificates must be provided as a PFX file containing an RSA key; certificates in the Windows certificate store must be exported first.
• Windows Authentication is only available when VS Code runs on Windows, and only for self-hosted agents. Requests are sent through a hidden Windows PowerShell process.

Learn more

Documentation: docs.enzounified.com

Reporting issues

Email dev@enzounified.com.

License

MIT (see LICENSE.md in the package). Copyright © 2026 Enzo Unified, Inc. The DataZen agents and platform this extension connects to are covered by your agreement with Enzo Unified; see the Terms of Service and Privacy Policy.