Two weeks in: deploying a persistent agent to my ops team
I deployed a custom-made persistent AI agent inside my company as a test. The agent runs on OpenClaw here in our office in Mountain View.
Our agent, nicknamed “Owl”, has already become a documentation champ. I didn’t expect this use case to be the first win. It’s almost fully removed the annoying/cumbersome (but important) task of capturing decisions in our Confluence wiki. It jotted down some decisions on IEEPA tariff refunds / Section 122 tariff changes, worked up a page about an expensive component risk buy we made & drafted several internal docs on 3PL workflows. Combined, I’d estimate that saved 4-5 hours of work.
The Claw framework is hyped, maybe overhyped; but with companies like NVIDIA launching their own fork, Nemoclaw, I believe it has already made a permanent mark. Anthropic & OpenAI have started to build persistent memory & remote-first features into their own products.
My thesis going in was that an agent can collect our team’s own institutional knowledge. It will become a compounding knowledge base that can be easily searched. And it will capture key decisions and be an automated early signal on news in our specific supply chain (electronics). There’s so many directions we could take this - but next on the roadmap is moving toward establishing the concept of “advisory councils” for the team - this could really widen our small team’s reach to draw on simulated “expert” advice for our key issues.
Owl is purposefully limited in its access to internal systems. This is a trial and cannot access any PII or sensitive IP.
A few quick notes about the agent’s access:
it has its own email address, google drive & calendar API integration
it has access to read/write from confluence
interfacing with the agent happens on slack
only the operations team has access / in specific channels
it has access to crawl the internet.
Owl writes everything down in markdown format and saves it, making querying down the line easy. It should hopefully function like a second brain.
For now the use case of having institutional memory is not delivering. Its knowledge of us is thin. I suspect investing in building out a repeatable process for capturing context will be key to making it useful. We will be looking into creating an internal CRM (of our partners & actions that we’ve taken), automating meeting note intake, slack summaries & weekly status updates.
I’m excited to see where this heads. Stay tuned for more updates.