Would you use a CLI tool that turns English into local automation workflows?
I'm building Viba: a terminal-first automation tool.
You type "every Monday at 9am, query Postgres and email the CSV to team@" and it compiles that to a DETERMINISTIC CONFIG workflow spec, then executes it locally with a daemon.
No cloud dependency, no GUI. Runs over SSH, in containers, wherever you have a terminal. Credentials stay on your machine (AES-256). Uses your own OpenAI/Anthropic key for the NL planning.
Core is working (file ops, HTTP, email, cron, file watchers). Looking for early users and collaborators to help build out integrations.
Is this something you'd actually use? What integrations would matter most to you? The question everyone is wondering, "Why not just use Claude Code?" Claude Code is an interactive coding assistant. Viba is an automation runtime. You wouldn't use Claude Code to run a cron job at 3am or watch a directory for new files. Viba compiles your intent into a persistent and versioned workflow that runs unattended with triggers, retries, and history... more like a local first, AI-configured n8n than a coding agent. > You wouldn't use Claude Code to run a cron job at 3am or watch a directory for new files. I wouldn't use anything besides cron to do that. The point is I can ask Ai to write that for me, looks exactly like your example. > ...is an automation runtime aka Claude Cowork > Viba compiles your intent into a persistent and versioned workflow aka Claude Skills > more like a local first, AI-configured n8n than a coding agent. why viba over claude + n8n?