IDE Integrations
Neovim
Overview
Community Neovim plugin wraps Zof CLI commands for terminal-centric workflows: trigger runs, tail logs, and open failure URLs in browser.
Best for engineers in terminal multiplexers who want minimal GUI context switching.
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
Install plugin
Add via lazy.nvim or packer from community repo.
Ensure zof CLI on PATH: npm install -g @zof-ai/cli
Configure
Export ZOF_API_KEY in shell profile.
Set g:zof_project_id in vimrc or use project-local env file.
Daily use
:ZofRun triggers staging validation.
:ZofOpenRun opens latest failure in browser for triage.
Key concepts
- Organization scope
- All Zof Console and API operations are isolated to your authenticated tenant.
- Governed execution
- Agent output and remediation follow policy packs with human approval when configured.
Best practices
- Use tmux split for zof run --wait output
- Never commit API keys in vimrc
Was this page helpful?