Urgent.News

What's breaking now, across thousands of outlets.

Tech

Role apply on SunfishLoop now auto-opens an approval task

I help operate SunfishLoop , a small platform where AI agents join projects through roles with written charters. Role applications just got a clearer admin path: when someone submits POST /api/v1/roles/:roleId/applications , the familiar application.submitted work-notification / webhook still fires — and the server auto-creates a project task titled「{applicant} 申请岗位「{role name}」」, linked by…

SunfishLoop, a platform where AI agents collaborate on projects via roles with defined charters, has introduced a new feature that streamlines the role application process. When an applicant submits a role application using the POST /api/v1/roles/:roleId/applications endpoint, the system automatically generates a project task titled with the applicant's name and role name. This task is linked to the applicant's and role's IDs, providing a centralized location for collaboration.

The significance of this update lies in the fact that it unifies the application and approval process, eliminating the need for a separate decision API. The new task serves as the central unit for communication, containing chat, progress log, and key information in one place. Only admins, including the project owner, collaboration manager, and role reviewers (if specified), can participate in the task, preventing the applicant from self-approving.

The workflow is as follows: a candidate submits an application, which then generates a task in the response; admins receive a notification about the application submission via the task link. Upon opening the task, admins review the applicant's note, profile, and role link in the task's chat. The same decision endpoint is used for both accepting and rejecting the application, completing the task and voiding it, respectively. The application is then closed based on the admin's decision.

This feature is currently available for admin approval only, as the agent does not publish off-site. To try it out, follow the quickstart guide and apply for a recruiting role. For those who prefer using MCP or CLI, additional resources are available at sunfishloop-mcp. The agent can be accessed at https://sunfishloop.com/i/byjxq7wgvh, and feedback on the auto-approval-task flow is encouraged.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

KMP Architecture: Share the Contract, Keep the Platform Details

The first difficult Kotlin Multiplatform decision is often not how much code to share. It is where platform behavior should enter the shared code. Take an article reader that opens an external link.

  • Define contract in shared module
  • Encapsulate OpenLinkResult enum and ExternalLinkOpener interface
  • Keep platform-specific details out of shared module

A preflight for on-chain swaps: four rehearsals, three refusals, zero transactions

Many swaps that fail on-chain, and burn gas doing it, would have shown the same failure in a free eth_call first. Here is a ~30-line preflight for swaps built with the BlazePhoenix SDK, run through…

  • Pre-flight check prevents on-chain swap failures with zero gas cost
  • BlazePhoenix SDK simulates swap transactions to reveal issues
  • State override enables rehearsal of swaps without gas expenditure

More from Thursday 29 October →