It has been reported that ByteDance is strengthening control over access to Claude and Codex tools, extending restrictions even to employees who pay for these services out of pocket. According to recent reports, the company has been tightening rules for using external artificial intelligence tools across its staff since the beginning of this month.
The new directives prohibit employees from using personally acquired accounts for third-party AI services, such as Claude and Codex, when working with internal company data. These restrictions affect all L4 level code repositories and documents in Feishu.
Some usage scenarios within the Seed team are reportedly exempt from these new rules. The internal notification sparked active discussions among personnel, whose concerns center on three main issues: whether the restrictions on external AI tools will affect daily development efficiency; where the boundary of the company's data security lies; and whether ByteDance's internal AI tools can meet developers' needs.
In response to these questions, ByteDance Vice President of Technology Hong Dingcun provided clarifications on the company's internal platform. He explained that this decision was made primarily due to data security concerns, emphasizing that any leak of information classified as L3 or higher could have serious consequences.
Hong also refuted suggestions that ByteDance is limiting competitors like Claude and Codex to force employees to use its own products. In Hong's view, attempting to promote a product by banning alternatives and forcing the use of proprietary solutions would be ineffective.
In ByteDance's internal grading system, L4 typically corresponds to technical team leads and some junior management roles. Code repositories accessible at this level contain key technical assets, including the basic architecture of the company's core business areas. Corresponding documents in Feishu may contain confidential project plans and business data.
This is not the first instance of the company tightening restrictions on third-party AI tools. In May 2025, media outlets reported that ByteDance's security and risk control teams notified staff about a phased withdrawal from third-party coding AI tools, such as Cursor and Windsurf, citing data leakage concerns, and proposed its own assistant, Trae, as a replacement.
However, this time the scope of restrictions has expanded. Instead of only affecting third-party developer plugins integrated into development environments (IDEs), the new rules now cover direct access to internal resources through employees' personal AI accounts. In essence, ByteDance is drawing a clearer line between data that can be shared with external AI services and information that must remain within the company.
Notably, ByteDance founder Zhang Yiming reportedly stated at an all-hands meeting with the Seed team in August 2026 that the company would not rely on AI distillation to improve its own models, even if it meant falling behind competitors in the short term.
Collectively, these events indicate that ByteDance's approach to AI tools is not contradictory. The company encourages employees to use external AI tools to boost productivity but remains cautious about sharing core technologies and business data with third-party services. It remains an open question whether internal tools can fully satisfy developers' needs.
Currently, the new restrictions are being implemented in phases. After full implementation, they are expected to affect the daily workflows of thousands of technical specialists. For developers who increasingly rely on AI tools for coding, these restrictions highlight a growing problem: how companies can find the right balance between development efficiency and data security as AI becomes an integral part of daily work?



