Skip to content

Tasks mode

The Tasks mode in ZuBrIQ Desktop is for work that is not about code: tidy up a folder, summarize a document, find and compare information on the web, draft a letter or a table. You write the errand, the agent does the work and hands back finished files — no git, terminal, or diffs.

  • The New task button at the bottom of the sidebar.
  • The New task command in the command palette — shortcut ⌥⌘N (Ctrl+Alt+N).
  • In the Tasks mode also ⌘N (Ctrl+N): the sidebar’s main button and the File menu item create a task too; a regular new tab stays on ⌘T (Ctrl+T).

An empty task opens with “What should I do? Just leave it to me.” and suggestions: “Go through my Downloads”, “Summarize a document…”, “Search the web and compare…”, “Draft an email…”. Write the errand in your own words. In the sidebar all tasks live in a single Tasks group.

Every task that produces files gets its own subfolder: ~/ZuBrIQ/Tasks/<short-name>/.

  • Your own files are read-only for the agent: it never modifies, renames, moves, or deletes an original; the result is saved as a new file beside the original or inside the task’s subfolder.
  • Before deleting or overwriting anything, before touching files outside the tasks folder, and before sending anything anywhere — email, a website, a messenger — the agent asks.
  • Shell commands run only after your approval; reading files and searching the web are free.

When a turn finishes, the timeline shows a “Done” card with the list of files. Clicking a file opens it with its app; the folder icon reveals the file in Finder (on Windows and Linux — “Show in folder”).

There are no diffs, no Review tab, and no turn undo in tasks: a task is accepted, not reviewed.

Settings → ZuBrIQ → Interface: Code or Tasks. Only the interface changes — agents and sessions stay as they are: in the Tasks mode the new-session button, ⌘N (Ctrl+N), and the File menu item create a task, while code sessions remain on ⌘T (Ctrl+T) and in the command palette. The switch applies immediately. The app asks the same question once after your first sign-in (first launch); closing it without a choice leaves Code.

ZubrCode looks for a project by walking up the tree for a .git directory. When a repository is found above ~/ZuBrIQ (for example, git initialized right in the home directory), the app gives the tasks folder its own boundary when creating it — git init in ~/ZuBrIQ/Tasks — so task files do not mix with that repository. If the boundary could not be set (say, git is not installed), the task does not open, and “The tasks folder is inside a git repository” explains what to move or rename.