Agent tools have made it easy to turn a request into action. That is useful, but it also creates a new operational question: where does the work live after the conversation ends?
For a person, a short-lived chat can be enough. For a team, it is rarely enough. Work has inputs, constraints, tools, approvals, outputs, and a record of what happened. When those parts are scattered across chat threads, browser tabs, and private accounts, the team cannot confidently reuse or review the result.
Self-hosting is often described as an installation choice. For agent systems, it is more accurately an operating model.
Where an agent runs determines where its credentials live, which data it can reach, how its network access is governed, and who can inspect its execution. Those are not details to add after the workflow is useful. They are part of the workflow from the beginning.
The first useful agent interaction often looks deceptively simple. Someone asks for help, the agent retrieves context, runs a tool, and produces an answer or artifact.
The next question is more important: can the team run that process again without reconstructing it from memory?
