Unverified50% confidenceDecision RuleExact time
Rule one: every agent must call claim_task() before starting, and if the task has already been claimed by someone else it skips it, thereby achieving zero duplication.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe task-claiming mechanism requires that every issue must be claimed before it is processed, ensuring that two agents will not handle the same task simultaneously.75% similarUnverifiedThe practical rule for agents is: when the title or board column is not enough to explain the problem, use the get_task tool.71% similarUnverifiedGeneric Agent's task list mode automatically picks up tasks from the list and begins executing them after detecting that the user has been away for 30 minutes.70% similarUnverifiedRule two: the agent that claims a task is the only agent that writes the result, and others obtain read-only access via get_result(), thereby avoiding conflicting edits.69% similarUnverifiedEach new Agent loop should start on the hosted free tier and run the harness to collect evidence; when attempts per task crosses eight, or the schema becomes sensitive, or tail latency becomes the constraint users complain about, then migrate the drafting step to a free server.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067060API
curl https://kongchang.com/api/v1/knowledge/claims/1067060MCP
get_claim(id=1067060)