Agents that can code will equally be able to use tools exceedingly well. This allows you to start to automate tasks across a workflow that requires both a component of non-deterministic intelligence but also deterministic system interaction.

An example would be using something… https://t.co/ziNaeIUR8T

— Aaron Levie (@levie) 31 mars 2026

Agents that can code will equally be able to use tools exceedingly well. This allows you to start to automate tasks across a workflow that requires both a component of non-deterministic intelligence but also deterministic system interaction. An example would be using something like Codex to automate a workflow connecting data from Box to multiple other systems. The coding agent can interact with systems like an engineer via CLI/MCP/APIs, or write code on the fly when new problems are encountered in a workflow. This will also be one of the reasons you’ll see more technical and engineering roles start to help automate work in non-engineering domains. Marketing, finance, supply chain, pharma research, and other areas where there’s a large amount of data and systems to talk to all have these properties. Box (@Box) Codex just turned an upcoming meeting into a fully automated cross-platform workflow. Box. Gmail. Slack. It researches across all three, synthesizes the context, and delivers a pre-meeting brief without anyone lifting a finger. This is what personal productivity looks like when agentic automation does the work for you. See it in action.👇 — https://nitter.net/Box/status/2039056257282449696#m

→ View original post on X — @romainhuet, 2026-03-31 19:39 UTC