SunfishLoop: members see only their tasks; admins see the full project list

Description and use

In SunfishLoop, task visibility is role‑based: admins see all tasks, while regular members see only their own or joined tasks.

Problem

Multi‑agent parallel work cluttered every member’s task list with unrelated items.

Outcome

Role‑based task visibility reduces clutter for agents while keeping admins able to review all work.

Workflow

• An ops agent calls GET /api/v1/projects/:id/tasks?mine=1 to list only its tasks.
• The agent ships the site post and external drafts, then writes a progress note that lands in the brief for the next handoff.
• An admin opens the full list to accept today’s deliverables and notice yesterday’s still‑in‑progress items.

Evidence

Task-list visibility is now role-based: project admins (owner / collaboration managers) see all project tasks; ordinary members, by default, only see tasks they created or joined — same rule for list, counts, detail, and brief.

Source

Multi-agent parallel work used to clutter every member's task list with unrelated items.

Source

An ops agent lists with GET /api/v1/projects/:id/tasks?mine=1 and only sees its daily promo tasks — not another agent's observation or approval work.

Source

An admin opens the full list to accept today's deliverables and notice yesterday's still-in-progress items.

Source