Kestra Workbench
Browse, edit, run, inspect, search, and follow Kestra flows and executions from VS Code.
Kestra Workbench gives teams a focused VS Code surface for Kestra work: manage connections, explore namespaces and flows, edit Flow YAML, run flows, inspect executions and logs, follow running executions live, jump between parent and child executions, and open the same Workbench in an external browser when a full browser workspace is easier.
Use at your own risk
This extension talks directly to your configured Kestra instances and includes write-capable actions. Creating, saving, running, deleting, or rolling back flows can change data or start real workloads in Kestra. Review the selected connection, tenant, namespace, and flow carefully before using these actions. Use this extension at your own risk.
Features
- Manage multiple Kestra connections from VS Code.
- Browse connections, tenants, namespaces, and flows in the Activity Bar.
- Search flows across configured Kestra instances.
- Open and edit Flow YAML directly in VS Code.
- Create namespaces and flows.
- Save Flow changes back to Kestra.
- Run flows and fill in required inputs before execution.
- Review flow revisions, compare changes, and roll back to a previous revision.
- Get Kestra-aware suggestions while editing Flow YAML.
- Open flows and namespaces in the Kestra web UI.
- Browse executions by namespace, flow, status, labels, time range, and text search.
- Inspect execution details, task runs, logs, inputs, outputs, variables, triggers, and subflows.
- Follow running executions automatically with live refresh.
- Search within the currently visible detail view and highlight matching text.
- Jump to parent executions and the outermost known execution in a subflow chain.
- Open Kestra execution deep links in the local Workbench view when a matching local connection exists.
- Open the Workbench in a local browser view served by the extension on
127.0.0.1.
Commands
- Kestra Workbench: Verbindungen verwalten opens the connection manager.
- Kestra Workbench: Flows aktualisieren refreshes the Flow tree.
- Kestra Workbench: Flows suchen searches and opens flows.
- Kestra Workbench: Flow schnell öffnen opens a flow from a Quick Pick.
- Kestra Workbench: Namespace anlegen creates a namespace.
- Kestra Workbench: Flow anlegen creates a new flow.
- Kestra Workbench: Flow ausführen runs a flow.
- Kestra Workbench: Flow-Revision öffnen opens a historical flow revision read-only.
- Kestra Workbench: Flow-Revision vergleichen compares the current flow with a selected revision.
- Kestra Workbench: Geöffnete Flow-Revision zurückrollen rolls an opened historical revision back to Kestra.
- Kestra Workbench: In Kestra Editor öffnen opens the selected flow in Kestra.
- Kestra Workbench: Namespace in Kestra öffnen opens the selected namespace in Kestra.
- Kestra Workbench: Browser starten starts the local browser view.
- Kestra Workbench: Im Browser öffnen opens the local browser view, starting it first when needed.
- Kestra Workbench: Browser ausschalten stops the local browser view.
The Activity Bar view Kestra Workbench: Flows contains the Flow explorer and the connection actions. The status bar item Kestra opens a small menu to start, stop, or open the local browser view.
Settings
kestraWorkbench.runOpenMode: choose whether a successful flow run opens the new execution directly in the Workbench view (direct, default) or shows a prompt with a link (prompt).kestraWorkbench.executionOpenTarget: choose whether executions opened after a flow run use a VS Code tab (tab, default) or the external browser (browser).
Privacy
Kestra Workbench does not include data tracking, telemetry, or usage analytics. The extension does not send usage data to the publisher.
Security
The VS Code extension talks to Kestra from the extension host. API tokens and passwords are stored with VS Code SecretStorage, while non-secret connection metadata such as name, URL, edition, version, tenants, and authentication type is stored in the extension's VS Code state. SecretStorage is provided by VS Code and uses the secure storage mechanism available on your platform.
The extension webviews receive connection metadata, but they do not receive stored passwords or API tokens. The local browser Workbench binds to 127.0.0.1 and uses a per-session local cookie for API access.
Kestra connections may target custom HTTP or HTTPS endpoints. Only add connections that you trust. HTTP connections transmit credentials without TLS and should only be used on protected internal networks.
If you enable insecure TLS for a connection, certificate validation is disabled for that connection. This can be useful for internal test systems with self-signed certificates, but it weakens transport security.
