Unverified50% confidenceFactExact time
When using local models, prompts and responses stay on the machine; the app has no analytics toolkit and does not send crash reports, but it still checks GitHub Releases for new versions after launch and at most every six hours thereafter, and anonymously counts each time the Cloud toggle is pressed.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/13/2026
First Seen
Valid until: 1/11/2027
Sources
Related Entities
Related Claims
Unverified在主节点故障场景下，GitHub 选择一致性（拒绝服务直到确认新主库）而非可用性，导致任务卡在 Queued 状态而非被错误地重复分配69% similarUnverifiedWhen an owner's GitHub connection is missing, the routine will skip and retry for up to 72 hours rather than closing directly on the first check failure.68% similarUnverifiedWhen Factory polls GitHub to check for tasks, it uses ordinary code to call the GitHub REST API to check for label changes, consuming no tokens, and only launches agents when there is actual work to do.68% similarUnverifiedGitHub's automatic issue closing mechanism: commit messages containing fixes/closes/resolves followed by an issue number will automatically close the corresponding issue, and cross-repository closure is effective under the default configuration.67% similarUnverifiedGitHub Digest plans to let users manually correct wrong priority judgments and to implement a daily email digest, the latter's code is ready but not yet enabled.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1022254API
curl https://kongchang.com/api/v1/knowledge/claims/1022254MCP
get_claim(id=1022254)