Adjutant
Personal software
I started Adjutant in March 2026 after deciding that the personal-agent tools I tried required more access than I was comfortable granting. I built a smaller framework whose knowledge, permissions and lifecycle I could understand and control.
Why I built it
I was interested in personal agents and tried installing OpenClaw. The amount of access it appeared to require across my computer and network made me uncomfortable, while changing documentation made the setup difficult for me to understand and trust. I wanted the same kind of assistance in a system where I could follow how the parts worked.
What I use it for
Adjutant helps me keep track of work connected to my cabin, selected responsibilities in voluntary organisations, and holiday planning. Telegram gives me one place to ask questions and add information to the relevant knowledge base while I am away from the computer.
Keeping subjects separate
The hardest technical problem was separating the knowledge bases properly and routing every request to the correct one. The separation matters because a note about one organisation, property or trip should not silently become context for another. Adjutant uses sandboxed knowledge-base workspaces and explicit knowledge-base commands alongside natural-language routing.
Building software with AI
Keeping the codebase consistent across many AI-assisted development sessions became another part of the problem. I learned to plan each session and preserve records of why, when and how a decision was made or implemented. Those records give later sessions the context needed to extend the project without reopening the same decisions.
A framework I can stop
The Python application connects Telegram, long-term memory, scheduled jobs, knowledge bases and a web dashboard. Pause, resume and emergency shutdown commands make its state explicit. Notification budgets and a human-in-the-loop approach limit when autonomous tasks interrupt me or take action.
Current status
The main framework was built from March 2026 and is now in maintenance mode. I continue to use it for personal knowledge and planning, while changes are mostly focused on keeping the system dependable rather than expanding its scope.
A personal project by Edvard Pires Bjørgen, started in March 2026. Source and documentation are released under the MIT license.