My Agents
/my-agents is your own corner of EnClaw — the place to create and manage assistants that belong to you alone. Where org agents are shared workhorses set up by your admin, a personal agent is yours: it works only for you, learns your preferences, uses your own connectors, and can be shaped however you like.
The page lists your personal agents in a simple table — each agent with its model, any bound channels, when it was last updated, and its status — with a search box when the list grows.
Personal vs org agents
| Org agents | Personal agents | |
|---|---|---|
| Who sets them up | Admins | You |
| Who can use them | Everyone in the organisation (subject to access rules) | Only you |
| Where they live in the app | Managed by admins | My Agents |
| Typical examples | Deal Desk Assistant, Customer Support | Your own PA, a research sidekick, a writing coach |
Both kinds chat the same way and follow the same approval rules. The difference is ownership and audience.
Why your personal agent answers only you
A personal agent is tied to your account. It never answers anyone else — not in a DM, not in a shared channel, not even if a colleague mentions it by name. If someone else asks a question that would normally suit your agent, the Orchestrator sends it elsewhere.
This is a privacy feature, not a limitation. Your personal agent may hold your preferences, your working notes and access to your connected accounts (via My Connectors) — so it stays strictly yours, with its own isolated memory. When the Orchestrator is choosing an agent for you, though, your personal agents are in the running alongside the org ones, so you can simply ask and let routing do its thing.
Creating a personal agent
New agent gives you three starting points:
- From a template — the quickest path; pick one of the built-in templates below and the identity, model and skills come pre-filled.
- Clone from an org agent — take a shared agent you like and make it yours. Your personal copy gets isolated memory and uses your connectors, with the identity and model already filled in — then tweak away without affecting anyone else.
- Start blank — just a name, an identity and a model, if you know exactly what you want.
Whichever you choose:
- Give it a name.
- Skim its identity (see below) and adjust anything you'd like — tone, focus, rules.
- Save. It's live immediately; the Orchestrator can now route your questions to it, or you can chat with it directly.
You can also Browse marketplace from this page — agent templates installed from here land as personal agents in your list, not on the org-wide registry. More in Marketplace.
The 12 built-in templates
| Template | Good for |
|---|---|
| Project Manager | Tracking tasks, statuses, standup summaries |
| RFP Agent | Pulling together responses to tenders and RFPs |
| Content Author | Drafting posts, articles and copy |
| Social Media Agent | Planning and drafting social content |
| CRM Assistant | Working with deals, contacts and pipeline |
| Health Monitor | Keeping an eye on metrics and flagging anomalies |
| Business Analyst | Digging into data and summarising findings |
| Coding Agent | Development help and code tasks |
| PR Review Agent | Reviewing code changes |
| Testing Agent | Test planning and checks |
| UI/UX Designer | Design feedback and ideas |
| Customer Support | Handling support-style questions |
Templates are starting points, not straitjackets — rename them, rewrite their identity, switch their skills on or off. A "Project Manager" template can become "Max's Friday-report writer" in two minutes.
Agent identity, in plain words
Every agent has an identity: a written description, in ordinary language, of who it is and how it behaves. Think of it as the brief you'd hand a new team member on day one:
- Role — "You are my research assistant. You summarise industry news and never speculate."
- Tone — "Warm and brisk. Australian English. No waffle."
- Rules — "Always cite a source. If you don't know, say so. Never send anything without asking me."
You don't need any special format. Clear sentences work. The identity is the single most powerful lever you have — a well-written one is the difference between an agent that "sort of helps" and one that feels like it's read your mind. The sales playbook has full worked examples of identities you can copy and adapt.
A few tips:
- Be specific about what the agent should refuse to do ("never guess an owner — show the options instead").
- Spell out what "good" looks like ("answers include the source link").
- Keep it focused. An agent that does one job brilliantly beats one that does five jobs vaguely.
Saving an agent as a template
Built something great? You can save any agent as a template, so its setup — identity, skills, configuration — becomes a reusable starting point. That's handy for:
- Spinning up a similar agent later without redoing the setup.
- Sharing a proven recipe with your team (via your admin), so everyone gets their own copy rather than crowding one agent.
Open the agent, choose Save as template, name it, and it appears in the template library alongside the built-ins.
Everyday care and feeding
- Correct it out loud. "Actually, our financial year starts in July" — the agent remembers, and future answers improve. See Memory & context.
- Give it schedules. A personal agent can run recurring jobs for you — a Monday-morning pipeline summary, say. See Schedules & reminders.
- Retire what you don't use. Each row has Enable/Disable, and inactive agents can be deleted (you'll be asked to type the agent's name to confirm — deletion is permanent). View logs on a row shows you what an agent has been up to.