Tool calls become workflows
Multi-step tool calls are saved as a workflow, so you can rerun it any time.
VEX is the typed language powering Vaktex. Every investigation becomes a workflow you can read, rerun, and hand to a teammate.
input domain: hostsubs = subfinder(domain)live = httpx(subs.subdomains)parallel(max=8) for url in live.urls { r = http.get(url, timeout=5s) expect r.status < 500, "server error", severity="medium"}out(head(live.urls, 5))
Started on sandboxParsed cleanlyhttps://www.example.comhttps://api.example.comhttps://docs.example.comhttps://status.example.comhttps://app.example.com
Multi-step tool calls are saved as a workflow, so you can rerun it any time.
Every tool checks its inputs before a command runs, so code doesn’t fail mid-run.
Developers rerun them as often as they like, without waiting on agents or the security team.
VEX is built to be easy to read and short to write, so models spend fewer tokens on every step.
The runtime optimizes your code for you, so code from agents, or your own rough drafts, runs as if a 10x engineer wrote it.
Algorithms and agents validate every call before anything irreversible changes, so dangerous actions are caught first.
Every finding links to a workflow, so future retests run quickly and your team can confirm it’s resolved.
The cell was re-run and the finding happened again.
Ask. Describe what you want checked, in plain words.
Investigate. Vaktex explores and writes each step as VEX.
Review. Every call, input and check is on the page.
Rerun. On a schedule, or the moment a solution ships.
Book a demo and we’ll write a workflow against a system you choose. Or read how we built the language.