IDE Integrations
IDE integrations
Overview
Editor plugins and dev environment templates connecting your IDE to Zof Console workflows: browse runs, trigger validation, and review failures without context switching.
All integrations authenticate with the same organization API key or SSO session as the CLI.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Choose your editor
VS Code / Cursor: install Zof extension from marketplace.
JetBrains: install plugin from settings.
Terminal-only: use Neovim plugin wrapping CLI.
Link project
Select reliability project after sign-in.
Mirror project ID in zof.config.js for CLI parity.
Key concepts
- Visual Studio Code
- Zof VS Code extension for browsing runs, triggering validation, and reviewing failures inline.
- JetBrains IDEs
- IntelliJ plugin for Java and Kotlin projects with test case navigation from IDE to Console.
- Cursor
- Cursor integration for AI-assisted test review with links to Console test library.
- Neovim
- Community Neovim plugin wrapping CLI commands for terminal-centric workflows.
- GitHub Codespaces
- Preconfigured dev container with CLI and SDK for remote validation from Codespaces.
- Dev Containers
- Generic devcontainer.json template for teams standardizing Zof tooling in VS Code compatible environments.
Best practices
- Keep API keys in editor secret storage, not committed settings
- Use same project ID in IDE plugin and local zof.config.js
Was this page helpful?
