Files over tools: how we built our agent with a virtual filesystem and bash
The engineering team at Knock explains how they transitioned from a tool-per-resource architecture to a virtual filesystem and bash-based approach for their AI agent. This shift allows the agent to manage complex customer messaging resources more efficiently by treating API interactions like file operations.
Claude Perplexity Google Gemini GitHub Copilot Grok In March 2026, we shipped the Knock Agent : an AI agent for managing all your customer messaging resources in Knock. It can create and update workflows, templates, and audiences, help segment users, and answer questions about how your customer messaging is performing. The agent can be invoked from the Knock dashboard, a connected Slack workspace, the API, or our MCP server.
Get the full story
Sign up for Headlinne to unlock AI insights, political bias analysis, and your personalized news feed.
Create free accountAlready have an account? Sign in