Skip to main content
Everything an annotator needs mid-task but does not need permanently on screen lives in the right rail: six tabs that slide out as drawers and disappear when you are done. The design goal is simple: never leave the task to answer a question about the task.

The six tabs

The Data drawer

A scrollable list of the project’s assets with thumbnail, assignee, stage and status per row: the editor’s answer to “let me check a different task” without a round-trip through the project page. Click an entry to jump.
PixlHub dataset drawer listing assets with assignee, stage and status

The Dataset drawer: every task browsable from inside the editor.

The Info drawer

Two tabs cover the current task’s paperwork:
  • Details: status chip, priority, time spent, stage, assignee, annotation count, skip state; the facts a reviewer or manager checks before judging progress.
  • History: the audit trail of status movements, the same trail exposed in the Tasks table.
PixlHub info drawer showing task details including stage, assignee and annotation count

Info: the task's live facts on Details, its audit trail on History.

Working habits

  • Guidelines open beats guidelines remembered. Ambiguity mid-task is a two-second check, not a guess; and if the answer is missing there, that is comment material.
  • Watch the Comments dot. The unread indicator is how reviewer feedback reaches you on rejected tasks; opening the task and ignoring the rail wastes the feedback.
  • Use Data for context, not for cherry-picking. Jumping to a neighboring frame to check how you labeled the same object yesterday is good practice; skipping around the queue to find easy tasks defeats the workflow’s bookkeeping.

Next steps

Comments

Pinned discussion, mentions and resolution.

Agents

What powers the Agent tab.