Tasks View

Tasks View is the antidote to "I'll do that" messages that disappear into the scrollback. Any message can become a tracked task — assigned, due-dated, and surfaced in one list.

Creating a task from a message

Hover a message → ⋯ menu → Convert to task.

Fill in:

• Title (pre-filled with the message text)
• Assignee (defaults to you)
• Due date (optional)
• Description (optional, markdown)

The task is pinned to the source message with a small badge. Click the badge to see who owns it and when it's due.

Creating standalone tasks

Type /task in any channel composer, or click New task in Tasks View. Standalone tasks belong to a channel but don't have a source message.

Tasks View

Every channel has a Tasks tab. Shows:

• Open tasks, assigned to anyone, with due dates.
• Your own tasks across every channel (via the "My Tasks" filter).
• Overdue tasks highlighted in red.

Filters:

• Status (open, in_progress, done)
• Assignee
• Due date range

Task statuses

• open — newly created.
• in_progress — optional intermediate state (click the circle to toggle).
• done — strikethrough in the list. Auto-collapses after 7 days.

Notifications

Task owners get:

• DM when a task is assigned to them.
• Reminder 24 hours before the due date.
• Reminder on the due date.
• Daily digest of overdue tasks at the start of their working hours.

Bulk updates

Shift-click tasks in Tasks View to select multiple, then bulk:

• Reassign
• Set due date
• Change status
• Delete

Integration with other ARK products

• Track — a task in Comms can optionally link to a Track record; Track's activity timeline shows the Comms task and vice versa.
• Ink — embed a task block inside an Ink page; the task syncs with Comms Tasks View.

Cross-product integrations require the products to share one Supabase project.

Data model

Tasks live in the channel_tasks table (see Database Reference). A task has a source_message_id when it originated from a message — NULL for standalone tasks.

Keyboard shortcuts

Limitations

• Tasks don't support subtasks in the current version — use a channel + tasks-per-message pattern instead.
• No recurring tasks. Use Pulse (/docs/pulse/features/reminders) if you need recurrence.