Matrix tasks
The Matrix workspace in onemind BETA lets your team track tasks, review AI-tool activity, and respond to permission requests from one place; it is available on all active onemind accounts.
Matrix workspace
Open Matrix from the BETA side panel. The left panel shows a grouped list of tasks and onemind agent conversations. Use the view icons at the top of the panel to change how items are grouped:
| View | What it shows |
|---|---|
| Project | All tasks across every Project, grouped by Project |
| Human | Tasks grouped by the member who created or was assigned them |
| Agent | Tasks grouped by the AI tool and its owner |
| Recent | All tasks in a flat list, sorted by most-recent activity |
| Needs me | Work that waits on you (a tool's request to answer, a follow-up or assignment to approve, or your blocked or failed task), then what runs for you, then what finished in the last 7 days for you to review |
Archived at the bottom of the panel shows only your archived tasks. The panel remembers your last-selected view and reopens to it on your next visit.
The search field under the view icons narrows every view to tasks whose title or details contain all the words you type, and to sessions whose title does.
Select any task to open its detail panel on the right. Tasks support deep links: share or bookmark a task URL to open Matrix and select that task directly.
Create and assign tasks
Select + at the top of the panel to open a new onemind agent chat. From the agent start page, select Create manually to open the Create Task form directly.
The Create Task form has:
- Title — required, up to 160 characters
- Project — the Project this task belongs to
- Assignment — optionally select an AI tool to assign the task at creation time
- Details — markdown description of the work, up to 2000 characters
Any team member can create a task.
Task Checker
After you submit, the Task Checker runs for you (the task creator) and checks whether duplicate or similar tasks already exist. When it finds matches, each is labelled Same or Similar with a similarity percentage. Review any matches shown. The check always ends with the task in Todo (no blocking match, or no match that prevents creation) or Assigned (if you assigned the task at creation). Run Task Checker appears again only when the check result is still pending.
Assigning a task
Any team member can assign a todo task. Open the task and choose an AI tool from your team's connected tools.
If the selected tool belongs to another member, an approval request goes to that owner. The task shows Awaiting approval until the owner decides. The tool owner also receives a notification in their inbox and can approve or decline directly from there without navigating to Matrix. On approval the task moves to Assigned; on decline it returns to Todo so you can choose a different tool.
To reassign a task that is in Assigned, In progress, or Blocked, open the task row menu and select Handoff to choose a different tool.
Matrix tasks run through the macOS app on the tool owner's Mac. Assigning a task to Codex, Claude Code, Grok Build, OpenCode, Hermes Agent, or Pi starts the tool automatically as a managed process — you do not need to launch it first. Other connected tools are not offered when you assign a task (see AI tools on your Mac).
Task statuses
Tasks move through the following statuses as work progresses:
| Status | What it means |
|---|---|
| Pending check | The Task Checker is running; the task cannot be assigned yet. |
| Todo | No blocking match found; ready to assign to an AI tool. |
| Assigned | A tool has accepted the task but has not started work yet. |
| In progress | The assigned tool is actively running. |
| Blocked | The tool cannot continue and is waiting for a decision or resource. |
| Completed | The tool finished the task successfully. |
| Failed | The tool encountered an error and stopped. |
| Cancelled | The assignment was withdrawn before or during work. |
Task details and activity
Select any task to open its detail panel. The panel shows the task's run transcript and a Task logs section with key events:
- A row showing when the task was created or last updated
- A row for each assignment or approval action
- A Handoff to <tool> row each time the task is routed to a different tool, including on the first assignment
Edit task is in the task row menu. Editing creates a new revision and withdraws any pending check or assignment.
Stop appears while a run is in progress and can be stopped; the task shows Stopping… until the tool confirms the stop.
Non-owner follow-up approval
When a run has finished, the tool owner can send a follow-up message directly from the composer. If you are not the tool owner, you can still type a follow-up; the composer notes that the owner must approve it before it runs. After you send, the follow-up shows Awaiting owner approval. The tool owner can Approve, Allow for this task, or Decline the follow-up from the task detail panel or directly from their Notification inbox.
When a task is assigned to a native tool and the tool's device has not yet picked up the run, the task shows a waiting indicator. If the device is offline, a notice appears with an option to reassign the task to a different tool or device.
Archive tasks
Archiving removes a task from your active list view without stopping any work in progress or deleting the conversation. Open a task row menu and select Archive. Archived tasks are hidden only from your own active views; conversations are kept and ongoing work continues.
An Undo action appears briefly after archiving or restoring so you can reverse the action immediately.
To view archived tasks, select Archived at the bottom of the panel. From there, open a task row menu and select Restore (or Unarchive) to return the task to your active list.
Archiving is personal — it affects only your own view. Other team members still see the task in their active list.
Task workbench
When a task has an active or completed run from a native AI tool, a workbench pane appears alongside the session transcript. Two tabs are always shown:
Task detail — the task's title, description, and current status.
Changes — shows the diff of the git repository branch the assigned tool is working on. A file list on the left lets you jump to individual files; each entry shows a status (Added, Modified, Deleted, or Renamed) and line counts. To share the current diff with your team, click Share changes. Sharing creates a team-visible snapshot with secrets masked; later edits require a new share. Each shared snapshot shows a summary in the form "name · N files · +additions −deletions". The tool owner shares from the Mac running the tool; other team members see what the owner has shared. If the working folder is not a git repository, the tab shows a notice.
On the Mac that is running the tool, two additional tabs appear:
Terminal — shows structured output entries from the AI tool's run. You can expand or collapse individual entries, and use Expand all, Collapse all, and Copy all output to manage the full log.
Preview — shows a local development server preview. Enter a local URL in the address bar (limited to localhost, 127.0.0.1, or [::1]), then click Reload to refresh it or Open in browser to open it in a new tab.
Task interactions from the sidebar
Select a task to open its detail panel. When a run has finished and the tool accepts follow-ups, type a message in the composer and press Shift+Enter to send (or Enter for a new line). The owner of the tool sends follow-ups directly; non-owners submit them as requests requiring the owner's approval (see Task details and activity above).
Answering permission requests and questions
When the assigned tool requests permission to perform an action, a permission card appears in the task detail. Only the owner of the Mac running the tool can answer a permission request. When the tool asks a question instead, the task creator can also answer. Select Allow once to grant permission for that action, or Decline to refuse. Some requests include structured form fields; fill them in and select Send answer to pass input back to the tool.
A request shows how much time remains; if no answer arrives in time, the tool treats it as declined. After an allow, the tool's run continues in the same task context. Permission requests also appear in the Notification inbox, where the tool owner can respond without navigating to Matrix.
Project sessions in the matrix list
Sessions from Codex, Claude Code, Cursor, Grok Build, Qoder, Pi, and CodeBuddy can appear in the task list and in task details alongside tasks. When AI sessions first become visible, a notice reads: "AI sessions are now visible in Matrix. Project sessions from your connected AI tools appear in task details and the board. You can turn sharing off in Settings." onemind accepts a session only from an AI tool you connected to onemind on that Mac.
The owner of a session can control who sees it. In the task detail, select Show to team or Hide from team for that session. Hidden sessions are visible only to their owner.
You can continue one of your own Codex or Claude Code sessions from onemind. When the session is idle and its Mac is online with the macOS app running, its details show a Continue this session box. Your message resumes the same session on that Mac, in the folder where it ran, and the session continues as a Matrix task. A session in the middle of a turn waits until the turn ends.
To stop sharing, go to Settings > Preferences and turn Share AI sessions off. The switch covers every AI tool you connected, and turning it off removes the sessions you already shared. While sharing is on, your sessions are visible to all team members unless you hide an individual session.