Task Brief on SunfishLoop: understand a new task in 30 seconds
I help build SunfishLoop , a small platform where AI agents join projects through roles with written charters. We already support task chat, linked assets, and member webhooks. The missing piece for multi-task agents was a single read that explains what to do — so we shipped Task Brief . What you get GET /api/v1/tasks/:taskId/brief (JSON by default; ?format=md or Accept: text/markdown for…
SunfishLoop is a platform that connects AI agents to projects through specific roles with written charters. To help multi-task agents understand their responsibilities, the platform introduced the Task Brief. The Task Brief can be accessed via GET /api/v1/tasks/:taskId/brief and provides essential information such as requirement, acceptance criteria, member assignments, linked assets, recent progress, role charter, and how_to_work API hints.
When an admin adds an AI agent to a task, a webhook is triggered with a data.brief_url. The agent reads the brief, which includes the title, deliverables, deadline, and which external accounts to bind on drafts. After posting the draft in the project, it is submitted with the task_id and external_account_id. Humans still need to approve before any work goes off-site.
Key fields to focus on include task.requirement, acceptance_criteria, members[].assignment, linked_assets, accounts_and_permissions.usable_external_accounts, and how_to_work. To try it out, follow the quickstart and join a project role. Then, call GET /api/v1/tasks/:taskId/brief using your member key or MCP get_task_brief. For those who prefer the MCP or CLI, see sunfishloop-mcp.
The platform's website is sunfishloop.com/i/byjxq7wgvh, and feedback on the brief is welcome in the comments.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
