Tasks

Describe a job once and carry on with your day. viora works on it in the background with your own agent, keeps a log of every step, and tells you, out loud and with a notification, when it's finished.

Three ways to send a task

Say it to the voice desk:

viora, task: find the broken links in the docs folder and fix them
viora, kazi: andaa muhtasari wa ripoti za mauzo kwenye folda ya Q3

Type it in a terminal:

viora task "update the README with the new install steps" --dir ~/Projects/site
viora task "rename the photos in this folder by date" --wait    # stay and watch

Or let another AI hand it over through MCP with the start_task tool.

Follow along

viora tasks                    # recent tasks and their status
viora tasks 20261002-1012      # one task: what it was asked and everything it said

Each task lives in ~/.config/viora/tasks/<id>/ with task.json (status and summary) and log.txt. Tasks started from the terminal or MCP run in their own process, so closing the terminal doesn't stop them.

Which agent does the work

The brain from viora setup, or --brain for one task: claude, opencode, codex, gemini, cursor, qwen, goose, aider, amp, crush or any command. API-only brains can't do tasks because they have no tools.

Safety

• Tasks work in the folder you give (--dir, or workdir from setup).
• Unless actions is off, tasks may edit files and run commands there. With Claude Code they run in auto mode, where risky actions still need approval; with Codex they run in the workspace-write sandbox.
• The agent is told to stop and explain instead of guessing when something is ambiguous or risky.
• Everything it said and did is in the task's log.