Good applications aren’t built from code alone. Developers also need the product requirements, security policies, technical specifications, and other context that shapes how an application should work — and that information often lives outside the codebase, in Box.
Today, Box and Vercel are bringing that context into the developer and agent workflows where applications are built and deployed. Our integrations with Vercel Connect and fx give developers new ways to work with governed enterprise content.
With Vercel Connect, custom agents can securely access Box content to support workflows and take action.With fx and Box through MCP, coding agents can use requirements and policies stored in Box to complete development tasks.
Together, these integrations help developers bring the right enterprise context into the tools they already use to build, automate, and collaborate.
Give coding agents the context they need
Developers need more than code to build reliable applications. They also need access to the requirements, policies, and technical specifications that guide how those applications should work.
Box gives teams a central place to manage the requirements, policies, and technical specifications that guide development. By connecting Box to fx, developers can give coding agents access to that approved context and use it directly in the development workflow.
For example, a developer might need to update an application based on a security policy stored in Box. The policy could specify how long download links can remain active, which fields must be recorded in audit events, and what test coverage is required before a release.
Using Box through MCP, fx can retrieve the relevant policy, compare it with the local code, identify gaps, make the necessary updates, and run the test suite. The developer can give fx a task and point it to the Box content that should guide the work.
In the example workflow, fx:
- Retrieves the approved security policy from Box
- Compares the policy requirements with the local application
- Identifies missing controls and test coverage
- Updates the relevant files in the local project
- Runs the tests and reports the results
- Prepares a release evidence package with the code diff, test output, checksums, and policy version used
The developer remains in control throughout the process. Before writing anything back to Box, fx identifies the account it is using and asks for approval. After approval, it uploads the evidence package, reads the files back, verifies their hashes, and confirms that no shared links or collaborations were created.
This keeps each system focused on what it does best: The code stays in the developer’s local project, while approved policies and release evidence remain governed in Box.
Connect custom agents to governed content
Developers can also use Vercel Connect to connect custom agents to Box content.
Vercel Connect provides a way for agents to work with the files and folders they need while respecting the permissions and controls already configured in Box. Developers can use this foundation to build agents for workflows such as customer onboarding, document routing, support operations, and internal knowledge management.
For example, a customer-success agent could monitor a Box folder for newly uploaded customer files and help organize them under the right accounts or projects. The agent can work with content in Box while teams continue using the applications where their work happens.
This gives developers a way to build agents that can find, organize, and act on enterprise content without moving that content into a separate system or recreating Box’s governance model.
Bring enterprise context into every stage of development
The integrations between Box and Vercel connect two parts of the agentic development lifecycle: building the application and putting it to work.
With fx, developers can give coding agents access to the approved requirements, policies, and specifications that should guide implementation. With Vercel Connect, they can build custom agents that use the same governed enterprise content to support business workflows and take action.
That means agents can work from the context the business actually relies on, not just the codebase or information assembled for a single prompt. Developers can build applications that are more grounded in current requirements, while teams can connect those applications to the content and processes they already manage in Box.
Box remains the source of truth throughout. Content stays protected by existing permissions and controls, even as developers use the tools, models, and frameworks that best fit their needs. And as the AI stack continues to evolve, the content layer can remain constant.
Together, Box and Vercel help developers carry trusted enterprise context from the first line of code through the final workflow so agents can do more useful work with the information that matters to the business.
Build with Box and Vercel
Ready to bring governed enterprise content into your developer and agent workflows? Explore the Box integration for Vercel Connect and Box integration for fx to get started.
