Sightdeck AIAgentic Studio

User Guide

Team settings

One person, one shared counter — that works until two of you add tasks to the same project. A project's team gives every member their own prefix, so ownership lives in the task id itself and two people never collide.

What it is

A project's team is an optional list of members, each with a short prefix (CD, MW, BOT). Once a team exists, every new task belongs to one member — claimed to a specific person, or left as a System Task belonging to the project itself.

The member prefix becomes part of the task id: a task CD created is SD-CD-5, one MW created is SD-MW-5. Project prefix first, then member prefix, then the number. A task nobody claimed keeps the project prefix alone — SD-2561 — exactly as it always did. The team list lives in the project's shared settings, so every teammate sees the same members.

What you get

  • Conflict-free numbering. Two people working the same project offline never collide — CD-5 and MW-5 are two different tasks, even before either of you has pulled the other's commits.
  • Ownership without an extra field. The owner is visible in the id itself — no "assigned to" column, no sync with an external tool, works offline.
  • Clean-slate migration. A project that starts with no team and adds one later keeps its history exactly as it was — every existing task becomes a System Task, new members simply start from 1.
  • Every member's tasks are protected. Only the owner can change a task; everyone else can still open and read it. A teammate's task shows This task belongs to … and is read-only here. Only its owner can change it. The same holds on Sightdeck Remote.
  • A claim that stays on your machine. Which member you are is a per-machine setting, not something committed to the repo — pull the project on a different machine and you claim it there separately.

How you use it

  1. Open Edit project → Team.
  2. Enter a member's name and a prefix (uppercase, typically 2–3 letters), then + Add member. Repeat for each teammate.
  3. Save. Existing tasks become System Tasks automatically — owned by nobody, still using the project prefix.
  4. On each machine you work from, find your name in the list and click Claim, then save. Sightdeck will not let you create a task until a claim is made on that machine — the Team tab shows a red banner if none exists yet.

Once claimed, every task you create carries your prefix automatically — nothing to pick per task. A Member scope filter above the task list (and in Journals) narrows the view to your own tasks, everyone's, or one teammate's.

Project settings Team tab with member names, prefixes and a Claim button
Edit project → Team — add members, then claim one on each machine you work from.

The split store

Once a team exists, Sightdeck stops keeping the whole board in one sightdeck.xml and splits it by owner instead — one file per member, plus a shared project file for settings and one for tasks that predate the team. This is what makes two members adding tasks conflict-free: they are writing to two different files. The migration runs on its own the first time a task is saved after a team is added (with a backup written first), or you can trigger and confirm it by hand from the Team tab.

The rare case — two of you editing the same task before pulling — is still caught by a merge driver Sightdeck ships: both sides' history is kept, and a field you both changed is recorded as a Merge conflict you resolve with one click (Keep mine / Take theirs) instead of a broken XML file. The Team tab offers a one-click Register the first time it sees a machine that has not set the driver up.

Reassigning and removing

  • Reassign a task — open it, use the … menu in its details and pick Reassign to…. The task gets a fresh id in the target member's range and its concept and attachments move with it; the old id is retired, not redirected. An Epic takes its subtasks along; a running task must go back to Backlog first.
  • Hand a task back to the project — the same Reassign flow can also target the project itself, so a claimed task becomes a plain System Task again, numbered like any unclaimed one.
  • Remove a member — Team → find them → Remove. This only takes away their ability to mint new ids; their existing tasks, history and concepts stay exactly as they are, listed under a quiet Removed member row. Re-add brings them back where they left off.