Ultimately, we opted to build the agent loop, tools, and the system for gathering context ourselves, and we connect directly to model providers instead of relying on a broad agent framework. That's because a framework we initially explored lagged behind the provider APIs we wanted to use and included more structure than Reclaim needed.

DropboxPublished by the organization itself (post), no named author

Post: Evolving our calendar assistant Reclaim to be AI-native without starting over, Dropbox.Tech, September 29, 2026, at Building the agent platform.

Not yet checked [ Grade B ] Said in the last year Dropbox: $2.5 billion revenue, FY2025

Filed under

How this was checked

Not yet checked by an independent second reader. The wording, speaker and date come from the source linked above; treat it as a lead until it is confirmed.

Matched word for word against the raw page fetched with curl (tags stripped), an engineering post by Dropbox authors Greg Unrein, Josh Jensen and Christopher Wildman. Curly apostrophes normalized to straight.

How to cite this passage

Dropbox, “Evolving our calendar assistant Reclaim to be AI-native without starting over”, Dropbox.Tech, 2026-09-29, at Building the agent platform. https://dropbox.tech/machine-learning/evolving-calendar-assistant-reclaim-to-be-ai-native Archived at https://the-ai-record.com/passages/dropbox-build-agent-loop-tools-context-ourselves-framework-lagged-2026

More from the same source

That's why we developed Preview Mode, which gives users a temporary version of their calendar where they can review AI suggestions and changes requested through chat before applying them to their actual calendar.

DropboxPublished by the organization itself (post), no named author

Post: Evolving our calendar assistant Reclaim to be AI-native without starting over, Dropbox.Tech, September 29, 2026, at Making calendar changes consistent and reviewable.

Not yet checked [ Grade B ] Said in the last year Dropbox: $2.5 billion revenue, FY2025 Passage page

Whether a request comes from a user, the automated scheduler, or an agent, the same Schedule Action type is used, including the same validation and commit process.

DropboxPublished by the organization itself (post), no named author

Post: Evolving our calendar assistant Reclaim to be AI-native without starting over, Dropbox.Tech, September 29, 2026, at Making calendar changes consistent and reviewable.

Not yet checked [ Grade B ] Said in the last year Dropbox: $2.5 billion revenue, FY2025 Passage page

Something wrong? Report a correction. JSON: /api/v1/passages/dropbox-build-agent-loop-tools-context-ourselves-framework-lagged-2026.json