- Your Personal Knowledge Graph Now Lives Outside the Control Plane
Enterprise AI teams running centralized orchestration stacks now have a new variable to account for: AWS Quick, which expanded this week to a desktop-native agent that builds a persistent personal knowledge graph and executes actions across local files and SaaS tools — outside the visibility of most control planes.
Unlike chat-based copilots that reset with each session, Quick now maintains a continuously updated knowledge graph built from the user's local files, calendar, email and connected SaaS apps. It uses it to proactively trigger actions without waiting to be asked.
AWS launched Quick in October last year as an alternative to AI workflow and productivity platforms coming from Google, OpenAI and Anthropic. It was a way for enterprise employees to access insights from connected applications, an agent builder, deep research, and workflow automation. Now, it’s grown beyond a simple AI assistant and acts more as a proactive workflow agent with a stateful, real-time knowledge graph of the user. It integrates with third-party apps like Google Workspace, Microsoft 365, Zoom, Salesforce and Slack — and now local files — so the agent can gather context and take actions.
“What we’ve been hearing is that many enterprises have not been happy with how difficult it is to get context from their legacy tools,” Jigar Thakkar, vice president of Quick Suite at AWS, told VentureBeat in an interview. “Our vision is that Quick is a desktop experience that is the one place where people can go to get all their information and tasks.”
Governance blindspots
Enterprises often put orchestration layers at the center to help guide and manage agents. Context is pulled in, decisions are made, and then actions are executed within defined system boundaries.
Recent releases like Anthropic’s Claude Managed Agents or updates to OpenAI’s Agent SDK also push for more stateless, autonomous agents within enterprise workflows, but still operate within defined orchestration boundaries.
Quick still operates under enterprise controls, something that AWS has always underscored with its AI products, so actions taken on Quick remain bound by permissions, identity and security. Integrations remain managed by either an API or an MCP connection.
However, this evolution of Quick introduces a more subtle shift in the decision layer. AWS updated Quick to build a personal knowledge graph that learns more about the user the more they interact with the platform. It builds a profile based on how they use local files, calendar, email or third-party app integrations to proactively suggest actions such as reminding a team leader to set up check-ins.
Enterprises should be wary that a kind of shadow orchestration could arise in a system like this. The personalized context means the decision layer focuses on implicit triggers rather than set workflows, user-specific interpretations, and different action timings. Practitioners are rightfully wary of this much autonomy, understanding that shadow orchestration may not be something completely under their control.
Upal Saha, co-founder and CTO of Bem, told VentureBeat in an email that platforms like AWS Bedrock AgentCore, its managed agent runtime, and similar ones from Salesforce "maximize autonomy rather than accountability" so enterprises are not losing agent visibility by accident.
"When you deploy an agent that reasons its way to a decision across multiple steps, you have already accepted that you will not be able to fully explain what happened after the fact," Saha said. "That is fine for a demo. It is not fine for a claims processing pipeline or a financial workflow where a regulator can ask you to produce a complete audit trail for every automated decision made in the last three years."
AWS said the platform's governance model is designed to address these concerns. “Users can set up different agents and automated workflows tailored to their role — things like monitoring tickets, pulling data from connected systems, or drafting docs — all managed within a governed environment where IT retains control over what's connected and what data flows where. It's designed to give individual users flexibility while keeping enterprise-level oversight in place,” an AWS spokesperson said.
A possible blueprint
Quick’s evolution from an AI assistant to something more proactive represents a possible approach some enterprise software providers will take to deep AI agent integration into workflows. While what AWS wants to accomplish with Quick—better context from apps and local files and a strong understanding of what its users actually want to do—is not unique, it isn’t focusing on traditional orchestration. Instead, it’s relying on context-driven agent management.
This market tension is growing, as evidenced by the release of similar platforms. Mistral, for example, announced Workflows the same day as the updates to Quick. That platform uses a more traditional orchestration framework.
Stateful and personalized agents continue to evolve, and so do the questions around how enterprises govern them.
- Discover how agentic context infrastructure transforms scattered team discussions into actionable data.
As AI model providers increasingly move downstream, launching products and agents for specific enterprise applications and sectors like finance, one big question still remains: how will said AI agents be equipped with the proper context surrounding a task — who assigned it, which other stakeholders are involved, what data or discussions have taken place about it and how it should be done?
This practice of "context engineering" remains one of the great unsolved problems of the AI era. But SageOx, a Seattle-based startup founded by the veterans who built the original AWS EC2 and EBS infrastructure, believes it has the answer: a new systems layer it calls "agentic context infrastructure."
Using a combination of small hardware recording devices and the existing applications enterprises already rely on — Slack, email, documents, files — and applying new, open-source frameworks and instructions atop it all, SageOX has developed a system by which enterprises can keep agents as "in-the-loop" and updated on the enterprise's tasks as their human employees are, and prevent them from "drifting" off their assigned tasks and the firm's larger goals.
“We are capturing all of this context where it happens," said Ajit Banerjee, founder and CEO of SageOX and a former Hugging Face, Meta, Amazon and Apple engineer said in a recent video call interview with VentureBeat. "Product development is a team sport, and the context doesn’t just come from people typing on a keyboard. It happens in conversations.”
By capturing the "why" behind the "what"—the intent that lives in Slack threads, whiteboarding sessions, and water-cooler conversations—SageOx aims to provide a "hivemind" that ensures agents don't drift and humans stay in flow.
"The way people have to work is not old-school coordination, where I write down an issue and then it goes through a sequence. It has to be almost like playing jazz," Banerjee added.
Today, the company emerged from stealth to announce its $15 million seed round led by Canaan and participation
from A.Capital, Pioneer Square Labs, and Founders’ Co-op.
The architecture of team memory
Today’s AI agents operate in isolated sessions, lacking a shared memory of prior decisions or architectural intent.
Every task effectively starts from scratch, forcing developers to manually recap context—a process that undermines the very speed agents are meant to provide. SageOx addresses this through a multi-surface product suite designed to capture context wherever it naturally occurs.
At the center of this ecosystem is the Ox Dot. A customized hardware device designed for the shared office, the Dot captures meetings, standups, and design reviews with a single touch.
Its most distinctive feature is "Auto Rewind"—a fail-safe for the spontaneous brilliance of a team. If a breakthrough happens during an unrecorded conversation, Auto Rewind allows the team to "go back" and capture the discussion after the fact. This audio is transcribed, speaker-identified, and distilled into team memory, where it becomes accessible to both humans and agents.
For the developer, the open-source, MIT-licensed Ox CLI provides the bridge. Commands like ox agent prime allow coding assistants—including Claude Code and Codex—to consult the team's shared history before writing code. This ensures that if a team decided in a meeting to use a specific authentication pattern, the agent knows it without being explicitly told in a prompt.
As Dr. Rupak Majumdar, Scientific Director, Max Planck Institute for Software Systems, noted after seeing the team’s development speed, they are effectively "treating code like assembler."
Agentic engineering: moving Beyond "clean" code
The shift to an agent-first workflow has forced the SageOx team to reconsider nearly every principle of modern software management.
SageOX CTO Ryan Snodgrass, formerly of Amazon, notes in a blog post transcript that traditional branch management and "clean" commit histories are often "bad for the agents." In the old world, humans preferred large PRs that were easy to read during a single code review.
In the agentic era, 10,000-line PRs spread across the codebase make it impossible for an agent to reason about intent.
Instead, SageOx advocates for smaller, high-volume, and highly focused commits. This "agent-readable" history allows the machine to look back and understand exactly why a specific change was made. The team is even re-evaluating repo structures; while they currently utilize a monorepo for their 750,000 lines of code, they are exploring a future where agents manage a constellation of micro-repos, as agents can "get lost" when a codebase grows too large for their context window.
This philosophy of "speed-over-stasis" allowed the team to build their own firmware for the Ox Dot in less than two weeks, despite having no recent hardware experience.
By feeding technical PDFs and documentation into AI models, they bypassed months of traditional research. CEO Ajit Banerjee calls this the "unlearning" of old habits—realizing that the "undifferentiated heavy lifting" of knowledge work can now be offloaded to a system that remembers everything the team knows.
Radical transparency: beyond open source to an "open work" model
Perhaps as significant as the technology is SageOx’s commitment to "Open Work." Moving beyond traditional open-source software, the company is practicing a form of radical transparency in an effort to foster the acceleration of development across the entire open source community and any enterprises who wish to learn from the way they work.
SageOx's team openly shares their internal prompts, their planning sessions, and even their unfiltered internal debates with the public. Users can sign in to the SageOx console and watch the team build SageOx in real-time.
This "open kimono" approach was an intentional decision to lead by example. Banerjee argues that since they are asking teams to change how they work, they must be willing to show the "WTF" moments and the course corrections as they happen.
"The revolution is not going to be televised," Banerjee says. "It's going to be SageOxed."
This transparency is intended to prove that a small, lean team—"yoking up lean"—can outpace massive organizations by leveraging a shared context layer.
As for how SageOx plans to monetize and become profitable, Banerjee said the revenue path is modeled on the AWS EC2 playbook: start with early adopters, especially small AI-native startups, then expand toward enterprises as the need becomes obvious.
The pedigree of infrastructure
The technical foundation of SageOx is rooted in the early days of cloud infrastructure.
Banerjee was an original member of the AWS EC2 team, and Snodgrass was one of Amazon's first engineers, leading the transition from monolithic architectures to microservices.
This background is reflected in the company’s name: the "Ox" represents the "Yeoman work" they aim to do—a dependable animal that handles the heavy lifting of data and context so the team can move forward.
The SageOx vision is one where humans are no longer the manual assemblers of context.
Instead, they act as the directors of a "parallel processing" engine.
In a recent demonstration, a feature request moved from a verbal discussion to a completed implementation in under seven minutes. By priming coding agents with the recorded context of the original discussion, the team bypassed the need for formal specs or Jira tickets.
The new way of work
SageOx is currently focusing its efforts on "AI-native" startups—teams that operate primarily through prompts and rely heavily on agentic coworkers.
Their suite of tools, from the open-source Ox CLI to the hardware-enabled Ox Dot, is designed to solve the immediate problem of alignment drift.
As AI moves from being a tool to a teammate, the most valuable asset a company possesses is no longer its raw source code, but its shared context.
SageOx suggests that the way forward is not to hoard information behind "private fences," but to create a communal ground where intent is visible to every teammate—human or machine. In this new epoch, the teams that win will be the ones that can remember as fast as they can execute.
- Agentic AI arrives, and the path forward demands our focus.
The age of agentic AI is upon us — whether we like it or not. What started with an innocent question-answer banter with ChatGPT back in 2022 has become an existential debate on job security and the rise of the machines.
More recently, fears of reaching artificial general intelligence (AGI) have become more real with the advent of powerful autonomous agents like Claude Cowork and OpenClaw. Having played with these tools for some time, here is a comparison.
First, we have OpenClaw (formerly known as Moltbot and Clawdbot). Surpassing 150,000 GitHub stars in days, OpenClaw is already being deployed on local machines with deep system access. This is like a robot “maid” (Irona for Richie Rich fans, for instance) that you give the keys to your house. It’s supposed to clean it, and you give it the necessary autonomy to take actions and manage your belongings (files and data) as it pleases. The whole purpose is to perform the task at hand — inbox triaging, auto-replies, content curation, travel planning, and more.
Next we have Google’s Antigravity, a coding agent with an IDE that accelerates the path from prompt to production. You can interactively create complete application projects and modify specific details over individual prompts. This is like having a junior developer that can not only code, but build, test, integrate, and fix issues. In the realworld, this is like hiring an electrician: They are really good at a specific job and you only need to give them access to a specific item (your electric junction box).
Finally, we have the mighty Claude. The release of Anthropic's Cowork, which featured AI agents for automating legal tasks like contract review and NDA triage, caused a sharp sell-off in legal-tech and software-as-a-service (SaaS) stocks (referred to as the SaaSpocalypse). Claude has anyway been the go-to chatbot; now with Cowork, it has domain knowledge for specific industries like legal and finance. This is like hiring an accountant. They know the domain inside-out and can complete taxes and manage invoices. Users provide specific access to highly-sensitive financial details.
Making these tools work for you
The key to making these tools more impactful is giving them more power, but that increases the risk of misuse. Users must trust providers like Anthorpic and Google to ensure that agent prompts will not cause harm, leak data, or provide unfair (illegal) advantage to certain vendors. OpenClaw is open-source, which complicates things, as there is no central governing authority.
While these technological advancements are amazing and meant for the greater good, all it takes is one or two adverse events to cause panic. Imagine the agentic electrician frying all your house circuits by connecting the wrong wire. In an agent scenario, this could be injecting incorrect code, breaking down a bigger system or adding hidden flaws that may not be immediately evident. Cowork could miss major saving opportunities when doing a user's taxes; on the flip side, it could include illegal writeoffs. Claude can do unimaginable damage when it has more control and authority.
But in the middle of this chaos, there is an opportunity to really take advantage. With the right guardrails in place, agents can focus on specific actions and avoid making random, unaccounted-for decisions. Principles of responsible AI — accountability, transparency, reproducibility, security, privacy — are extremely important. Logging agent steps and human confirmation are absolutely critical.
Also, when agents deal with so many diverse systems, it's important they speak the same language. Ontology becomes very important so that events can be tracked, monitored, and accounted for. A shared domain-specific ontology can define a “code of conduct." These ethics can help control the chaos. When tied together with a shared trust and distributed identity framework, we can build systems that enable agents to do truly useful work.
When done right, an agentic ecosystem can greatly offload the human “cognitive load” and enable our workforce to perform high-value tasks. Humans will benefit when agents handle the mundane.
Dattaraj Rao is innovation and R&D architect at Persistent Systems.
