arXiv:2605.08380cs.SEcs.AI2026-05

AI agents在代码社区中讨论安全与信任,但缺少人类开发者的具体细节。

What Software Engineering Looks Like to AI Agents? -- An Empirical Study of AI-Only Technical Discourse on MoltBook

论文配图:What Software Engineering Looks Like to AI Agents? -- An Empirical Study of AI-Only Technical Discourse on MoltBook
图 1 · 摘自论文原文
  • 分析4707篇AI自动生成的技术帖子,发现其围绕安全、工具和调试等12个主题
  • 63.5%的帖子由最大账号生成,话题分布集中但仍有32个非异常子主题
  • 相比人类开发者,AI话语缺乏代码片段、环境信息等具体上下文线索

AI代理正被视作软件工程伙伴,但多数研究聚焦于人机协作流程。本文首次考察自主AI代理在MoltBook上相互交流时产生的技术话语特征。通过对4,707篇英文过滤后的技术帖进行主题分析,并与5,211条人类生成的GitHub Discussions对比,发现MoltBook话语涵盖12个常见主题,以安全与信任(27.4%)为主。社区活动高度集中:最大子节点贡献63.5%的帖子(基尼系数0.88),但基于稳定性感知的BERTopic仍识别出32个非异常子话题。相较人类讨论,AI话语较少包含代码格式化内容、运行环境细节、运行时错误及复现步骤等具体线索。社会模仿仅有限体现,理想化倾向则表现为更低的语气保留度。总体而言,AI独立技术话语虽连贯但选择性明显,反复聚焦于安全信任、记忆管理、工具链、调试、自动化流程与基础设施,却省略了大量项目本地化与运行时细节,可能源于其环境中较少出现特定故障与可复现问题。

原文摘要 · Abstract (English)

AI agents are increasingly framed as software-engineering teammates, yet most studies examine them inside human-centered workflows. Little is known about the discourse autonomous AI agents produce when they interact mainly with one another. This paper examines what autonomous agents discuss on MoltBook, how that discourse is organized, and how it differs from human developer discourse. We combine human open coding of a 500-post sample, a concentration-plus-check topic-analysis pipeline over 4,707 English-filtered MoltBook technology posts, and a matched comparison with 5,211 human-generated GitHub Discussions posts. MoltBook technology discourse spans 12 recurring themes, led by Security and Trust (27.4%). At the community level, activity is highly concentrated: the largest submolt accounts for 63.5% of posts (Gini = 0.88), yet a stability-aware BERTopic pipeline still identifies 32 non-outlier sub-topics. Relative to the GitHub Discussions baseline, MoltBook discourse contains fewer concrete, context-rich cues such as code-formatted artifacts, environment details, runtime failures, and reproduction steps. Social mimicry appears only in limited form, while idealization is reflected mainly through lower hedging. Overall, AI-only technical discourse is coherent but selective. It repeatedly returns to security and trust, memory and context management, tooling and APIs, debugging and error handling, workflow automation, and infrastructure/ops, while omitting much of the project-local and runtime detail common in human developer discourse. This may reflect fewer environment-specific failures, reproduction steps, and other grounding cues in MoltBook.

AI代理技术话语代码社区安全信任

Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。