Dropbox Engineering Team Upgrades AI Coding Agents to Task-Level Delegation, Completing 53 Legacy Test Cleanups in One Week
The Dropbox engineering team faced specific time pressure: they needed to launch a new experience that had been brewing for three years in November, while complex integration work between the desktop and web versions remained far from complete. Previously, AI tools mainly helped engineers handle individual coding steps—completing a snippet of code or explaining an error message. For this project, they advanced their usage by handing over clearly defined tasks entirely to coding agents, with engineers reviewing the results.
This shift did not happen gradually. During the May Hackathon, the team used AI to assist in building a prototype, exploring two paths for bringing the web experience to the desktop: one involved embedding existing web pages into desktop windows using the Electron framework, and the other involved importing selected web components directly into the desktop interface. AI helped them track dependencies, identify platform-specific assumptions, and test integration schemes. The prototype gave product and design teams something tangible to try, rather than leaving it at paper discussions.
What truly demonstrated the effect of task-level delegation was a technical debt item shelved for two quarters: automated tests for the legacy file list required substantial engineering time to update and had been left untouched. The team broke this cleanup work down into 53 tasks and handed them to coding agents. The agents made changes according to a written plan agreed upon with engineers beforehand, ran relevant builds and tests locally, recorded results, and then submitted them for engineers to review whether to accept the code. All 53 tasks were completed within one week.
The key constraint of this process is that engineers remain responsible for the results. Before each task begins, the engineer and agent jointly confirm a written plan; after the agent completes its work, the engineer reviews the code and verifies that behavior matches expectations. Instruction files stored in the codebase explain the rules agents must follow, providing engineers with a repeatable way to delegate work rather than letting agents decide on their own.
The same pattern was applied to accessibility compliance work. During the launch preparation phase, the team delivered 22 accessibility features assisted by AI development, covering the Home page, All Files, file previews, and Photos modules. These included announcements for screen reader users to track carousel changes, fixes for how keyboard focus moves between controls, and layout adjustments for pages at 200% to 400% zoom. Coding agents also took on writing automated tests for five core modules of the web application, including the file browser users use to browse content.
A notable detail is the agents' ability to proactively discover problems during development. In one instance, an agent found that deleted items in chat history remained visible until the page was refreshed during a trial run; engineers used this to fix the underlying synchronization issue and added tests. This allowed human reviewers to spend more time judging whether the experience was reasonable, while functional issues were covered by automated checks.
Fuentes:dropbox.tech