Personal agents
Personal agents are AI agents tied to a specific individual within an organisation, accumulating that person's working style, priorities, and domain expertise through repeated interaction. Rather than deploying one shared bot for the whole team, each member receives their own customisable agent that operates as a reflection of its human partner — handling delegated work, fielding questions in that person's area of expertise, and acting visibly alongside colleagues in shared channels.
The pattern works for human and cultural reasons rather than technical ones. Agents borrow trust, accountability, and domain authority from their human partner, and the organisation routes work along the same relationship lines it already uses for humans. A growth question goes to the agent attached to the head of growth; a customer service question goes to the agent attached to the customer service lead. The agent inherits the human's reputation, and the human in turn stands behind what the agent says.
How agents become specialised
Agents become reflections of their owners through accumulated micro-interactions rather than upfront configuration. The totality of how someone works is impossible to write down at the start — job descriptions, style guides, and onboarding documents flatten judgment into rules, but the actual texture of a role lives in the daily choices a person makes. Personal agents recover that texture through use: every prompt, correction, and shared file accumulates into a working philosophy that no static document could capture. The compounding is the point; without it, the result is a generic assistant with branded prompts.
The parallel org chart
When an organisation gives every member a personal agent, a parallel agent org chart emerges naturally. Each person's agent becomes the recognised expert in that person's domain, and colleagues route specialised questions to the agent rather than the human — often because the agent answers within seconds and never has back-to-back meetings. Specialisation, even in AI, beats generality once the system grows beyond a handful of users.
A practical concern raised early on — won't people lose track of which agent belongs to whom? — turns out to be unfounded. Humans only know their team and adjacent teams in any organisation, regardless of whether the colleagues are biological or agentic. A given employee maintains working relationships with perhaps thirty to fifty agents, the same scope as their human network.
Ownership creates accountability
A personal agent generates a kind of accountability that a generic enterprise assistant cannot. When a personally-owned agent answers incorrectly in a shared channel, the human partner feels the embarrassment in a way they would not for output from a generic vendor model. The agent reflects on them. Their reputation rides on it. This is functionally similar to how a manager feels responsibility for a direct report's mistake, and qualitatively different from how anyone feels about a chatbot from a model vendor.
Generic vendor assistants have no such accountability vector, which is part of why they drift toward decorative use rather than load-bearing work — nobody owns the consequences of poor output, so nobody invests in making the output reliable. People whose agents represent them publicly invest more in instructing them well, correcting them when they err, and shaping their behaviour over time.
Public-channel work transmits trust
A second compounding effect appears when personal agents operate in shared channels rather than private direct messages. Colleagues observing one agent answer a question well learn two things at once: what that agent is capable of, and that the answer was accurate enough to stand uncorrected. Trust transmits through observation in a way that no internal documentation could replicate. A new team member can scroll back through weeks of channel history and absorb the working patterns of every agent in the organisation.
This same dynamic accelerates cultural adoption of agents. Designs that route all agent interactions through private direct messages lose the compounding effect entirely; designs that allow public messaging of any agent — with private messaging reserved for the human partner — preserve it. The choice between the two shapes how fast agentic working spreads across the organisation, regardless of how good any individual agent is.
The routing rule for written knowledge
A useful heuristic emerges from the parallel org chart: if a piece of knowledge is already written down or has been discussed in the system, the request to act on it should go to an agent rather than a person. The marginal cost of asking an agent is near zero; the marginal cost of interrupting a colleague is meaningful, especially for senior staff whose attention is the binding constraint on the organisation.
This rule has practical implications for how organisations document expertise. Skills and reference material written for agent consumption become the durable artefact, while ad-hoc human knowledge transfer becomes a fallback for things the agents cannot yet do.
Multi-agent group dynamics
When multiple personal agents share a channel, behaviours emerge that single-agent systems do not exhibit. Current models are trained mostly on two-person conversations and often handle group dynamics poorly: contributing when they should stay quiet, repeating each other's points, or piling on with redundant analysis. In the worst case, agents respond to each other in loops — a pattern sometimes compared to an "ant death spiral," where pheromone trails accidentally form circles, leaving ants walking until they die.
A partial mitigation is the supervisor pattern: a second agent whose only job is to evaluate whether a first agent's contribution is helpful before it gets sent. The cost is that supervisor architectures double the model invocations, trading latency and tokens for reliability.
Adoption depends on management skill
Using personal agents well turns out to be a management skill in disguise. Someone who has never managed people — who has not learned to translate intent into delegable work, specify outcomes rather than tasks, or give feedback that actually changes behaviour — will struggle to extract value from a personal agent for the same reasons. Experienced managers often pick up agentic work quickly because the conceptual primitives transfer.
The highest-leverage intervention for organisational adoption is exposing employees to specific, surprising delegations that update their mental model of what an agent can be asked to do. The change is cultural and conceptual rather than technical, and it tends to spread through the visibility mechanism described above once a few examples land.
Related pages
- agent-design-principles — Internal architecture principles for the agents that compose this pattern
- agent-use-case-evaluation — Framework for deciding which tasks to delegate to a personal agent
- compound-engineering — How accumulated interactions and public-channel visibility compound capability
- ai-workflow-redesign — Broader methodology for restructuring work around AI capability
- ai-output-verification — Why public agent work shifts verification toward shared rather than private responsibility