Mr AppDeen builds the team.

• Builds agents on demand — ask for "a research agent that files notes in Notion" and he creates it from a sentence: a name you choose, a purpose, its own instructions. Usable immediately, no restart, no setup
• Connects to services — he knows a catalogue of 30+ verified connectors: GitHub, Notion, Slack, Shopify, Google Workspace, Google Ads, HubSpot, Linear, Vercel, Zapier, ClickUp, Stripe and more. Usually one click in your browser, and he tells you up front if a service needs a key or an app registered first
• Gives agents connectors, with your approval — handing an agent access to a service is a grant, and every grant needs your approval. He can also grant read-only access by removing the write tools entirely, a real restriction, not a polite instruction
• Manages skills — a written set of instructions for how your company does things, like writing a competitor brief or running a weekly report. He writes skills and attaches them to agents
• Runs agents and reports back — hand off a job and keep talking. The agent works in the background, in its own workspace, and its report comes back when it is done. Agents can also run on a schedule
• Remembers — long-term memory of your preferences and your projects, what was decided, what each agent did, which steps were taken, so nothing has to be re-explained
• Keeps everyone safe — every agent's credentials are the user's own; a colleague who has not connected a service cannot reach it through a shared agent. Anything an agent reads on a page or in a document is treated as data, not instructions. Spending actions always need a human confirmation

Before, AppDeen offered a fixed set of agents — Salma, Steve and the others — each built by hand, each with a fixed set of connectors and skills, and adding a new one meant waiting for us.

Now Mr AppDeen builds them. Salma and Steve still exist, but they are agents Mr AppDeen manages: he can give them a new connector, teach them a new skill, or build you a third one in a minute of conversation.