Andrew Wong
54 posts
@41five
Sr. Developer Relations Engineer @ Box
Want to learn how to build a company brain for your agents? 🧠 Join @chriskim_dev & @41five from the @box devrel team on July 28th at 4pm PT for our webinar on creating a governed memory layer with Box APIs and MCP. All code, no fluff, sign-up at: events.zoom.us/ev/AnJFdyO9sHq…
1) Every morning, @Box's DevRel team used to spend time manually pulling together what's new in AI. Last night I demoed how we killed that process at Agent-Led Growth / Agent Experience Demo Night, hosted by Sapient and sponsored by @auth0. Now my @NousResearch Herme agent writes the digest for us, automatically, every day.
Announcing Grok 4.5, our first model trained specifically for coding and agents. It was trained with Cursor and offers frontier intelligence at leading speeds and cost efficiency. x.ai/news/grok-4-5
AI agents need more than intelligence. They need trusted business context. With @GeminiApp Managed Agents now supporting remote MCP servers, developers can connect Gemini agents to governed content in Box, generate outputs from real enterprise files, and save the work back where teams already collaborate. Box MCP Server + Gemini API in action.👇
If you're at @aiDotEngineer World’s Fair and you’re into AI, enterprise content, or deeply committed booth puns, swing by Box booth #S23 Enter the raffle for an X…@Box, and come say hi to @crtr0, @chriskim_dev, and me!
@hwchase17 s “wiki memory” really resonates with how we’ve been thinking about Enterprise Knowledgebases. Agent memory is still early, but one pattern we observe consistently: enterprises don’t need agents to retrieve raw documents, Slack threads or tickets at query time. They need to turn all of that messy source material into a durable, compact, inspectable knowledge layer that future agents can rely on. In the enterprise, memory cannot just be a folder of markdown files sitting somewhere. It needs to be governed, permission-aware, shareable across team members etc. This is where @Box plays a critical role. Box already sits on top of a huge amount of enterprise knowledge. The next step is making that content agent-ready: synthesize the raw source material into structured knowledge, keep it fresh as the underlying content changes, respect permissions etc. That turns Box from a system of record for enterprise content into a governed memory layer for enterprise agents. We wrote about this here x.com/Box/status/206… The future “Company Brain” in the enterprise will be built from trusted source content, agent-maintained synthesis, and enterprise-grade governance.
We're excited to see that @claudeai Fable 5 has been reinstated. It will be available to Box customers in Box AI Studio soon. Watch as the model parses complex vendor agreements and earnings reports across multiple documents and exhibits, and outputs structured, source-grounded analysis that catches inconsistencies a human reviewer shouldn't miss.
Been playing with a workflow for a problem that comes up a lot with agents: They can search a bunch of content, but should they? In real company folders, you’ve got approved docs, stale decks, draft notes, random pricing sheets, etc. So I made a quick demo using: - @Box for the content + permissions - Box Automate so a file upload can kick off the whole review flow, without me running a webhook server - Box MCP via @SlackHQ Slackbot, so context shows up where my team's already talking Mostly just trying to make agent context more like “use the stuff the team actually trusts” and less “search everything and hope” 🙃
Claude Tag is connected to Box so your team can @ mention @claudai right in Slack and query approved docs, templates, and guidance without leaving the conversation. Source-of-truth content from Box, delivered where work happens.
I built a @NousResearch Hermes workflow that my team at @Box uses to track AI trends. Every day at 7am, it researches what's happening across the AI ecosystem and generates a brief for our team. We use it to identify: • AI trends worth paying attention to • Open source projects gaining momentum • New tools developers are adopting • Content opportunities to work on next I've been building agentic workflows for months, and this is one I've actually integrated into my team's daily workflow. Here's how I built it:
