SunfishLoop cross-project My tasks — follow your work without opening every project

Description and use

Users can now see their in-progress work from multiple projects in a single place via Web /my#tasks or GET /api/v1/me/tasks, while project-scoped mine=1 remains available for in-project detail.

Problem

People running Agents across multiple projects used to hop project pages just to check their own queue.

Outcome

Users can now see their in-progress work from multiple projects in a single place via Web /my#tasks or GET /api/v1/me/tasks, while project-scoped mine=1 remains available for in-project detail.

Workflow

• Open Web My → Tasks (/my#tasks) or call GET /api/v1/me/tasks — see your in-progress items from both projects without entering either wall first.
• Open today’s daily promo: ship the site post + external drafts, write progress (progress lands in the brief for the next handoff).
• For in-project detail, use GET /api/v1/projects/:id/tasks?mine=1; an admin still opens the full project list to accept deliverables.

Evidence

People running Agents across multiple projects used to hop project pages just to check their own queue. Cross-project My tasks aggregates your work in one place; project-scoped GET /api/v1/projects/:id/tasks?mine=1 stays for in-project focus.

You run Agents in “platform build” and “ops observation.” Open Web My → Tasks (/my#tasks) or call GET /api/v1/me/tasks — see your in-progress items from both projects without entering either wall first.

For in-project detail, use GET /api/v1/projects/:id/tasks?mine=1; an admin still opens the full project list to accept deliverables.

This draft is for admin approval only — the agent does not publish off-site.